• Thread Author
Microsoft's latest preview update for Windows 11 — KB5067036 — delivers the most significant Start menu overhaul since the OS launched, promoting a single, scrollable, and more adaptive Start experience that Microsoft says will make app discovery faster and more intuitive for both tablet and desktop users.

Windows-style Start Menu with pinned apps and categories on a blue gradient background.Background​

Microsoft has steadily iterated on the Windows 11 Start menu since the first release, moving away from the legacy two‑pane Start of Windows 10 toward a tile‑free, icon‑centric design. That evolution included minor UI tweaks, personalization options, and experimental builds in the Insider channels. With KB5067036 — published as a Release Preview / optional preview update on October 28, 2025 — Microsoft promotes a redesigned Start menu from testing into broader optional preview distribution for Windows 11 versions 24H2 and 25H2 (OS builds 26100.7019 and 26200.7019).
This update is delivered as an optional preview (Release Preview channel and optional Windows Update offering) and can be installed via Settings > Windows Update or by downloading the standalone package from the Microsoft Update Catalog. Microsoft and multiple industry outlets emphasize that feature rollouts remain staged, so installing the preview package does not guarantee immediate exposure to every new Start menu behavior — features are enabled progressively by Microsoft.

What changed: the redesigned Start menu (feature breakdown)​

Microsoft documents the redesign with a concise list of functional changes. The highlights are:
  • Scrollable “All” section on the main page: All installed apps appear at the top level via vertical scrolling rather than being hidden behind a separate All‑apps page. This eliminates the secondary navigation step that previously interrupted app discovery.
  • Multiple views — Category and Grid (plus List memory): The Start menu now supports at least two prominent browsing modes. Category view groups apps by functional category (Productivity, Games, Creativity, Communication, etc.) and surfaces frequently used apps in each bucket. Grid view shows apps alphabetically with more horizontal spacing for quicker scanning. The Start menu remembers the last view you selected.
  • Responsive, adaptive layout: The Start canvas adjusts to screen size. On larger displays, users will see more pinned apps, more recommendations, and broader category columns; on smaller screens the layout compresses to remain usable. Sections like Pinned and Recommended expand or collapse depending on content and available space.
  • Phone Link integration: A new mobile device button appears next to Search inside Start. Clicking it expands or collapses Phone Link content (your connected Android or iOS device info and interactions) directly inside the Start surface. Microsoft notes the feature supports Android and iOS in most markets and will roll out to the European Economic Area (EEA) in 2025.
  • Customizability and Settings: You can adjust the new Start behavior in Settings > Personalization > Start — including hiding the Recommended area to create a more compact experience. The Start menu remembers preferences like the last used view.
These are not superficial visual tweaks; the redesign is a rework of Start's interaction model — promoting discovery, grouping, and an at‑a‑glance mental model for app organization. Multiple independent outlets confirmed the same functional changes during the Insider and preview rollouts.

Why the redesign matters for Windows 11 users​

Short, practical benefits:
  • Reduce friction: By putting the All apps list at the top level and adding vertical scrolling, the Start menu cuts clicks and reduces context switching for users with many installed programs.
  • Faster scanning: Grid view and the more exportable column system on wider displays enable faster visual scanning of app icons and names.
  • Smarter organization: Category view can surface frequently used apps and group related programs together — a benefit for users who install many utilities or games.
  • Tighter mobile integration: Phone Link inside Start brings phone notifications and quick access into the same discovery surface where users find apps. This further positions Start as a single hub for launching and cross‑device interactions.
From a product design perspective, Microsoft is prioritizing discoverability and contextual relevance over the minimal icon grid of earlier Windows 11 builds. The change is particularly relevant for power users and those using large‑format monitors or mixed tablet/laptop devices.

How Microsoft is delivering the update and what to expect​

KB5067036 is an optional, non‑security preview update released on October 28, 2025 for Windows 11 versions 24H2 and 25H2. The package increments OS builds to 26100.7019 (24H2) and 26200.7019 (25H2). Install paths are:
  • Settings > Windows Update — check for updates; optional preview updates appear under "Optional updates available."
  • Microsoft Update Catalog — download and install the standalone MSU when you want manual control.
Microsoft explicitly states this is a preview update intended for broader validation before full optional distribution; as with prior preview updates, features are rolled out in waves under feature‑flighting mechanisms. Installing the package does not guarantee immediate activation of the redesigned Start; Microsoft enables features server‑side for subsets of devices as part of staged rollouts.
If you prefer to avoid preview packages, you can leave the "Get the latest updates as soon as they're available" toggle off in Windows Update, or hide the optional update with the Microsoft show/hide tool or by simply declining the optional update when it appears. The Microsoft support and community documentation explain that preview releases are optional and intended to be safe for broad testing, but they can include changes that are still under refinement.

Installing KB5067036 — step‑by‑step for power users​

  • Open Settings > Windows Update.
  • Click Check for updates. If the preview is offered, look for an "Optional updates available" link.
  • Choose KB5067036 or the listed Preview package and select Download & install.
  • Reboot if prompted. Some feature changes may only appear after sign‑out/sign‑in or after a phase‑in from Microsoft’s side.
  • To get the package manually, visit the Microsoft Update Catalog and download the MSU that matches your build and architecture. Manual installation may be preferred for lab testing or system imaging.
If the update fails to install, common troubleshooting steps are: disable "Get the latest updates as soon as they're available" and retry after a reboot, use the Windows Update Troubleshooter, or download the package and install it directly from the Microsoft Update Catalog. Microsoft community threads note that preview updates can sometimes be noisy on consumer machines; they are not required for security and can be skipped until the next cumulative update.

Hands‑on experience and early impressions​

Independent coverage from outlets that tested the preview reports a consistent experience: the Start menu feels more discoverable and less clicky for users with many apps. The new vertical canvas exposes more content at once and reduces the need to toggle between pages. On large monitors the Start can present several columns of pinned apps and categories at a glance; on small screens the layout compresses but still retains the single‑surface model.
That said, whether the Start menu feels "faster" in daily use depends on the device and the user. The perception of responsiveness will vary with CPU, GPU, system resource usage, and driver maturity. Reported user feedback during the Insider phase included praise for the grouping model and mixed responses from users who preferred the older, simpler grid-only approach. The ability to switch views and to hide Recommended provides options for different workflows, which helps mitigate the UX tradeoff.

