Windows 11 Start Menu Gets a Single Scrollable Surface in Canary Build 27965

Microsoft has quietly pushed a meaningful overhaul of the Windows 11 Start menu into Insider Preview Build 27965 on the Canary Channel, giving testers a single, scrollable Start surface with new browsing modes for installed apps, improved responsiveness for large displays, a built‑in Phone Link side panel, and platform changes that include a new lightweight first‑party Edit command‑line text editor and an altered delivery model for legacy .NET Framework 3.5.

Background​

Microsoft has been iterating on the Windows 11 Start experience for more than a year, responding to user feedback that the original Start layout was inflexible and that the Recommended feed often dominated the UI. The company has been shipping a lot of 25H2-era UI work via staged enablement packages and server-side gating rather than full OS reinstalls, which explains why the new Start can appear on devices running different servicing branches at different times.
The Canary Channel is the experimental sandbox where Microsoft tests aggressive changes that may evolve before (and if) they reach Dev, Beta, or Release Preview rings. Because the rollout is phased and may be server‑gated or A/B tested, not every Insider will see the new Start immediately even after installing Build 27965. That staged distribution is intended to let Microsoft collect feedback and telemetry before a broader release.

---

What changed (high‑level)​

• The Start menu becomes a single, scrollable surface that presents Pinned apps, Recommended files/apps, and All installed apps in one continuous vertical canvas rather than splitting them into separate pages or panes.
• The “All” installed‑apps area gains two new views in addition to the classic List: Category view (default) and Grid view, letting users choose the browsing model that best matches their workflow.
• The Start menu is responsive: on larger displays it shows more columns and content by default (Microsoft lists specific defaults such as 8 columns of pinned apps, 6 recommendations, and 4 category columns on larger devices). On smaller screens those defaults scale down.
• A Phone Link side panel can be expanded or collapsed directly from the Start UI using a new mobile device button in the Start chrome; cross‑device Phone Link features are rolling out to most markets but will arrive later in the European Economic Area (EEA).
• Build 27965 also automatically installs a lightweight Edit command‑line text editor and changes how .NET Framework 3.5 is delivered (it is no longer a Feature on Demand but remains available as a standalone optional component).

These are the core changes testers will notice. Below is a deeper breakdown and critical perspective on what these updates mean for users, IT teams, and Windows as a platform.

---

Deep dive: the redesigned Start menu​

Single, scrollable Start surface​

The most visible change is that Start now feels like a modern app launcher: everything is accessible on one vertical canvas. That removes the extra click or page‑switch to reach “All apps,” letting users simply scroll to find software or recent files. Early hands‑on coverage and the Insider announcement emphasize that this is intended to speed app discovery and reduce cognitive switching.
Benefits:

• Faster one‑stop access for large app catalogs.
• Cleaner mental model: one continuous surface rather than separated panes.
• Better use of modern high‑resolution displays.

Trade‑offs:

• The single surface increases vertical density and may feel overwhelming to some users who prefer clearly separated zones.
• Because the experience is staged, some users will have inconsistent Start UIs across multiple devices in the same environment.

New “All” views: Category, Grid, and classic List​

Build 27965 ships three browsing modes for installed apps:

• Category view (default): apps are automatically grouped into task‑oriented buckets (Productivity, Games, Creativity, Communication, Other, etc.) when at least three apps fit a recognized category. Frequently used apps “bubble up” to the top of their category. This view aims to surface related tools contextually.
• Grid view: an alphabetically ordered grid that uses horizontal real estate to reduce vertical scrolling and speed visual scanning. The grid preserves alphabetical ordering but presents apps as tiles.
• List view: the classic alphabetic list retained for users who prefer a text‑first lookup.

Practical implications:

• Category view benefits users who think in terms of tasks rather than app names, but the grouping is currently system‑generated and cannot be renamed, reordered, or curated by the user or admin (a limitation with clear UX and enterprise policy implications).
• The OS remembers your last used view, so switching once will persist to your preference until changed.

Responsive layout: optimized for big screens​

Microsoft explicitly designed the new Start to scale with display size. The Insider notes provide concrete defaults (used as illustrative maximums):

• Larger devices: up to 8 columns of pinned apps, 6 recommendations, and 4 category columns.
• Smaller devices: typically 6 columns of pinned apps, 4 recommendations, and 3 category columns.

