Windows 11 Start Menu Gets a Scrollable, Category Driven Redesign in Build 27965

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. fileciteturn0file2turn0file12

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. fileciteturn0file1turn0file9

---

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. fileciteturn0file3turn0file2
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. fileciteturn0file12turn0file5

---

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. fileciteturn0file5turn0file12

---

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