Risks, caveats, and things to watch​

  • Preview status — expect rough edges: KB5067036 is released as a preview and still subject to refinement. Historically, preview cumulative updates can contain regressions or compatibility quirks on some hardware and driver combinations. Treat this update as optional if stability is critical.
  • Flighting and staggered rollouts: Installing the update may not immediately enable the full feature set because Microsoft uses staged enabling. Users who install early may not see changes until Microsoft completes feature flighting for their device cohort. This makes troubleshooting tricky: you may have the update installed but not the feature enabled.
  • Custom workflows may break: Power users with carefully curated Start layouts, third‑party Start launchers, or enterprise policies controlling Start behavior should test before broadly deploying. Group Policy and MDM settings that manage Start layouts could intersect unpredictably with the new adaptive layout, particularly in environments that rely on pinned app placements. If you manage devices in businesses, validate KB5067036 in pilot groups first.
  • Uninstall and rollback limitations: While optional preview packages can often be removed from Update history, cumulative updates that include servicing stack or component updates can complicate rollback. Use system restore points, backups, or test VMs for safe validation. Microsoft’s community guidance recommends hiding the optional preview if you want to avoid reinstallation loops.
  • Privacy and recommendations controls: The Recommended area and new personalized surfaces may show suggestions or file recommendations. Microsoft includes settings to hide or control recommendations, but administrators and privacy‑conscious users should review Settings > Personalization and related privacy pages after updating.

Enterprise and admin considerations​

IT administrators and deployment engineers must treat KB5067036 as a non‑security preview: it modifies UX and may change end‑user workflows.
  • Pilot first: Deploy to a pilot ring, observe telemetry and user feedback, then evaluate for broader deployment.
  • Group Policy/MDM: Verify that Start layout policies (pinned apps, layouts, and Start configuration) behave as expected with the new adaptive Start. Microsoft’s documentation and admin channels should be consulted for any policy changes tied to the redesign.
  • Imaging and provisioning: If you maintain golden images or provisioning packages, test the new Start behavior against your onboarding processes to avoid surprises.
  • Support channels: Be ready for increased support volume from users noticing differences in app discovery. Prepare KB articles and internal guides that show Settings > Personalization > Start paths and toggles for category/grid view and hiding recommendations.

Practical tips for end users​

  • To speed acceptance: try Grid view if you prefer alphabetical lists; Category view if you like grouped discovery. The Start menu remembers your last used view.
  • If you want the old behavior back temporarily: hide Recommendations and reduce pinning to approximate the prior minimal grid. You can also avoid installing the preview and wait for the feature to roll into a standard optional update.
  • For developers and app authors: confirm that your app’s install metadata (AppUserModelID, Start shortcut name, categories) is correct so Start’s categorization logic assigns your app to the intended bucket. Unclear or missing metadata can place an app into "Other" and reduce discoverability. This is a subtle but important implication of the new category grouping.

Cross‑checking claims and verifiability​

Microsoft's official KB article for KB5067036 provides the authoritative feature list and the build numbers for this preview release; independent reporting from technology publications and hands‑on coverage during the Insider and preview windows corroborate Microsoft’s changelog and user‑facing behavior. Key load‑bearing claims — the introduction of a scrollable All section, category and grid views, responsive layout changes, Phone Link integration, and the stated build numbers — are all confirmed by Microsoft’s support notes and multiple independent outlets that tested the preview.
Claims about subjective improvements in speed or responsiveness should be treated as experiential and hardware‑dependent: while the redesigned Start reduces steps and can feel faster for many users, explicit performance gains are situational and not universally guaranteed. This distinction is important when evaluating any headline that markets feature updates as inherently faster — real‑world results vary by device.

What this signals about Microsoft’s direction for Windows 11​

This Start menu redesign is consistent with Microsoft’s broader strategy for Windows 11: make the OS more adaptive across device classes, emphasize discoverability, and integrate cross‑device features (like Phone Link) more tightly into core UI surfaces. The move toward categorized app shelves and server‑side feature flighting signals a continued shift to iterative, phased feature delivery instead of monolithic yearly OS revisions.
Expect more of these incremental UX experiments to emerge in preview rings before broader rollouts. Microsoft’s approach reduces the blast radius of big changes but increases the need for organizations and enthusiasts to actively test preview packages if they want to be early adopters.

Final verdict — practical recommendation​

KB5067036 delivers a meaningful, well‑scoped redesign to the Windows 11 Start menu that should improve app discovery and modernize the Start interaction model for many users. For enthusiasts, power users with large app libraries, and those who rely on Phone Link, the new Start is a tangible productivity gain. For enterprises and stability‑sensitive environments, treat the update as a preview: pilot carefully, validate MDM/Group Policy interactions, and deploy broadly only after confirming no regression in your environment.
If you want the redesigned Start now, install KB5067036 from Settings or the Microsoft Update Catalog and be prepared to wait for Microsoft’s staged enablement; if you prefer to avoid preview behavior, wait for the feature to arrive through standard cumulative updates in the coming months.

The Start menu has been a defining element of Windows for nearly three decades; with KB5067036 Microsoft is not merely polishing visuals — it’s rethinking how users discover and launch apps. The result is a more dynamic, device‑aware Start that aligns with modern desktop and mobile usage patterns — and one that will be worth testing for anyone who spends time curating and launching applications on Windows 11.

Source: Windows Report Windows 11 Start Menu Gets a Major Redesign in KB5067036
 

Four years after Windows 11 first rearranged a familiar piece of Windows UI, Microsoft has quietly — and finally — fixed what a lot of users called the Start menu's most annoying friction: the need to click a separate “All” page to see every installed app. The Start menu now exposes a true “All apps” experience on the main page with three browsing modes — Category, Grid, and List — and gives you the option to collapse the Recommended area entirely so your full app list sits immediately under your pinned shortcuts. This redesigned Start is shipping as part of the October 2025 optional update (KB5067036) for Windows 11 and is also discoverable now via community tools; the official update shows the feature controlled by gradual rollout and user device factors.