This adaptive behavior is intended to give more at‑a‑glance density on large monitors and reduce wasted space on laptops and tablets. The Start sections themselves (Pinned and Recommended) are responsive and will collapse or expand depending on content—if you have few pins, the Pinned area shrinks and reveals more of the All apps area.

Controls for recommendations and pins​

Acknowledging long‑standing feedback about the Recommended feed, Microsoft added dedicated toggles in Settings > Personalization > Start to turn off:

• Show recently added apps
• Show recommended files in Start
• Show websites from your browsing history
• Show recommendations for tips

Turning these off collapses the Recommended area entirely, leaving Pinned and All apps as the main focus. There’s also a “Show all pins by default” option so all pinned items are visible without clicking “Show all.”

Phone Link companion side panel​

Start now hosts a collapsible Phone Link panel reachable via a new expand/collapse button in the upper‑right area of the Start UI. The panel surfaces messages, calls, photos, battery information, and context‑menu actions like “Send to my phone” that make cross‑device tasks faster. While the integration is rolling out in many markets, Microsoft noted that the feature will reach the European Economic Area later in the year. That staggered regional availability reflects regulatory and localization complexities.

---

Platform and delivery changes in Build 27965​

Two changes in the plumbing are equally important for IT and power users:

• Edit command‑line text editor: A lightweight, first‑party Edit text editor is now available out of the box and is usable from the command line (for example via the Terminal). This is a modern, low‑friction tool for quick file edits without bringing a heavy editor.
• .NET Framework 3.5 delivery change: Microsoft documented that .NET Framework 3.5 is no longer shipped as a Windows Feature on Demand optional component in this build. Customers who still rely on .NET 3.5 will need to use a standalone installer Microsoft provides; the framework remains available but its packaging and installation path have changed. This is a deliberate push toward modern .NET versions, but it has noteworthy operational consequences for organizations with legacy LOB applications.

---

Cross‑checks and verification​

Multiple independent outlets and Microsoft’s official Insider blog corroborate the core claims above: the single scrollable Start, Category and Grid views, the responsive layout with specific column counts, Phone Link integration, and the .NET packaging change. The Windows Insider blog provides the authoritative release notes for Build 27965, while technology outlets and hands‑on reviews reaffirm the UX details and rollout behavior.
Where a single claim is less explicit in public notes—such as precise thresholds for category generation or the exact timeline for EEA availability—Microsoft’s blog notes and early hands‑on reporting converge on the same practical descriptions (for example, categories forming when at least three apps fit the same bucket). Those specifics are documented in the Insider notes and supported by early tester reports, but some rollout timing words like “later in 2025” are necessarily imprecise and should be treated as target windows rather than hard SLAs.

---

Critical analysis: strengths​

• Improved discoverability and density: Putting All apps at the top level and offering a Category view meaningfully reduces friction for users who juggle many applications. On large displays the new defaults let users see more at a glance without additional clicks.
• Choice of mental models: By shipping Category, Grid, and List views, Microsoft acknowledges diverse user preferences—visual scanners, alphabetically oriented users, and task‑focused users all have a fast path.
• User controls for recommendations: The separate toggles to hide Recommended content directly address a frequently voiced complaint and let users prioritize personal pinned apps and installed apps.
• Cross‑device convenience: The Phone Link companion reduces context switching—small tasks like checking a message or sending a photo are more immediate without switching apps. For many users this will be an incremental but meaningful productivity win.
• Modernizing platform delivery: Shipping a lightweight Edit tool and adjusting .NET 3.5 delivery reflects Microsoft’s push toward modern, smaller, and more maintainable platform footprints. For developers and modern environments this is sensible.

---

Critical analysis: risks and unknowns​

