Microsoft’s latest Insider flight, Windows 11 Build 27965 (Canary Channel), delivers the most substantial Start menu overhaul since Windows 11’s debut — a single, scrollable Start surface with new browsing modes, a responsive layout that adapts to screen size, and deeper Phone Link integration — while also introducing platform-level packaging changes and a small, open-source command-line editor aimed at developers and administrators.
Microsoft has been iterating on the Windows 11 Start experience for more than a year, responding to repeated user feedback about the original Start layout’s limited flexibility and the space consumed by the Recommended feed. The company moved from a multi-pane Start (Pinned / Recommended / All apps separated) toward a more unified, app-first surface that mirrors modern mobile launchers: everything is accessible via a single vertical canvas that scrolls. That design philosophy underpins Build 27965 and the related 24H2/25H2 servicing work Microsoft has been rolling out via enablement packages rather than full OS reinstalls.
This build is currently available to Windows Insiders in the Canary channel and is being staged gradually; not every Insider will see the experience immediately because Microsoft uses server-side gating and A/B testing to manage exposure. That rollout model reduces heavyweight upgrades but increases variability in what a given device receives.
Independent early coverage and hands-on reports from testers corroborate the single-surface model and emphasize that this is more than cosmetic: it materially speeds up app discovery and makes the Start experience feel more like a true app launcher.
The inclusion of toggles to hide recommended content is a long-overdue UX win; it restores agency to users who found in-Start recommendations noisy or promotional. The Phone Link integration inside Start is a sensible, incremental cross-device capability that supports quick glance flows without merging the full phone app experience into the desktop.
However, the current lack of manual category management, combined with limited management APIs, means power users and IT admins are being asked to accept AI/system decisions without a way to assert control. That’s the single most important shortcoming from a management and predictability perspective. Microsoft should prioritize MDM/GPO controls for Start layout and category behavior, and provide predictable enterprise hooks before broad enterprise rollout.
Accessibility needs focused verification: keyboard focus, narration ordering, consistent column changes, and predictable behavior when sections collapse are all non-trivial for assistive tech users. These deserve targeted testing and public documentation of keyboard shortcuts and semantic roles for the new Start structure.
For everyday users and power users, the redesigned Start should feel faster and more flexible. For IT teams and enterprises, this update is a signal to inventory legacy dependencies, test imaging and deployment workflows, and watch for management controls that make Start predictable at scale. And because these changes are being rolled out via staged enablement, individual experiences will vary: validation in a controlled lab and a cautious pilot remains the recommended approach.
Windows’ Start menu has long been a central interaction point; Build 27965 is the most thoughtful rework Windows has offered in years. It solves many discoverability and space problems while exposing clear areas where Microsoft must deliver more controls for administrators and more assurances for accessibility. The redesign is promising — but the details of manageability and long-term polish will determine whether this becomes a universal improvement or another feature that requires careful enterprise planning.
Source: Windows Report Windows 11 Build 27965 Brings Smarter Start Menu With Scrollable Layout
Microsoft has been iterating on the Windows 11 Start experience for more than a year, responding to repeated user feedback about the original Start layout’s limited flexibility and the space consumed by the Recommended feed. The company moved from a multi-pane Start (Pinned / Recommended / All apps separated) toward a more unified, app-first surface that mirrors modern mobile launchers: everything is accessible via a single vertical canvas that scrolls. That design philosophy underpins Build 27965 and the related 24H2/25H2 servicing work Microsoft has been rolling out via enablement packages rather than full OS reinstalls. This build is currently available to Windows Insiders in the Canary channel and is being staged gradually; not every Insider will see the experience immediately because Microsoft uses server-side gating and A/B testing to manage exposure. That rollout model reduces heavyweight upgrades but increases variability in what a given device receives.
What’s new in Build 27965 — the headline features
A single, scrollable Start surface
The most visible change is the consolidation of Pinned apps, Recommended content, and All apps into one continuous, vertical surface. The “All” apps view is now at top-level, eliminating the separate “All apps” page and allowing users to simply scroll to find installed applications. This reduces clicks and context switching, which is particularly useful for users with large app sets. Microsoft’s release notes describe this as putting “All” on the top-level to make apps “easily accessible without having to navigate to a secondary page.”Independent early coverage and hands-on reports from testers corroborate the single-surface model and emphasize that this is more than cosmetic: it materially speeds up app discovery and makes the Start experience feel more like a true app launcher.
Two new browsing modes for “All” apps: Category and Grid (plus List)
Microsoft ships three ways to browse installed apps:- Category view (default): Apps are system-grouped into buckets (e.g., Productivity, Games, Creativity) when at least three apps fit a recognized category. Frequently used apps in each bucket “bubble up” toward the top of the group, prioritizing the apps you use most.
- Grid view: An alphabetically ordered grid that uses horizontal real estate to reduce vertical scrolling, making scanning faster for visual users.
- List view: A classic alphabetical list retained for familiarity and users who prefer a text-first approach.
Responsive start: larger screens show more columns, smaller screens scale down
A central goal for the redesign is to “make better use of your screen real estate.” Microsoft documents specific defaults:- On larger displays: up to 8 columns of pinned apps, 6 recommendations, and 4 columns of categories.
- On smaller displays: typically 6 columns of pinned apps, 4 recommendations, and 3 columns of categories.
Phone Link integration inside Start
Build 27965 surfaces a small mobile device button beside the Start search box that expands a Phone Link sidebar directly in the Start surface. This provides quick access to basic phone capabilities — messages, calls, photos, battery status — without launching a separate Phone Link app. Microsoft says cross-device integration is generally available for connected Android and iOS devices in most markets and will extend further geographically later. Testers report the Phone Link pane is collapsible and intended for lightweight glances and quick share flows.Beyond Start: platform and tooling changes
Edit — an open-source, lightweight command-line editor now delivered with Windows
Microsoft has introduced Edit, a new modeless, text-user-interface (TUI) command-line editor that ships as part of Windows and is open source on GitHub. Edit is intentionally small (under ~250KB), supports mouse mode, multiple open files, find & replace with regex, word wrap, and keybindings for menu actions. It fills a long-standing gap in modern 64-bit Windows, which lacked a built‑in CLI editor comparable to MS-DOS Edit in 32-bit editions. Edit is accessible from the Terminal using the commandedit and can also be installed via winget. Microsoft has published documentation and source, and the editor is rolling to Insiders. This addition targets developers, SREs, and administrators who do quick config edits in-terminal. .NET Framework 3.5 packaging change
Starting with Build 27965, .NET Framework 3.5 is no longer offered as a Windows Feature on Demand (FoD) optional component. Microsoft encourages migration to modern .NET versions and provides a standalone .NET Framework 3.5 installer for scenarios that still depend on the legacy runtime. This is a packaging and delivery change rather than a removal, but it has real operational implications for imaging, offline deployments, and legacy line-of-business applications. Enterprises should inventory dependencies, test the standalone installer scenario, and prepare a deployment plan for devices that still require .NET 3.5.Fixes, known issues, and the Canary trade-offs
Build 27965 also includes a collection of daily‑use fixes (taskbar autohide correction, video playback tint issues, and protected-content playback fixes), but as a Canary Channel flight, it ships with multiple known issues. Reported problems include File Explorer crashes with network transfers, Settings crashes on certain drive info pages, lock-screen media control regressions, and some power/sleep anomalies. Canary is Microsoft’s sandbox: expect instability, evolving behaviors, and frequent updates. For production or enterprise pilot groups, patience and test labs are essential.Why this redesign matters — UX and productivity analysis
- Fewer clicks to reach your apps. By placing All apps at top-level and enabling a single scrollable surface, users save time compared with switching to a secondary page. This benefits power users and people who multitask across dozens of applications.
- Contextual discovery with Category view. Grouping related apps reduces cognitive load when searching for a task rather than an app name. For example, “Productivity” will surface email, office, and calendar tools together. This model favors task-first workflows.
- Better use of large displays and high-DPI setups. The responsive column logic takes advantage of widescreen real estate that was previously wasted, letting you pin more apps in one view. This is a clear win for desktop and multi-monitor users.
- Reduced in-Start promotion surface. Microsoft added explicit toggles under Settings > Personalization > Start to hide recommended content (recent files, tips, websites). That gives users more control over whether Start is promotional or purely functional. This addresses a long-standing complaint from many Windows 11 adopters.
- Native developer tooling. Shipping Edit in-box reduces friction for quick terminal edits and aligns Windows more closely with Unix-like workflows where a terminal editor is assumed to exist. The open-source release also invites community contributions.
Risks, caveats, and unanswered questions
1. Enterprise determinism and managed fleets
The Category view is system-controlled and currently lacks manual curation or policy controls that enterprises need for deterministic image behavior. For managed fleets where predictable app placement matters (training, compliance, kiosk-style deployments), the inability to set categories or pin layouts via Group Policy or MDM APIs is a significant limitation today. Enterprises should treat this as an operational risk until Microsoft provides management hooks.2. Rollout variability and enablement flags
Because the code is present in servicing branches and features are often flipped server-side, two identical devices can show different Start experiences. While this reduces heavy upgrades, it complicates IT validation and user support: the visibility of a feature depends on enablement flags, not only on OS version. Organizations should assume staged exposure and test across multiple enablement scenarios.3. Accessibility and discoverability trade-offs
Category groupings can speed discovery for many users but may confuse others if apps are categorized unexpectedly or if the grouping algorithm places apps in an “Other” bucket. Accessibility testing will need to validate screen‑reader behavior, keyboard navigation across the scrollable surface, and whether the adaptive column changes create focus or navigation surprises for users relying on assistive technologies. Early reports do not indicate major regressions, but full accessibility audits are necessary before enterprise-wide rollouts.4. Packaging change for .NET Framework 3.5
Removing .NET 3.5 as a Feature on Demand is operationally mild but practically important. Environments that rely on offline imaging or that use unattended installs must ensure the standalone 3.5 installer is included in their image or deployment pipeline. Failing to plan can break legacy line-of-business apps. This is a change in delivery model, not immediate removal — but it needs action.5. Canary instability
This build is Canary — early, experimental, and unstable. The presence of UI polish alongside hard crashes (File Explorer network transfers) and power regressions underscores the need to avoid deploying Canary bits to production hardware. Use virtual labs or dedicated test hardware for evaluation.Practical guidance for different audiences
For casual and power users (early adopters)
- Join the Windows Insider Canary channel only on non-critical devices.
- Test the Category and Grid views to see which model fits your workflow. Use Settings > Personalization > Start to toggle Recommended items if you prefer a cleaner launcher.
- Try the Edit editor in Terminal (
edit <filename>) for quick file edits; it’s a welcome, lightweight addition for command-line work.
For IT teams and admins
- Inventory your estate for .NET Framework 3.5 dependencies and prepare the standalone installer in images and deployment repositories. Test legacy apps against the packaging change.
- Don’t deploy Canary builds to production. Use lab devices to evaluate the Start redesign and document any workflow impact, especially around training and helpdesk scripts.
- Monitor Microsoft’s policy and management updates for Start layout controls. If deterministic pin layouts or category controls matter, escalate to the Windows Insider channels and track feature requests.
For developers and SREs
- Install Edit via winget or test the in-box
editcommand — it’s useful for quick configuration edits inside Terminal and integrates well with Windows Terminal workflows. - If you rely on automated imaging or scripts that surface pinned items or manipulate Start, account for the responsive column behavior and potential UI changes that may affect optical checks or GUI automation scripts.
Design and accessibility commentary — what Microsoft gets right, and where it should push further
Microsoft’s move to a scrollable Start that adapts to screen size is a pragmatic and user‑centric shift. It acknowledges the variety of modern form factors — from small laptops to high-resolution ultrawide monitors — and reduces friction by placing “All apps” where users naturally expect them: on the main surface.The inclusion of toggles to hide recommended content is a long-overdue UX win; it restores agency to users who found in-Start recommendations noisy or promotional. The Phone Link integration inside Start is a sensible, incremental cross-device capability that supports quick glance flows without merging the full phone app experience into the desktop.
However, the current lack of manual category management, combined with limited management APIs, means power users and IT admins are being asked to accept AI/system decisions without a way to assert control. That’s the single most important shortcoming from a management and predictability perspective. Microsoft should prioritize MDM/GPO controls for Start layout and category behavior, and provide predictable enterprise hooks before broad enterprise rollout.
Accessibility needs focused verification: keyboard focus, narration ordering, consistent column changes, and predictable behavior when sections collapse are all non-trivial for assistive tech users. These deserve targeted testing and public documentation of keyboard shortcuts and semantic roles for the new Start structure.
Conclusion
Windows 11 Build 27965 marks a meaningful evolution of the Start menu from a rigid set of panels to a responsive, scrollable launcher that better fits modern workflows and displays. The new Category and Grid views, the adaptive column logic, and the Phone Link integration are clear usability wins that respond to long-standing pain points. At the same time, the release bundles operational changes — notably the .NET Framework 3.5 packaging update — and ships experimental tooling like the open-source Edit editor, all under the Canary channel’s experimental umbrella.For everyday users and power users, the redesigned Start should feel faster and more flexible. For IT teams and enterprises, this update is a signal to inventory legacy dependencies, test imaging and deployment workflows, and watch for management controls that make Start predictable at scale. And because these changes are being rolled out via staged enablement, individual experiences will vary: validation in a controlled lab and a cautious pilot remains the recommended approach.
Windows’ Start menu has long been a central interaction point; Build 27965 is the most thoughtful rework Windows has offered in years. It solves many discoverability and space problems while exposing clear areas where Microsoft must deliver more controls for administrators and more assurances for accessibility. The redesign is promising — but the details of manageability and long-term polish will determine whether this becomes a universal improvement or another feature that requires careful enterprise planning.
Source: Windows Report Windows 11 Build 27965 Brings Smarter Start Menu With Scrollable Layout