A light blue Windows-style launcher with a search bar and grid of pinned apps.Background​

When Windows 11 launched, Microsoft introduced a visually cleaner Start menu but moved some long-standing ergonomics — notably the complete, always-visible alphabetical app list — behind a second tap. Power users and long-time Windows users complained that the extra click and extra page broke fast keyboard-centric workflows and discoverability. Over subsequent Windows 11 builds Microsoft iterated on visual density, pinned layout, and recommendations, but the “All apps” workflow remained a pain point for many. The October 2025 update is the first widely available change that addresses that complaint directly by making the entire app inventory accessible from the main Start surface and by adding new presentation modes to suit different users and screen sizes.

Overview of what changed​

The refreshed Start menu introduces three meaningful changes that matter to everyday users:
  • A scrollable “All” / All apps section visible on the main Start page so you no longer have to open a separate page to see every installed program. This makes launching apps faster and removes an extra click for the common “open app X” workflow.
  • Three presentation modes for apps in the All section:
  • Category view — apps are grouped by category automatically and surface frequently used apps inside groups.
  • Grid view — an information-dense, multi-column alphabetical grid that maximizes visible apps at a glance.
  • List view — a compact alphabetical list for classic vertical scanning.
    The OS remembers the last view you used.
  • The Recommended section can be hidden via Settings so that your installed-apps area takes priority in the Start layout. When Recommendations are disabled, the installed apps list appears directly under pinned apps; when Recommendations are enabled, the app list sits below them. Several toggles in Settings > Personalization > Start control the Recommended content.
Those are the visible changes; under the hood Microsoft built the Start surface to be responsive — sections collapse and expand based on available content and screen real estate — and added hooks for future companion features (Phone Link integration is represented by a separate mobile device button). Feature availability is gated by phased rollout logic, so not every eligible device will see the UI immediately.

How to tell if your PC already has the new Start​

  • Check your Windows build level. Press Windows+R, type winver, and hit Enter; the dialog shows your current Windows build number. The new Start is tied to builds 26100.7019 and 26200.7019 (the October 28, 2025 optional/preview release) for Windows 11 versions 24H2 and 25H2. If your build number is at or above those numbers you have the necessary bits for the new Start — but Microsoft still controls whether it’s visible on a per-device basis.
  • Install the optional preview update (KB5067036) via Settings → Windows Update → Check for updates → Optional updates. Microsoft is shipping KB5067036 as a preview/non-security rollup with a gradual rollout mechanism; installing it gives your machine the updated Start infrastructure used in the rollout.
If you already have a recent 24H2 or 25H2 build and the Start has not changed, that’s expected: Microsoft is using staged rollouts that gate features by device, region, or other telemetry signals. The alternative is to enable the UI yourself using community tools, which is where ViVeTool comes in — but that approach is unsupported by Microsoft and carries risk.

Step‑by‑step: how to enable the new Start now (official route)​

  • Open Settings → Windows Update → Check for updates and install any available optional updates. Look specifically for the October 2025 preview (KB5067036) that updates to builds 26100.7019 / 26200.7019.
  • After installing, restart the PC and click Start. If the new Start is enabled for your device, you’ll see the updated layout with a scrollable All section and the new view controls. If the layout hasn’t changed, Microsoft’s rollout hasn’t reached your device yet.
This is the safest option: you get the feature on Microsoft’s terms, and you maintain support and stability guarantees associated with standard updates. The update includes many other fixes and features (File Explorer tweaks, battery icon changes, administrative protection, and more), so read the update notes if you need to know what else will change on your devices.

How to enable the new Start immediately using ViVeTool (community method)​

If you’re impatient and understand the risks, members of the Windows enthusiast community have been using ViVeTool to flip Start feature flags on devices that already have the requisite update installed. The common set of commands posted and used across community forums is:
  • Download the ViVeTool release from its official GitHub releases page and extract it to a convenient folder (example: C:\ViVe). Make sure you download the release matching your CPU architecture. ViVeTool v0.3.4 or later contains updated feature dictionaries for recent builds.
  • Open an elevated Command Prompt (right-click → Run as administrator) and change directory to the ViVe folder:
    cd C:\vive
  • Run the commonly shared enable command:
    vivetool /enable /id:57048231,47205210,56328729,48433719
  • Restart your PC. The new Start should appear when you open the Start menu.
Important notes and caveats about this method:
  • Those numeric IDs are community‑discovered flags that map to Microsoft feature gates; they are not an official API and Microsoft does not document a public mapping of IDs to features. That means the exact set of IDs needed can change between builds. Treat these IDs as community pointers, not official knobs. This is an unverifiable mapping unless Microsoft publishes the mapping. Use caution.
  • ViVeTool modifies internal feature state; running it is essentially flipping experimental flags on your release installation. This is unsupported by Microsoft. Expect that some features might behave oddly, that certain components may be missing, and that you could encounter regressions. Community reports include Start search input failing and Start not opening after enabling certain flags. Back up your system and create a restore point before experimenting.
  • If something goes wrong you can flip the flags back with vivetool /disable /id:... and restart, or uninstall the preview update via Settings → Windows Update → Update history → Uninstall updates. Some users report needing to roll back the update to fully revert behavior.

Exactly what toggles control the Recommended section​

Microsoft built explicit toggles inside Settings → Personalization → Start to control Recommended content. The key items you can disable are:
  • Show recently added apps
  • Show recommended files in Start (and related File Explorer recs)
  • Show websites from your browsing history (where applicable)
  • Show recommendations for tips, shortcuts, new apps, and more
If you switch these off the Recommended area collapses and the installed apps list moves up, giving you immediate access to all installed programs beneath your pinned apps. This is the recommended adjustment for users who prefer a direct All-apps-first workflow.

Troubleshooting and rollback​