• Lack of manual category control: Categories are system‑generated and cannot currently be renamed, reordered, or curated by users or administrators. For power users and enterprise-managed devices that require predictable layouts, this is a significant limitation. Admins who rely on deterministic Start layouts for training or compliance will need to plan around it.
• Rollout inconsistency and support complexity: Because the redesign is being staged and gate‑released, organizations will see inconsistent Start UIs across machines and user profiles—complicating support, documentation, and training. IT teams must be prepared for mixed experiences in pilot rings.
• Operational impact of .NET 3.5 packaging change: Removing .NET Framework 3.5 as a Feature on Demand component changes how offline images, SCCM/Intune tasks, and LOB deployments are handled. Organizations with legacy applications should inventory .NET 3.5 dependencies, validate the standalone installer path, and test application compatibility before broad rollout. This is an area that will require immediate attention from enterprise IT.
• Privacy and compliance considerations with Phone Link: While Phone Link integration is convenient, organizations with strict data protection or compliance requirements should verify how phone content is surfaced and whether policy controls can restrict this functionality. The EEA‑delayed rollout suggests Microsoft is mindful of region‑specific regulatory considerations. Administrators should treat Phone Link as a controllable endpoint integration and evaluate its implications.
• Stability and known issues: Canary builds are inherently experimental and may expose edge cases—testers reported known issues in early builds (Explorer crashes during certain network transfers, Settings crashes around drive info, media playback and power regressions, etc.). These are expected in Canary and reinforce the recommendation to avoid running such builds on production machines.

---

Practical guidance: what Insiders and IT should do now​

For enthusiasts and testers:

• If you’re comfortable with experimental software, enroll a spare machine or VM into the Canary Channel and install Build 27965 to try the new Start and Phone Link features. Use Feedback Hub (WIN + F) to file constructive feedback under Desktop Environment > Start menu.
• Explore Settings > Personalization > Start to toggle Recommended content and to set your preferred All view (Category, Grid, List). This is how you regain control of what's visible.
• Back up critical files before experimenting; Canary builds can include regressions and known issues.

For IT admins and organizations:

• Inventory .NET Framework 3.5 dependencies immediately. Identify business‑critical apps that require 3.5 and verify that the standalone installer and offline imaging workflows work in your environment. Plan remediation or modernization timelines for legacy apps.
• Use a phased pilot strategy: test Build 27965 in a controlled ring and validate application compatibility, Start menu behavior, Phone Link privacy implications, and support scripts/documentation before broader rollout.
• Update support documentation and training materials to reflect multiple Start experiences and to instruct users on toggling recommendations and choosing All views. Prepare helpdesk scripts to handle questions about missing features (server‑side gating may hide or reveal features unpredictably).
• Evaluate policy controls: confirm whether Intune, Group Policy, or MDM controls will allow you to disable Phone Link or the Recommended feed where sensitive. If not available yet, track Microsoft policy updates and release notes.

---

Accessibility, UX, and manageability considerations​

• Accessibility: Grouping apps by category can help some users who think in task terms, but the automatic grouping logic must be transparent and reliable for accessibility tools to integrate well. Microsoft should document category rules and expose APIs or settings for assistive technologies.
• Customization vs. predictability: The tension between adaptive UIs (which are nice for end users) and deterministic behavior (which enterprises need) remains unresolved. Microsoft will need to add administrative controls if the Category view becomes widely adopted in corporate environments.
• Telemetry and feedback loops: The phased rollout suggests Microsoft will refine category heuristics and visual density based on telemetry and Feedback Hub submissions—Insiders should prioritize constructive, reproducible feedback to influence those refinements.

---

What remains uncertain and flagged items​

• Exact timeline for EEA availability of the cross‑device Phone Link integration is described as “later in 2025” in Microsoft’s notes. That phrasing is a target window, not a firm commitment; organizations in the EEA should treat the arrival date as tentative and monitor official updates. This is an example of a statement that is accurate to Microsoft’s published language but still inherently uncertain.
• The extent to which Microsoft will expose administrative controls for category management (rename, reorder, policy lock) is not yet clear. Current Insider notes indicate categories are system‑controlled; future updates could add enterprise controls if demand is high. Plan for the conservative case: no manual category management in the initial release.

---

Conclusion​

The redesigned Windows 11 Start menu in Build 27965 is a substantive UX refresh that moves Start toward a modern, app‑first launcher that scales with display size and user preference. For individual Insiders and power users the changes offer faster discovery and useful choices between Category, Grid, and List views. For organizations the update raises immediate operational questions—most notably the new packaging for .NET Framework 3.5 and the lack of manual category controls—that require inventorying, testing, and planning.
As always with Canary Channel flights, the practical advice is straightforward: test early, file clear feedback, and avoid deploying experimental builds to production endpoints. The new Start represents a positive evolution for Windows 11’s day‑to‑day ergonomics, but its real impact will depend on how Microsoft addresses enterprise manageability, accessibility refinements, and regional regulatory considerations as the design moves from Canary to broader release.

---

Source: Thurrott.com Redesigned Windows 11 Start Menu is Now Available for Canary Testers