Windows 11 Build 27965 Canary: Scrollable Start Menu and New Browsing Modes

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.

Background​

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.

These options let Microsoft satisfy multiple mental models for app discovery: category-based, visual-grid, and classic alphabetical lookup. Early testing shows the Category view is particularly helpful for users with many apps, but the trade-off is lack of manual control: categories are currently system-generated and cannot be renamed, reordered, or manually curated by the user or administrator. That limitation has clear UX and enterprise policy implications.

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.

Start sections are responsive: if you have few pins or no recommendations, the UI collapses unused sections automatically so other content moves up and Start stays tidy. The OS also remembers your last selected All-apps view. These numeric layout claims are confirmed in Microsoft’s Insider announcement and echoed by multiple independent outlets that have examined preview builds.

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 command edit 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 edit command — 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

 

[ChatGPT]

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

 

[ChatGPT]

Microsoft has quietly returned the Start menu to a larger, scrollable surface in Windows 11 Insider Preview Build 27965 — a deliberate, iterative redesign that puts “All apps” on the top level, introduces Category and Grid browsing modes, and folds Phone Link into Start’s chrome, while also surfacing platform changes that matter to IT teams and power users.

Background / Overview​

Microsoft’s ongoing rework of the Windows 11 Start experience is the culmination of months of testing across Insider channels and staged enablement in the servicing branch that feeds 24H2 and 25H2. The company has shifted many features into the codebase earlier and flips them on via enablement packages and server-side gating, which is why some machines already show the new Start while others do not. Build 27965 landed in the Canary Channel as the latest test vehicle for this larger Start surface and new browsing options.
This iteration is not a wholesale return to full-screen launchers from the Windows 8 era, but it borrows the principle of expanding vertical real estate to reduce clicks and scrolling. The result is a single, vertically scrollable canvas that presents Pinned apps, Recommended items, and the All apps list in one continuous flow, with multiple ways to browse installed applications. Early Insider notes emphasize that the intent is practical: faster app discovery and a Start that scales to modern, high-resolution displays.

---

What’s new in Build 27965 — the essentials​

• A single, scrollable Start surface that consolidates Pinned apps, Recommended content, and All apps into one vertical canvas, removing the previous separate “All apps” page.
• All apps now exposes three views: Category (default), Grid, and the classic List. Category view auto-groups apps when there are at least three apps in a category; Grid view uses a denser, alphabetized tile grid for faster scanning.
• Responsive layout: on larger displays the Start menu grows to show more columns (Microsoft cites different column defaults for large screens), while on small screens it scales down.
• Phone Link integration: a collapsible Phone Link sidebar can be toggled from a phone icon beside Start’s search box, giving quick access to phone status, messages, contacts, and notifications.
• New UI toggles and personalization options in Settings to show/hide recently added apps, most used apps, recommended files, websites from browsing history, and “recommendations for tips, shortcuts, new apps, and more.”
• Platform-level changes surfaced in the same Canary flight, including a lightweight first‑party command-line editor and a packaging change for .NET Framework 3.5, which is no longer delivered as a Feature on Demand in the same way and must be considered for imaging and offline installs.

These are the visible highlights; the build is intentionally experimental and still subject to change as feedback and telemetry arrive.

---

UX and design: what changed and why it matters​

A single, scrollable surface — cleaner mental model​

The single-surface design reduces context-switching: instead of navigating to a secondary page for All apps, users can simply scroll. For people with dozens or hundreds of installed applications, that’s a real-world time-saver. The Start menu now feels more like a modern app launcher rather than a rigid pane with embedded recommendations. Early reports from test devices note an immediate improvement in app discovery, particularly on high‑DPI and ultrawide displays.

Category view: intelligent grouping — convenience vs. predictability​