When you enable features by flipping hidden flags you need a rollback plan. Here’s a pragmatic checklist:
  • Create a System Restore point and an image backup before you begin. If your device supports Reset or you use enterprise imaging, ensure those recovery paths are current.
  • If Start behaves oddly after enabling flags:
  • Run vivetool /disable /id:57048231,47205210,56328729,48433719 (or the IDs you used) and reboot.
  • If disabling flags does not restore normal operation, uninstall the KB preview via Settings → Windows Update → Update history → Uninstall updates and reboot.
  • If search in Start stops accepting input (a community-reported symptom), disabling the Start flags has been reported to restore search behavior for some users. Community threads also document other remedies such as restarting Windows Search or re-registering Start/Search components, but results vary. Backups protect you from prolonged troubleshooting.

What to expect functionally and visually​

  • Grid view: This is the most information-dense option and is ideal for users who rely on quick visual scanning and want more apps on-screen at once. On large monitors expect more columns and more items per row.
  • Category view: Windows auto-groups apps by category when there are at least three apps in that category. This is useful for users who prefer topic-first browsing but also limits manual organization — you cannot (yet) manually create or move category groupings.
  • List view: Classic alphabetical vertical scanning for users who prefer the old-style All apps list.
The Start menu now adapts to your available pins and recommendations. If you only have a few pinned apps the Pinned area will shrink and the installed apps or Recommended areas slide up accordingly. The Start menu remembers your last chosen All view and restores it on subsequent opens.

Security, support, and enterprise considerations​

  • ViVeTool and community flag-flipping are unsupported in corporate environments. IT departments should not use community feature IDs on production-managed endpoints. Enterprises should wait for Microsoft’s controlled rollout or validate features in test rings and through official servicing channels.
  • Because KB5067036 is an optional, non-security preview update, enterprises that follow controlled servicing should evaluate it in a lab or pilot ring before broader deployment. The update contains multiple unrelated changes (Copilot integrations, File Explorer tweaks, Administrator Protection previews) that should be validated together.
  • Microsoft’s gradual rollout means that not all devices will see the new Start even after the KB is applied; telemetry and gating decisions may vary by region and device configuration. For managed fleets, use Microsoft’s official release-health dashboard and update channels to plan migrations.

Why this matters: practical benefits and trade-offs​

Benefits:
  • Fewer clicks and faster app launch: Putting All apps on the main page reduces friction for keyboard and mouse users alike.
  • Better density choices: Grid and list modes allow you to choose a layout that matches your workstyle — dense grids for power users, lists for legibility.
  • Cleaner control over recommendations: Users who value a consistent app-first layout can hide recommendations rather than tolerate an ever-shifting “Recommended” area.
Trade-offs and risks:
  • Feature flip volatility: The new Start is rolling out and will still evolve; features like automatic category grouping may be refined or altered. Users who rely on precise Start behavior (e.g., accessibility workflows) should validate the UI before committing.
  • Unsupported toggles: Using ViVeTool can introduce instability and is outside Microsoft support. Community-discovered IDs are brittle across builds. Proceed with caution and back up.

Smart checklist before you try anything​

  • Verify your build with winver; confirm you are on or above build 26100.7019 / 26200.7019.
  • Create a full system backup or at least a System Restore point.
  • If you are in an enterprise, test on a non-production machine or in a controlled test ring.
  • Prefer the official update route (KB5067036) if you want minimal risk.
  • If you use ViVeTool, download the binary only from the official GitHub releases, run it from an elevated prompt, and be prepared to disable the IDs or uninstall the preview if things go wrong. ViVeTool v0.3.4 is the current recommended community build for recent Windows 11 releases.

Final analysis: why Microsoft likely made this change, and where Start goes next​

This redesign signals a pragmatic course correction. Windows 11’s initial Start focused on aesthetics and surfacing dynamic recommendations, but users consistently asked for speed and predictability. Restoring instant access to a full app inventory — while offering modern views and responsive layout — balances the original vision with practical convenience. Doing so in an opt-in preview and via gradual rollout helps Microsoft gather telemetry across device classes before committing to a wider release.
Looking ahead, expect Microsoft to iterate on category grouping (potentially adding manual controls or smarter ML grouping), deepen Phone Link and cross-device experiences in Start, and refine accessibility behavior to ensure keyboard-first and screen-reader workflows remain fast and predictable. Enterprises should watch the telemetry-driven rollout and stage adoption carefully. Enthusiasts who prefer the fastest route can experiment with ViVeTool now, but they should also assume they may encounter teething problems and may need to revert changes if their workflows rely on a stable Start/Search combination.

The new Start delivers a long-requested convenience: all your apps, reachable from a single surface, in a layout you can tune. The official path is to install the October 2025 preview (KB5067036) and wait for Microsoft’s phased rollout; the community path via ViVeTool exists and works for many, but it is unsupported and can introduce instability. For most users the recommended route is the update — for power users who test and back up, ViVeTool provides early access to the reworked experience.

Source: theregister.com How to get the new Windows Start menu now
 

Microsoft has quietly rebuilt the Start menu in Windows 11, replacing the old two‑pane launcher with a single, vertically scrollable surface, adding three distinct “All apps” views (Category, Grid, and List), tighter Phone Link integration, and new personalization toggles — delivered as an optional preview in KB5067036 and rolled out via staged enablement so not every PC will see it at once.

A desk monitor displays a Windows-style app grid with a search bar.Background / Overview​

Microsoft’s redesign addresses one of the most persistent criticisms of Windows 11’s original Start layout: the split between Pinned shortcuts and the separate All apps page, plus the prominence of the Recommended feed. The new model promotes a single, continuous Start canvas where pinned apps, recommendations (if enabled), and the full installed‑apps inventory live in one vertical scroll. That single surface is paired with three browsing modes so users can choose what matches their workflow: Category (auto-grouped buckets), Grid (denser, alphabetized tiles), and List (classic A–Z).
This update is distributed as part of a non‑security, optional preview package labeled KB5067036, released into Release Preview and staged for broader rollout. Microsoft ships the binaries in servicing updates but flips feature flags progressively — which means installing the KB may not immediately expose the redesign until Microsoft enables the feature for a device. The preview contains related UI polish (taskbar and File Explorer tweaks), on‑device voice improvements, and Copilot/Copilot+–adjacent features that appear in the same servicing drop.

What changed: concrete details​

Single, scrollable Start canvas​

  • The Start menu is now a single, vertically scrollable surface that places the full app list on the main page instead of hiding it behind a separate “All apps” page.
  • Pinned apps and recommendations (when enabled) sit in the same continuous surface above or alongside the app list, depending on your display size and layout choice.
This change eliminates the extra click or page hop many users complained about and better matches the mental model used by modern mobile launchers and many third‑party PC launchers.

Three browsing modes: Category, Grid, List​

  • Category view auto‑groups apps into functional buckets such as Productivity, Games, Creativity, and Communication. Frequently used apps are surfaced within those groups. This is designed for task‑oriented discovery when you don’t remember exact names.
  • Grid view preserves alphabetical ordering but increases icon spacing and panel size, optimizing for quick visual scanning on wider displays.
  • List view provides the compact, keyboard‑friendly A–Z vertical list familiar to long‑time Windows users. The OS remembers your last selected view and restores it on subsequent opens.

Phone Link panel inside Start​

A new Phone Link (mobile device) button appears beside the Start search area and expands a collapsible panel inside Start that surfaces recent calls, messages, photos, and basic phone controls for paired Android or iOS devices. This folds common phone‑to‑PC continuity tasks into the primary launcher. Availability and exact capabilities depend on region and device pairing.

Personalization and toggles​

Microsoft added explicit toggles in Settings > Personalization > Start to control:
  • Show recently added apps
  • Show most used apps
  • Show recommended files (Recommended area)
  • Show websites from browsing history / web suggestions
  • Phone panel visibility
If you prefer a minimal, distraction‑free Start, you can use these switches to hide recommendations and reduce the UI to pins + app list only.

Responsive layout and density behavior​

Start adapts to screen size and DPI. On larger displays the menu surfaces more pinned columns, more recommendations, and additional category columns; on smaller devices it scales down to remain usable. There’s also a “Show all pins by default” behavior so you can surface every pinned item without additional clicks.

How Microsoft is delivering and why rollout matters​

  • The redesign is packaged as part of KB5067036 (an optional preview / Release Preview drop) and corresponds to specific servicing builds for Windows 11 24H2 and 25H2.
  • Microsoft uses staged enablement (server‑side feature gating / A/B testing) to flip the redesign on for subsets of devices after monitoring telemetry. Installing the KB does not guarantee immediate exposure.
  • Devices opted into “Get the latest updates as soon as they’re available” are more likely to receive the preview earlier. Community tools (e.g., ViVeTool) have been used to accelerate access, but those methods are unofficial and carry risk.
This delivery model protects broad compatibility but creates an uneven experience: technicians and enthusiasts may see changes before the majority of users, and administrators must treat this as a staged feature that needs pilot testing before broad deployment.

Usability gains — where Microsoft fixed long‑standing friction​

  • Fewer clicks: Placing the full app list on the main Start surface removes the extra step to reach All apps. That single change speeds the common “open app” flow for users with large app catalogs.
  • Better scanning: Grid view and the responsive column behavior make Start more scan‑friendly on ultrawide and high‑DPI displays.
  • Task discovery: Category view helps users who think in tasks (e.g., “open something for photo editing”) rather than exact app names.
  • Control over noise: Explicit toggles let people hide Recommended content entirely, restoring a deterministic, app‑centric launcher experience.

Remaining friction points and technical caveats​

Search and indexing remain the wild card​

When Windows search and the indexer are functioning, Start can act as a fast command palette. When the indexer “tumbles” (index corruption, delayed indexing), search results slow and the Start key becomes less responsive for typed launches. The redesign doesn’t solve inconsistent search/indexer performance on affected machines; the indexer and Windows Search service still determine the speed and reliability of typed queries. Administrators and power users should monitor indexing health and be prepared to rebuild or tune search settings where necessary.

Feature flags and policy controls​

  • Because Microsoft enables the redesign via feature flags, enterprise imaging and update testing must include checks for feature exposure. IT teams cannot assume installing KB5067036 will flip the redesign for every device; targeted pilot rings are still the recommended approach.
  • Group Policy and MDM controls may be used to disable recommendation features and set Start behavior for managed machines, but administrators should verify behavior on the specific builds they deploy.

Privacy and telemetry considerations​

Phone Link integration and Recommended content surface cross‑device and recent file data inside Start. Administrators and privacy‑conscious users should review pairing permissions, telemetry settings, and the new personalization toggles to ensure nothing unwanted is being surfaced in shared or public‑facing workstations. The ability to hide recommendation content mitigates exposure of recent files if that is a concern.

The staged rollout means inconsistent exposure​

Because the rollout is A/B gated, device fleets will likely have a mixture of old and new Start behaviors during the transition period. This can impact helpdesk scripts, training materials, and screenshots used in documentation. Prepare staff for both experiences during pilots.

How to get the new Start (practical steps)​

  • Opt in to preview updates if you want early access: Settings > Windows Update > Get the latest updates as soon as they’re available (toggle).
  • Check Windows Update for the optional preview labeled KB5067036 (October preview / Release Preview drop) and install it. Reboot after installation. Expect some devices to still not show the redesign immediately because of staged enablement.
  • If the change doesn’t appear and you’re comfortable with community methods, some enthusiasts use feature‑flag tooling to enable the redesign sooner, but those approaches are unsupported and can introduce instability. Proceed only in test environments.
To disable recommendation and reduce distractions: Settings > Personalization > Start, then turn off Recent apps, Recommended files, Most used apps, and the Phone panel if desired. This will shrink the Recommended area or hide it completely, restoring a more classic, app‑first start surface.

Comparison with third‑party Start menu alternatives​