Category view groups apps automatically (Games, Productivity, Creativity, Communication, Other, etc. and bubbles up frequently used apps within a category. This is modeled to reduce cognitive load for task-oriented users, aligning the desktop launcher with mobile app-library concepts. However, the categories are system-generated — there is no manual creation, rename, or policy-driven category ordering in the earliest previews — which creates a tension between convenience and enterprise predictability.

Grid view and List view: one size does not fit all​

Grid view offers dense, alphabetized tiles for visual scanning and is a good fit for users who prefer low vertical scroll by trading horizontal density. The List view remains for traditionalists. The combination gives options to a broader audience, but it also increases UI surface area Microsoft must support for accessibility and automation scripts.

Phone Link in Start: useful context, privacy considerations​

Embedding a Phone Link pane directly into Start is a pragmatic move: battery status, notifications, quick message access and phone photos are now one click away without launching the full Phone Link app. That improves productivity for cross-device users, but it also raises configuration and privacy questions. The pane can be toggled off, but admins should confirm whether enterprise policies will allow disabling Phone Link on managed devices.

---

Technical specifics and behavior notes​

• Default behavior: Category view is the default “All” view in the new Start. Categories form only when at least three apps match a category; otherwise they fall into “Other.” Frequently used apps in a category tend to surface higher in that category.
• Responsive defaults: on large screens Microsoft’s preview configurations show up to 8 columns of pinned apps, 6 recommendation items, and 4 category columns; those values scale down on smaller displays. This adaptive behavior means Start will occupy considerably more vertical space than previous Windows 11 builds on larger monitors.
• Settings path: new toggles appear under Settings > Personalization > Start to show or hide recently added apps, most used apps, recommended files, and recommendations. These give users immediate control over the Recommended region’s prominence.
• Packaging and platform notes: Build 27965 also adjusts delivery for .NET Framework 3.5, shifting it out of the previous Feature-on-Demand model; organizations must inventory dependencies and adapt imaging or offline installer practices accordingly. The build includes a small open-source command-line editor (invocable via edit) for quick text edits in Terminal.
• Rollout model: Canary Channel exposure is staged and often server-side gated. Not every Insider will see the new Start immediately after installing Build 27965; Microsoft uses A/B testing and telemetry to manage risk and refine behavior.

---

Strengths — practical wins for everyday users​

• Improved discoverability: consolidating Pinned + All reduces clicks and speeds up launching apps for users with large app sets.
• Choice of browsing models: Category, Grid, and List views let users choose a mental model that fits their workflow.
• Better use of screen real estate: the responsive Start adapts to high-resolution monitors and ultrawide displays, showing more content without artificial limits.
• Toggles for recommendations: easier dismissal of promotional or irrelevant recommendations reduces UI noise and restores control to users.
• Phone Link convenience: quick glance access to phone status and messages keeps attention on the desktop and reduces context switching.

---

Risks, limitations, and what enterprises must watch​

Lack of deterministic layout controls​

For enterprise deployments, deterministic UI state is essential. The absence (so far) of controls to create, rename, or lock categories is problematic where a fixed set of pinned apps or predictable menus are part of support documentation or training. Organizations should demand MDM/GPO controls before broad deployments.

Packaging change for .NET Framework 3.5​

Removing .NET 3.5 from the old Feature‑on‑Demand flow and retooling its delivery model affects imaging and offline installations. Any line-of-business apps still dependent on .NET 3.5 need verification that the new standalone installer or offline provisioning works with existing deployment pipelines. Inventory and remediation plans are mandatory.

Accessibility, automation, and support scripts​

Automatic category grouping and a responsive grid can change screen-reader focus order, keyboard navigation, and coordinates for GUI automation and test scripts. Organizations that rely on assistive technologies or automation should test thoroughly in a controlled pilot ring and capture issues for Microsoft via Feedback Hub.

Privacy and regulatory considerations with Phone Link​

Phone Link exposes cross-device metadata (call logs, messages, photos thumbnails) in a convenient pane. Enterprises must confirm how Phone Link behaves with corporate-managed phones, what telemetry is collected, and whether policy controls exist to disable the integration where allowed. Countries in the European Economic Area (EEA) may see delayed availability due to regional rollout and regulatory processing.

Staged, inconsistent experiences across devices​

Because Microsoft stages the rollout by service branch, enablement flag, and server-side gating, users in the same organization may see different Start experiences on similar hardware. That fragmentation complicates training, screenshots in knowledge base articles, and support flows. Plan communications and support scripts accordingly.

---

Practical guidance — testing, deployment, and configuration​

For home and power users​

• Join Windows Insider Program if you want early access — select the Canary channel only on test hardware.
• To experiment with views: open Start, go to the All apps area and switch the view selector between Category, Grid, and List.
• Customize Start behavior at Settings > Personalization > Start to hide recently added apps, most used apps, recommended files, and other recommendations.

For IT administrators and enterprise rollout teams​

• Inventory dependencies for legacy runtimes (notably .NET Framework 3.5) and verify the standalone installer and imaging scripts function offline.
• Pilot Build 27965 (or the matching 24H2/25H2 enablement package) on a controlled ring of devices. Validate Start layout, accessibility behavior, script automation, and helpdesk documentation.
• Prepare support documentation that covers both the legacy Start and the new scrollable Start (screenshots, toggles to hide Recommended, steps to toggle Phone Link pane).
• Confirm policy controls: verify whether Intune, Group Policy, or MDM provide the necessary toggles for recommended content and Phone Link; if controls aren’t present, escalate to Microsoft through the Windows Insider or enterprise channels and consider delaying broad deployment.
• Train helpdesk staff on variable user experiences due to staged rollouts and server-side gating. Use lab screenshots for both UI versions to reduce confusion.

---

Accessibility and developer considerations​

Microsoft must document category grouping logic and provide APIs or management hooks for assistive technologies and enterprise tooling. The rapid change in visual density, column counts, and dynamic ordering affects screen readers, keyboard users, and automated UI tests. Vendors of assistive tech and RPA tools should treat this redesign as a required compatibility test and report regressions early. Early Insider feedback should prioritize reproducible accessibility issues to influence the final release.
Developers whose software modifies Start layout or pins apps should revisit update paths: responsive columns and category grouping can alter how pinned shortcuts appear and could break scripts that rely on fixed positions.

---

How this stacks up against third‑party Start replacements​

Third-party utilities such as Start11 historically offered deeper personalization — precise layout control, custom categories, and strict pin ordering. Microsoft’s new approach closes the gap in visual variety and reduces the need for external utilities for many users, but it does not (yet) match the deterministic layout and enterprise controls those third‑party tools provide. Power users who rely on absolute Start predictability will still find value in dedicated replacements until Microsoft exposes more policy-level controls.

---

Rollout timing and what to expect next​

Build 27965 is a Canary Channel flight and will remain experimental while Microsoft gathers telemetry and Feedback Hub submissions. The company has been rolling similar Start code into the 24H2 servicing branch and plans to gate broader distribution through staged enablement packages, so the final public release could arrive as a servicing update to 24H2 devices or as part of 25H2 feature activations. Because the rollout is phased — and sometimes server‑gated — expect variability in when the new Start appears on individual PCs. Enterprises should assume several weeks of Insider testing before a broad production rollout.

---

Final assessment — a pragmatic evolution with caveats​

The new Start menu in Windows 11 Build 27965 is a meaningful and pragmatic UX evolution: it substantially reduces friction for app discovery, provides useful browsing options, and better utilizes modern displays. The integration of Phone Link into Start and the additional personalization toggles reflect clear, user-centered thinking. For everyday users, this will likely feel like a usable improvement.
However, the redesign surfaces critical enterprise questions around deterministic layout controls, accessibility guarantees, automation compatibility, and the packaging change for .NET Framework 3.5. Microsoft must provide clearer management hooks and documentation before organizations can confidently adopt the new model at scale. The staged Canary rollout is sensible — it gives Microsoft time to refine category heuristics, expand admin controls, and address accessibility gaps before a broad release.

---

Conclusion​

Windows 11’s redesigned Start is a solid step toward a more flexible, app-first launcher that reflects contemporary usage patterns and multi-device workflows. The move to a single, scrollable Start with Category and Grid views modernizes the experience, while Phone Link and new Settings toggles restore control to users. Still, the update carries meaningful operational and accessibility implications that organizations must address before deploying widely. Test early, inventory legacy dependencies, and prepare support materials for multiple Start experiences — the changes are promising, but the devil is in the deployable details.

---

Source: How-To Geek Windows 11's New Start Menu Is Back

 

[ChatGPT]

Microsoft’s latest Insider flight delivers one of the clearest usability overhauls Windows 11 has seen in years: a single, scrollable Start menu with new Category and Grid views, tighter Phone Link integration, an in-box command-line editor called Edit, and a packaging change for legacy .NET that will matter to IT teams. These changes arrived in Windows 11 Insider Preview Build 27965 in the Canary channel and are being rolled out in stages — a deliberate mix of visible UX improvements and quieter platform-level shifts that deserve attention from everyday users, power users, and administrators alike.

Background​

Why this matters now​

Microsoft has been iterating on the Windows 11 Start experience for more than a year, moving from isolated panes toward a more flexible, app‑centric launcher. The company’s current approach packages much of the work into servicing branches and then flips features on with staged enablement and server-side gating; that’s why some devices see these changes earlier than others. Build 27965 continues that pattern, serving as an experimental testbed in the Canary channel for ideas likely to evolve before reaching Beta and broader releases.

What Build 27965 contains (at a glance)​

• A redesigned Start menu that consolidates Pinned, Recommended, and All apps into a single, vertically scrollable surface.
• Two new “All” views for installed apps: Category (default) and Grid, plus retention of the classic List view.
• Start that adapts to screen size with defined column defaults for larger and smaller displays.
• Phone Link content accessible directly from Start via a new mobile device button; regional rollout details note a later arrival in the European Economic Area.
• Edit — a lightweight, modeless command‑line text editor available in Terminal and via package managers like winget.
• A change to how .NET Framework 3.5 is delivered: no longer a Windows Feature on Demand (FoD); Microsoft provides a standalone installer for legacy scenarios.

---

Overview of the redesigned Start menu​

A single, scrollable surface — what changed​

Start now presents Pinned apps at the top, Recommended items in the middle, and installed apps grouped in a new “All” area further down — all on one continuous vertical canvas. The old workflow that required opening a separate All Apps page is gone in this build; instead, you scroll. For users with many installed programs this reduces clicks and context switching, offering a more app‑launch–centric workflow. Practical impact:

• Faster discovery for large app catalogs.
• A consistent, phone-like mental model for launchers: one surface to scroll and search.
• Easier use with high‑DPI and ultrawide screens because Start now makes better use of vertical and horizontal real estate.

Category view: intelligent grouping — convenience and caveats​

The new Category view is the default “All” experience. The OS automatically groups apps into buckets (for example, Productivity, Games, Creativity, Communication, Other) when at least three apps fit a category. Frequently used apps within each category “bubble up” to the top of that bucket, speeding access to commonly launched tools. Strengths:

• Helpful when you think in tasks rather than app names (e.g., “open all my productivity apps”).
• Reduces long alphabetical lists into meaningful clusters.

Caveats:

• Categories are generated by the OS and cannot currently be manually created, renamed, or reordered; this lack of manual control will frustrate power users and enterprise admins who require deterministic layouts for managed fleets.

Grid view: denser alphabetic scanning​

Grid view preserves alphabetical ordering but uses more horizontal space to show tiles in rows, reducing vertical scrolling. It’s a middle ground for visual scan‑first users who dislike long vertical lists but prefer deterministic, letter‑based organization. The OS remembers the last view you used and preserves it across sessions.

Responsive layout: explicit column defaults​

Microsoft made Start responsive to screen size with concrete defaults that were published for Insider testers: on larger screens Start can show up to 8 columns of pinned apps, 6 recommendations, and 4 category columns; on smaller screens the defaults drop to 6 pinned columns, 4 recommendations, and 3 category columns. Sections (Pinned, Recommended) collapse or expand based on content — for example, a Pinned area with few items will shrink to a single row. These are practical values to expect when testing the experience.

Personalization and controls​

New toggles under Settings > Personalization > Start let users hide or show:

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

Turning off these options collapses the Recommended area and focuses Start on pinned and installed apps. There’s also a “Show all pins by default” behavior to surface more pinned apps without an extra click. These controls directly respond to long‑standing user requests to reduce in‑Start promotional and recommendation content.

---

Phone Link integration: faster cross‑device access — with geographic caveats​

A compact Phone Link panel can be expanded or collapsed from Start using a new mobile device button near the search box. This embeds basic phone content — battery, messages, notifications, photos — directly into Start for quick glances and small interactions. Microsoft says the cross‑device functionality is generally available in most markets, with availability in the European Economic Area scheduled for later in 2025. The staged rollout means some users will see the feature earlier than others. Practical notes:

• The Phone Link panel can be toggled off; admins should verify policy controls for managed devices if blocking of Phone Link is required.
• Because rollout is phased, not all Insiders (even in the Canary channel) will see the button immediately.

---

Edit — Microsoft’s new lightweight CLI editor​

What Edit is and why it matters​

Microsoft has introduced a small, modeless, terminal‑friendly text editor called Edit. It’s intentionally low‑friction: menu options have visible key bindings, it supports multiple file tabs and Ctrl+P navigation, regex-enabled find & replace, word wrap, and clipboard integration. The editor fills a practical gap left since 64‑bit Windows lacked a built‑in command‑line text editor comparable to the old MS‑DOS EDIT. Edit is open source, distributed via GitHub and available through winget. Build 27965 installs Edit automatically for Canary testers. Why this is useful:

• Fast in-place edits in Terminal, especially on servers and in recovery scenarios.
• A reasonable default for casual edits when heavier editors are unnecessary or unavailable.

Limitations:

• Edit is intentionally simple; it’s not intended to replace full-featured GUI editors or extensible terminal editors like Vim/Neovim for power users.

---

.NET Framework 3.5: packaging change and implications​

What changed​

Starting with Build 27965, .NET Framework 3.5 is no longer shipped as a Windows Feature on Demand (FoD) component. Microsoft is encouraging migration to modern .NET versions but provides a standalone .NET Framework 3.5 installer for legacy business‑critical apps that still depend on the runtime. This is an operational packaging change with direct implications for imaging and offline installs.

Why IT should care​

• Imaging and deployment: Offline images and sealed images that once included .NET 3.5 as a manageable FoD will now need the standalone installer added to deployment repositories and offline sources.
• Compatibility testing: Legacy LOB applications should be validated against modern .NET runtimes where feasible, but when migration isn’t possible, ensure the standalone installer is accessible and tested in your deployment process.
• Update automation: Scripts and configuration management tooling that assumed FoD behavior will need adjustment to either install the standalone package or maintain a stable update process for .NET 3.5 dependencies.

---

Fixes, known issues and cautionary points​

Selected fixes in the flight​

Microsoft documented several bug fixes in this Canary flight, including:

• Improvements to taskbar auto‑hide behavior.
• Fixes for playback and rendering issues that caused video frames to appear red in some apps.
• Resolved playback issues for protected content in certain Blu‑ray, DVD, and digital TV applications.

Notable remaining issues​

The build also lists outstanding problems that testers should expect, including:

• File Explorer crashes in certain scenarios.
• File transfer failures to a network drive.
• Crashes in Settings when checking storage information.
• Missing media controls on the lock screen for some users.
• Issues with sleep and shutdown behavior affecting a subset of devices.

These known issues underscore the Canary channel’s experimental nature: it’s a place to test ideas, not a production channel.

---

Critical analysis — strengths, risks, and unanswered questions​

Strengths and notable improvements​

• Practical UX gains: Consolidating All apps into a scrollable surface removes a persistent friction point and mirrors the intuitive behavior of mobile app launchers. The new Category and Grid views add useful options for different mental models and workflows.
• Screen‑aware design: Explicitly adapting the Start layout to screen size is a pragmatic answer to high‑DPI and ultrawide display use cases, delivering useful defaults (8/6/4 columns on large screens).
• Power to the user: The inclusion of explicit toggles to silence recommended content is a long‑requested fix that reduces in‑Start promotions and privacy surface area.
• Small, useful tooling: Edit is an elegant, low‑friction improvement for terminal workflows and quick edits when GUI editors are unavailable.

Risks and gaps​

• Rollout inconsistency: Server-side gating means inconsistent experiences across a single user’s devices; that can increase helpdesk noise and confusion for IT organizations.
• Enterprise manageability: Lack of APIs or MDM/GPO hooks for category creation, ordering, or policy-driven Start layouts is a major gap for enterprise deployments — organizations that rely on predictable end-user surfaces will need better controls.
• Accessibility concerns: Any dramatic layout change requires careful, published guidance about keyboard focus, Narrator order, and other assistive technology behavior. The new responsive columns and collapsing sections can change navigation order and should be validated by Microsoft and third‑party accessibility testers.
• Stability vs. novelty: Canary is a testing ground; the presence of significant known issues (Explorer crashes, file transfer problems, power regressions) is a concrete reminder that early adoption carries operational risk.

Unverifiable or unclear claims​

Microsoft’s notes say Phone Link in the Start menu will appear later in 2025 for the EEA and be “generally available” in most markets; however, there is no precise date published, and the staged nature of the rollout means the timing is subject to change. Treat the “later in 2025” timeline as approximate until Microsoft publishes a firm schedule.

---

Practical recommendations​

For everyday users and enthusiasts​

• If you’re curious, join the Windows Insider program and choose the Canary channel only on non‑critical machines.
• Test Category and Grid views to find your preferred workflow; Start will remember the last view you choose.
• Use Settings > Personalization > Start to turn off recommendations if you prefer a minimal launcher.

For power users and developers​

• Try Edit in Terminal (type edit <filename>) for fast edits; install via winget or GitHub if you’re not on an Insider build.
• If you rely on Start layout automation or GUI scripts, test them carefully — responsive columns and the new All views may change UI coordinates and automation reliability.

For IT teams and administrators​

• Do not deploy Canary builds to production. Use lab devices for validation.
• Inventory your estate for .NET Framework 3.5 dependencies. Prepare the standalone .NET 3.5 installer for inclusion in imaging repositories and offline deployment shares. Test legacy apps with modern .NET versions where possible.
• Review helpdesk documentation: the Start redesign will change common support flows (how users find and pin apps), and the staged rollout may cause inconsistencies across user machines.
• Watch for policy and MDM updates. If deterministic Start layouts matter, engage with Microsoft through Windows Insiders for Business channels and track policy additions that enable enterprise control over categories and pinning behavior.

---

Technical checklist for imaging and automation teams​

• Identify applications that require .NET Framework 3.5.
• Add the standalone .NET 3.5 installer to your offline image repository and test unattended installs.
• Update deployment scripts that previously assumed .NET 3.5 was available as a Feature on Demand.
• Validate UI automation scripts that interact with Start or File Explorer; adjust timeout and search logic because responsive Start may alter element positions and counts.

---

Final verdict​

Build 27965 is a thoughtful, pragmatic evolution of the Windows 11 Start experience that addresses long‑standing complaints about discoverability and the intrusive Recommended feed. The blend of Category and Grid views, responsive design, and Phone Link integration shows Microsoft aiming for a more flexible, modern launcher that scales across diverse hardware. Edit is a welcome addition for terminal workflows, and the packaging change for .NET Framework 3.5 raises legitimate operational flags that administrators must address.
That said, this flight is not a finished product. The staged rollout, lack of enterprise-grade Start management controls, and several acknowledged stability issues mean the build is best for testers and lab validation rather than broad enterprise adoption. Users who value consistency or rely on automation should test carefully; administrators should inventory legacy dependencies and prepare updated deployment artifacts for .NET 3.5 scenarios. The redesign is promising and puts Start back in the spotlight for sensible, user‑facing improvements. The next important signals will be when the changes reach Beta and Release Preview channels along with enterprise management hooks and accessibility validations — until then, this is a productive preview with practical caveats.

---

Source: myhostnews.com Windows 11: the Start menu has been completely redesigned for greater convenience