Many power users still prefer third‑party Start replacements because they offer deterministic layouts, legacy affordances, and deeper customization that matches long‑established muscle memory.
  • Start11 (Stardock) — Restores a classic two‑column Start layout, with extensive size, spacing, icon and right‑click behavior controls. It’s polished and paid, aimed at users who want consistent Windows 7–style workflows.
  • StartAllBack — Focuses on precise taskbar and legacy UI control, attractive for users who want the pre‑Windows 11 look and feel with modern compatibility.
  • Open‑Shell — The open‑source alternative for users who prefer a free, classic‑style menu with community‑driven customizations.
Why people stick with third‑party options:
  • Predictable, configurable layouts that don’t change with staged Microsoft feature flips.
  • Restored jump lists, nested folders, and keyboard/workflow optimizations tuned to power‑user habits.
  • Centralized configuration export/import for fleet standardization in managed environments.
The redesigned native Start narrows the gap: it fixes the All‑apps friction and offers layout choices, but mature third‑party menus still win on deep customization and predictability for power and enterprise users.

Enterprise and IT implications​

  • Testing posture: Treat KB5067036 as a feature preview. Pilot across a representative sample of hardware and software configurations before broad deployment. Staged enablement may complicate validation because some pilot devices could remain on the old Start while others switch.
  • Documentation & training: Prepare dual helpdesk guides and screenshots, since some users will be on the old Start during the phased rollout. Standardize recommended toggles for managed devices (e.g., hiding Recommended files) to keep a consistent experience.
  • Configuration management: Where uniformity is essential, consider validated third‑party Start solutions that support export/import of configuration to guarantee consistent menus across fleets. These tools can reduce training overhead for legacy power users.
  • Security & privacy: Review Phone Link pairing policies and telemetry/privacy settings before enabling Phone Link panels in shared or regulated environments. Personalization toggles can be used to limit exposure of recent files and web suggestions.

Risks, limitations, and unverifiable claims​

  • The rollout timing and exact build exposure are controlled by Microsoft’s staged flags; while KB5067036 is documented as the preview package that contains the redesign, the timing for each tenant and device is not deterministic and can change. Treat any claim of “everyone will see it on date X” as tenuous until confirmed in your specific environment.
  • Some public writeups mention region gating (e.g., EEA differences for Phone Link) and hardware gating (Copilot+ device dependencies for AI features). Those constraints are productized and may vary by licensing, hardware, and local regulation — administrators should validate behavior in their region.
  • Search/indexer behavior is still dependent on the Windows Search service and indexing health. Reports indicate the new Start improves layout friction, but it does not fix indexing‑related search slowdowns — that remains a separate subsystem to monitor and troubleshoot.

Practical recommendations (for everyday users and admins)​

  • If you run a personal device and want the new Start, opt into preview updates, install KB5067036, and be patient — the feature may still be gated for your device. Use the Start personalization toggles to remove recommendations if you prefer a leaner UI.
  • If you rely on predictable, keyboard‑centric workflows (power users), test the new views (List vs Grid vs Category) but keep your third‑party Start option handy until you verify the new cadence matches your muscle memory. Many users find the native redesign helpful; others still prefer Start11 / StartAllBack for consistency.
  • IT teams should pilot KB5067036 on a small, representative set of devices and verify search/indexing behavior, Phone Link pairing behaviors, and Group Policy/MDM interactions before a wider roll‑out. Document a rollback path and prepare training materials that cover both legacy and redesigned Start experiences.

Outlook: why this matters​

This redesign is Microsoft’s most meaningful Start menu change since Windows 11’s initial rearrangement. It restores a core expectation — quick, single‑surface access to all installed apps — while offering multiple views to suit different workflows and displays. For many users, this will be the first time Windows ships a default Start that balances visual minimalism with practical discoverability. For enterprises and power users the ecosystem remains healthy: Microsoft provides better default ergonomics, while third‑party tools still deliver deeper, deterministic control when needed.
The staged rollout model is a double‑edged sword: it reduces the risk of large regressions in production fleets but complicates adoption planning and makes visibility uneven across user populations. The safest path for organizations is the usual one: pilot, validate, define desired toggles (especially around Recommended content and Phone Link), and then scale once telemetry and user feedback are satisfactory.

Microsoft’s redesigned Start does not radically rediscover the OS, but it pragmatically addresses a long‑running UX complaint with a combination of single‑surface navigation, multiple view modes, and more explicit personalization controls — and that alone will be a material quality‑of‑life win for millions of Windows 11 users once it finishes staged rollout.

Source: findarticles.com What changed in Windows 11’s redesigned Start menu
 

Windows-style start menu with pinned apps on a blue abstract wallpaper.
Microsoft has quietly delivered the most consequential redesign of the Windows 11 Start menu since the operating system launched — a single, vertically scrollable launcher that promotes the full “All apps” list to the main surface, adds multiple presentation modes (Category, Grid, and the retained List), folds a Phone Link panel into the Start chrome, and arrives as part of an optional, staged preview packaged under KB5067036.

Background / Overview​

Windows’ Start menu has been the most visible and emotionally charged piece of desktop UI for decades. Windows 11’s original centered layout traded dense discoverability for a cleaner look, separating Pinned shortcuts from the complete alphabetical All apps list and elevating a Recommended feed — choices that many users praised aesthetically but criticized for extra clicks and reduced efficiency. Microsoft responded by iterating in the Insider channels for months, and those experiments have now been folded into an optional preview release identified as KB5067036 for Windows 11 versions 24H2 and 25H2.
The rollout model Microsoft is using is important to understand: the preview packages deliver the updated binaries, but the redesigned Start experience is activated through staged, server‑side enablement (feature flags). That means installing KB5067036 may place the necessary files on your PC, but Microsoft may not enable the UI until your device is included in the staged activation group. This conservative approach reduces risk for Microsoft but means visibility will be inconsistent across users for a time.

What’s new (feature breakdown)​

Single, scrollable Start surface​

The most visible change is structural: the Start menu is now a single, vertically scrollable canvas that can present Pinned apps, Recommended content (if enabled), and the full installed-apps inventory on the main surface. The redesign removes the older two-step pattern — open Start, then open All apps — and replaces it with a mobile-style app drawer where everything is discoverable by a single scroll. This was a core goal for Microsoft: reduce friction when launching apps, especially for users with long software catalogs or those on touch devices.
Practical benefits:
  • Fewer clicks to reach infrequently used apps.
  • Better use of vertical space on high‑DPI and ultrawide displays.
  • A unified mental model for launching apps and accessing recent files.

Multiple app presentation modes: Category, Grid, List​

The Start menu now supports multiple ways to browse installed apps:
  • Category view — Apps are automatically grouped into topical buckets (for example: Productivity, Games, Creativity, Communication). Frequently used apps “bubble up” within each category, aiming to accelerate task-oriented discovery.
  • Grid view — An alphabetized grid with wider horizontal spacing for quick visual scanning; useful on larger monitors.
  • List view — The traditional A→Z list remains available for keyboard-driven power users.
The menu remembers the last view you selected and restores that preference on the next open. This choice gives users flexibility: contextual discovery with Category, dense scanning with Grid, or predictable ordering with List.

Customization and hideable sections​

Responding to long-standing user demand, Microsoft added explicit toggles under Settings → Personalization → Start to control:
  • Show recently added apps
  • Show most used apps
  • Show recommended files / recommendations
Users can hide the Recommended area entirely, collapse the Pinned grid, or choose to show all pins by default. These options let people who prefer a minimalist launcher restore a distraction‑free layout quickly.

Phone Link integration inside Start​

A new mobile-device button appears beside Start’s search. Clicking it opens a collapsible Phone Link panel embedded into the Start surface that shows recent messages, missed calls, notifications, and quick-photo access from a paired smartphone. Microsoft specifies the integration works for Android and (in most markets) iOS, though some regional gating is in effect. This folds basic phone continuity tasks into the primary launcher without forcing a separate app window.

Taskbar and polish: smoother animations and battery percentage​

The KB preview bundled with the Start redesign also includes subtle taskbar refinements — smoother hover animations for app thumbnails, a redesigned battery icon that can always show percentage, and other small quality‑of‑life changes intended to make day‑to‑day multitasking feel snappier. These are visible but incremental; together they lend the refreshed shell a more cohesive, modern feel.

Availability and rollout: KB5067036 and staged enablement​

What is KB5067036?​

KB5067036 is the non-security, optional preview update Microsoft released in late October 2025 that packages the redesigned Start menu and a set of adjacent UI and platform improvements for Windows 11 builds 26100.7019 (24H2) and 26200.7019 (25H2). The Microsoft support page lists the Start menu redesign explicitly among Windows 11 PC experiences delivered in that preview.

Who sees it first?​

Microsoft’s staged rollout prioritizes devices that have opted into receiving updates early — for example, users who enabled “Get the latest updates as soon as they’re available” in Settings → Windows Update and Release Preview/Insider channels. Even after you install the KB, the experience may not appear immediately because activation is controlled server‑side. Expect broader visibility as Microsoft expands the stage-gated rollout and includes the feature in forthcoming Patch Tuesday cumulative releases.

How to check whether you have the bits​

  1. Press Windows+R → type winver → Enter.
  2. Look for build numbers 26100.7019 or 26200.7019 (or later). If your build is at or above those numbers, the required binaries are likely present, but the UI may still be disabled by Microsoft for your device.

How to try the redesigned Start menu now​

Microsoft’s supported path:
  1. Open Settings → Windows Update → Check for updates.
  2. Under Optional updates, install the preview labelled KB5067036, or install via the Microsoft Update Catalog if you prefer manual control.
  3. Reboot. If the Start redesign doesn’t appear immediately, wait — feature activation can be server‑gated.
An alternative (unsupported) method:
  • Community tools such as ViVeTool can force-feature flags locally once the preview bits are present. The typical steps reported by multiple outlets are: install KB5067036, obtain ViVeTool from GitHub, run an enable command for the relevant feature IDs, and reboot. This approach lets enthusiasts get the UI immediately but is unsupported by Microsoft and can complicate future updates or troubleshooting. Use it only if you accept the risk. 
Warning: activating server‑gated features locally can hide telemetry used in Microsoft’s staged rollout tests and may make your machine behave differently than standard configurations. Enterprises should avoid unsupported methods.

Hands‑on expectations and initial impressions​

Early hands‑on reviews and insider reports paint a consistent picture: the new Start is faster to scan, especially on devices with many installed apps; the Category view is useful for task-based discovery; Grid view offers efficient horizontal scanning on widescreens; and hiding the Recommended area restores an app-first launcher that many long-time Windows users craved. However, some users may find the single-surface approach denser than before and may need time to adapt muscle memory.
Notable UX points:
  • The Start menu remembers your last chosen view, which helps continuity between sessions.
  • Categories are generated automatically when the OS detects enough related apps; users cannot (as of the preview) create custom categories manually.
  • The responsive layout adjusts pins and category columns to screen real estate; larger monitors may show up to eight columns of pinned apps and multiple recommendation slots.

Critical analysis — strengths​

  1. Real, measurable discoverability gains. Elevating the All apps list to the top surface cuts clicks and mirrors UX patterns users already understand from phones and many third‑party launchers. This is especially helpful for users who maintain large app inventories.
  2. Choice without clutter. By offering Category, Grid, and List views and explicit toggles for recommendations, Microsoft has struck a pragmatic balance between personalization and simplicity. Power users can keep a compact alphabetical list; casual users can lean on categories.
  3. Better use of modern hardware. The responsive canvas makes the Start menu scale with monitor size and DPI. For users on ultrawide or 4K screens, the new layout avoids wasted whitespace and offers more immediate app targets.
  4. Cross-device continuity is closer to the desktop. Integrating Phone Link into Start reduces context switching. Basic phone tasks (messages, missed calls, photos) become one click away, which is useful for hybrid workflows.

Critical analysis — risks and limitations​

  1. Staged activation complicates troubleshooting and support. Enterprises and power users must be aware that installing KB5067036 does not guarantee feature activation. This can produce inconsistent UIs across a fleet and complicate documentation and support. IT teams should test on representative pilot devices before broad deployment.
  2. Automatic categorization can be imperfect. The Category view groups apps automatically based on type thresholds. For users with niche or mixed-use setups, automatic grouping may place apps into unintuitive buckets or leave many in “Other.” There is, at preview time, no supported interface to create or edit categories manually — an omission some users will find limiting.
  3. Potential for bugs and regressions in preview builds. The preview channel and optional updates exist precisely because significant UI and shell changes carry regression risk. Published reports and community discussion around other October/November updates have noted a handful of bugs in concurrent releases. Those deploying KB5067036 widely should be prepared for early issues and plan rollback/mitigation strategies. Tech writers recommend waiting unless you’re comfortable with previews.
  4. Privacy and telemetry considerations. Features like Category grouping and recommendations rely on on‑device heuristics and, in some cases, telemetry. Microsoft’s documentation does not suggest sensitive data leaves the device for classification, but enterprises with strict data policies should validate the behavior in their test environments and review privacy settings for Recommended content. Where Phone Link is used, paired-phone notification data is accessible inside Start; users should review pairing permissions and what is surfaced. If you need strict separation of mobile notifications and corporate desktops, validate before enabling widely.

Enterprise and IT considerations​

  • Pilot first: Deploy KB5067036 to a controlled pilot group in your ring strategy (Release Preview or pilot ring) and confirm behavior with standard workloads. The presence of the updated binaries does not guarantee activation, but testing activation workflows and Group Policy interactions is essential.
  • Group Policy and MDM: Verify how the new toggles map to Group Policy or MDM settings. Some Start settings may be governed by existing policies; test whether new toggles are enforceable centrally and whether hiding Recommended content can be mandated. If custom Start layouts were part of corporate images or onboarding scripts, validate compatibility.
  • Compatibility testing: Some third‑party shell extensions, app launchers, or accessibility tools may interact with Start in ways that manifest as regressions after this change. Run representative compatibility tests, particularly for assistive technologies and keyboard-driven workflows.

Accessibility and performance​

Microsoft’s preview notes emphasize on‑device responsiveness and an unchanged commitment to accessibility, but changing the primary navigation model requires updated accessibility guidance. Screen-reader users, keyboard-only users, and voice-access workflows should be validated: the List view remains available for more deterministic keyboard navigation, which is an important accessibility preservative. Performance-wise, early reports indicate the new Start is snappier on modern hardware, but older or low‑spec machines should be tested to confirm there is no perceptible overhead.

Security, privacy, and data flow — what to verify​

  • Confirm whether Phone Link features require broad device permissions or if they can be scoped to minimal notification and photo access.
  • Check whether Recommended file suggestions rely on cloud-indexed signals or are strictly local. Microsoft’s preview positions these as local UX features, but admins should validate in corporate environments.
  • Ensure the staged activation model does not inadvertently expose incomplete features to regulated endpoints before policy review.
If any of these items remain ambiguous in your environment, treat KB5067036 as a preview-only package until clarity is reached.

How this fits into Microsoft’s broader strategy​

This Start redesign is not an isolated polish — it’s an architectural shift in how Microsoft surfaces apps, files, and phone content to users, aligning the desktop launcher with mobile app drawer mental models and the company’s broader push toward context-aware discovery. It also dovetails with Microsoft’s incremental introduction of on‑device AI features and tighter Copilot integrations — the Start rework provides a larger canvas for future, more proactive assistance features. Expect Start to continue evolving as Microsoft tests Copilot and other AI hooks into everyday workflows.

Practical recommendations (summary)​

  1. If you’re conservative or managing production systems: wait for the cumulative Patch Tuesday release that includes the redesign and for Microsoft to remove staged gating for general availability. This reduces preview risk and gives time for early issues to be resolved.
  2. If you’re an enthusiast or power user who wants it now: install KB5067036 via Settings → Windows Update (or Update Catalog) and then be patient; if the UI doesn’t appear immediately, decide whether you accept the risk of using ViVeTool to force flags (unsupported). Back up system restore points before using unsupported tools.
  3. If you’re an IT admin: pilot the preview in a representative ring, validate MDM/Group Policy interactions, test assistive technologies, and prepare user-facing documentation that explains the new views and toggles. Coordinate with helpdesk teams so they can recognize both the presence and absence of the redesigned Start on patched devices.

Caveats and unverifiable claims​

  • Microsoft’s server‑side staged activation means some statements about exact availability timing for every region or device are inherently probabilistic. Any claim that “installing KB5067036 guarantees the new Start” is inaccurate; the correct statement is that the KB installs the updated binaries but activation can remain gated. Users who claim instant global availability may be reporting anecdotal experiences that will not reflect everyone’s outcome.
  • Region-specific rollout for Phone Link — references to exact availability windows for the EEA or other markets are based on Microsoft’s preview guidance and early reporting; specific, date-bound commitments were not universal across Microsoft’s public notes. Treat any timeline that places exact dates or days for EEA activation as provisional unless Microsoft publishes an explicit schedule. 

Final verdict​

Microsoft’s Start menu redesign is a substantive, thoughtful correction to an often-criticized element of Windows 11. By elevating the All apps list, adding multiple browsing modes, and giving users direct controls to hide recommendations, Microsoft addresses both power‑user and casual workflows in one release. The Phone Link integration and taskbar polish further knit mobile and PC experiences together in a way that feels coherent rather than tacked on.
That said, the staged rollout model and preview packaging mean early adopters may encounter uneven availability and preview‑level bugs. Enterprises should pilot carefully, and individual users who dislike surprises should wait for the general release. For enthusiasts and testers, KB5067036 offers a clear preview of a more discoverable, customizable, and modernized Start — a small but meaningful step in Windows’ ongoing UX evolution.

The Start menu’s redesign is now a practical choice rather than a distant promise: it’s packaged, it’s in the wild, and it shows the direction Microsoft intends for desktop discovery — faster access, more choice, and tighter cross-device continuity.

Source: digit.in Microsoft’s new Start Menu for Windows 11 is packed with new features, all details
 

Back
Top