Microsoft has quietly packed a long‑requested overhaul of the Start menu into an optional Windows 11 preview (KB5067036) and the new single, scrollable Start experience can be activated today — either by accepting Microsoft’s staged rollout after installing the preview, or immediately by flipping community‑discovered feature flags with ViVeTool (with attendant risks).
Background / Overview
Microsoft’s October 2025 preview update, identified as
KB5067036, delivers a redesigned Start menu that replaces the split Pinned / All‑apps workflow with a single, vertically scrollable Start surface and introduces multiple ways to browse installed apps. The official release notes describe a
scrollable “All” section, new
Category,
Grid, and
List views for apps, a responsive layout that adapts to screen size, and tighter Phone Link integration. The preview targets Windows 11 servicing builds tied to versions 24H2 and 25H2; Microsoft lists the relevant builds for this drop as
26100.7019 and
26200.7019. Why this matters: the change directly addresses a frequent complaint — the extra tap/page to see All apps — and aims to improve discoverability, reduce friction for keyboard and mouse workflows, and scale better across larger and high‑DPI displays. The redesign also gives users stronger controls to hide or collapse the Recommended area so your installed apps take priority.
Official (recommended) route: install KB5067036 and wait for staged enablement
Microsoft uses a
staged, server‑side enablement model for this Start redesign. That means installing the preview update places the necessary binaries on your PC, but Microsoft may still gate activation for a subset of devices as it monitors telemetry and stability. The supported, least‑risky approach is therefore:
- Open Settings → Windows Update → Check for updates.
- Install the optional preview update labeled KB5067036 (or download the same package from the Microsoft Update Catalog).
- Restart and wait — the Start redesign may appear immediately for some devices, or it may arrive automatically when Microsoft expands the staged rollout to your device group.
If you prefer stability, security assurances, and an easy rollback path, use this supported path rather than forcing flags locally. The Microsoft support page lists the Start redesign and the associated servicing builds for the preview.
Community (unsupported) route: why enthusiasts use ViVeTool
Because Microsoft gates features, many enthusiasts and IT testers use
ViVeTool, a community utility that toggles hidden feature flags on Windows installations, to reveal staged UI elements immediately. ViVeTool is hosted on GitHub and actively maintained; releases are available for x86/x64 and ARM64 devices. The tool exposes commands to enable, disable, or reset specific numeric feature IDs that map to Microsoft’s internal feature‑gating keys. Important framing: ViVeTool edits
local feature state and is
unsupported by Microsoft. Feature IDs are community‑identified and can vary between servicing builds; using the tool may cause UI regressions and unexpected behavior on some systems. Enterprise and managed devices are especially likely to encounter blocks or policy-based failures, and running ViVeTool on production machines is not recommended.
Step‑by‑step: how to enable the new Start now (practical walkthrough)
The following consolidated procedure reflects the commonly shared approach used by experienced testers and enthusiasts. It shows both the
official prerequisite steps and the
ViVeTool commands that have been reported to work on the preview builds. Treat the command IDs as
community pointers — they may require adjustment for later or different builds.
1) Confirm you have the right servicing binaries (build check)
- Press Windows + R, type
winver, and press Enter.
- Confirm the build number is 26100.7019 (24H2) or 26200.7019 (25H2) or later. If your build is lower, install KB5067036 first via Windows Update or the Microsoft Update Catalog.
2) Back up and prepare (do not skip)
- Create a System Restore point and a full backup or image of the system drive.
- Record BitLocker recovery keys and any enterprise recovery information.
- If this is a managed device, consult your IT admin — do not run ViVeTool on devices under Group Policy restrictions.
3) Download ViVeTool
- Get the latest ViVeTool release from its GitHub releases page and unpack it to a folder you’ll remember (for example:
C:\ViVeTool). Choose the package matching your CPU architecture (Intel/AMD vs ARM64). ViVeTool v0.3.x and later include updated feature dictionaries for recent servicing branches.
4) Run Command Prompt as Administrator and navigate to ViVeTool
- Press Windows, type
cmd, right‑click Command Prompt, and choose Run as administrator.
- Change directory to the extracted ViVeTool folder:
cd C:\ViVeTool (adjust to your actual path)
5) Feature‑flag commands that communities have used
- There isn’t a single canonical set of IDs that works universally; the IDs below have been reported across multiple community sources and testing threads. Try the smallest set first (single ID) and add others only if necessary.
Common single‑ID command that has frequently surfaced:
vivetool /enable /id:47205210
Community multi‑ID sets reported to unlock the full redesigned Start and companion features:
vivetool /enable /id:57048231,47205210,56328729,48433719- Some threads also include additional IDs (for companion features or variant builds), e.g.
49221331, 49402389, 55495322 — but these vary by build and hardware.
After running the enable command(s), reboot the PC. The new Start menu should appear when you open Start; if it does not, re‑verify your build and try a different ID combination cautiously.
6) Revert or reset if needed
- To return to the previous Start behavior, either:
- Reset the specific ID:
vivetool /reset /id:47205210
- Or disable the same IDs you enabled:
vivetool /disable /id:57048231,47205210,56328729,48433719
- Then restart Windows. If UI problems persist, uninstall the preview update (KB5067036) via Settings → Windows Update → Update history → Uninstall updates, or restore from the system image you made earlier.
What exactly changes in the Start menu?
The redesign is practical rather than purely cosmetic. Key user‑facing elements are:
- Single, scrollable Start canvas that places Pinned, Recommended (optional), and All apps on one vertical surface.
- Three All‑Apps presentation modes:
- Category — automatically groups apps into topical buckets (Productivity, Games, Creativity, Communication).
- Grid — denser alphabetical grid optimized for wide displays.
- List — classic compact alphabetical list for keyboard power users.
- Responsive layout that adapts columns, pinned counts, and recommendations visibility to screen size and DPI.
- Controls to hide or collapse Recommended so installed apps get priority.
- Companion/Phone Link hooks — a collapsible mobile device pane inside Start for cross‑device content (availability may be region and server‑gated).
- Subtle taskbar and system tray refinements shipped with the same preview, including a redesigned battery icon with optional percentage visibility and smoother hover animations.
Troubleshooting: common issues and community reports
Because ViVeTool flips internal feature gates, community posts show a variety of outcomes. Some commonly reported issues include:
- Start menu fails to open or becomes unresponsive after enabling certain IDs.
- Search input not accepting keyboard input (Win+S or typing into the search box).
- Certain companion integrations or Phone Link elements not appearing even after flag changes — server gating still applies.
- Differences between user accounts — feature activation may be profile‑specific on some systems, or affected by prior registry tweaks and personalization settings.
If you encounter problems:
- Reboot and try
vivetool /disable or /reset for the IDs you toggled, then reboot again.
- If that doesn’t help, uninstall KB5067036 and restore a system image or use System Restore.
- For managed devices, contact IT; do not use ViVeTool on production systems.
Security, support and enterprise considerations
- ViVeTool is not malicious, but it is an unsupported community tool that changes internal feature flags. Microsoft may refuse assistance for issues caused by local flag toggles; running ViVeTool can complicate troubleshooting and support interactions. Relying on it in enterprise environments can violate support policies or MDM constraints.
- KB5067036 also includes other changes — notably Administrator Protection and platform fixes — and was shipped as an optional, non‑security preview so organizations should pilot the update before wide deployment. The Administrator Protection feature requires Windows Hello integrated authentication for privileged prompts on eligible systems. Test admin workflows and automation before broad rollouts.
- Always maintain recovery plans: System Restore, full disk images, recorded recovery keys, and tested rollback procedures are essential before experimenting with preview updates or local flag toggles.
Critical analysis: strengths, limitations and risks
Strengths (what Microsoft fixed well)
- Immediate usability improvements: exposing All apps on the main canvas reduces a frequent friction point and speeds app discovery for many users. The Category/Grid/List options give users a choice between discovery and compact, keyboard‑friendly listing.
- Better scaling across devices: the responsive Start surface is a clear win for large displays and high DPI setups where the previous fixed layout wasted space.
- Administrative and security polish: the preview combines the UI changes with security features like Administrator Protection, which improves least‑privilege workflows when properly validated.
Limitations and design caveats
- System‑determined categories: Category view relies on automatic grouping; there’s no user interface to edit or pin groups manually in this initial rollout. Power users who prefer deterministic placement may find this frustrating.
- Staged rollout fragmentation: because Microsoft uses server gating, two similar machines can behave differently for days or weeks — that inconsistency complicates support documentation and enterprise pilot planning.
Risks of forcing the feature with ViVeTool
- Instability: community threads document cases of Start/search regressions and transient breakages after enabling flags.
- Changing feature IDs: IDs that work for one servicing build may be different in the next. Relying on pinned ID lists without revalidation risks no‑ops or unexpected side effects on future updates.
- Supportability: Microsoft support may decline to assist with ViVeTool‑related breakages on managed or production systems.
Recommended approach for most readers
- Home users who value stability should install KB5067036 via Windows Update and wait for Microsoft to flip the staged enablement. This gives you the new Start with the fewest risks and a supported rollback path.
- Enthusiasts, testers, and IT pilots who understand the hazards can use ViVeTool on non‑critical machines after taking full backups and creating restore points. Treat community IDs as temporary and verify the exact IDs for your specific build before toggling them.
- Enterprise administrators should pilot the update on representative hardware, validate Group Policy and MDM interactions, and document rollback plans before broader deployment. Consider waiting until the redesign arrives through broader cumulative updates if you need consistent, supported behavior across a fleet.
Final checklist (quick reference)
- Confirm build:
winver → expect 26100.7019 or 26200.7019 (or later).
- Official safe path: Settings → Windows Update → Install KB5067036 → wait for staged enablement.
- Community path (advanced, unsupported):
- Download ViVeTool (GitHub releases) and extract.
- Run elevated CMD →
cd to the ViVeTool folder.
- Try
vivetool /enable /id:47205210 (start small). If needed, try multi‑ID sets reported by testers: vivetool /enable /id:57048231,47205210,56328729,48433719.
- Reboot. If problems occur,
vivetool /disable or /reset the IDs and reboot.
- Safety: create a System Restore point, full disk image, and record recovery keys before experimenting.
The new Start menu in KB5067036 is a measured, pragmatic refinement of Windows 11’s launcher — it addresses long‑standing usability complaints while remaining conservative about controls and scaling. For most users the supported path (install the preview and wait) is the best balance of benefit versus risk; for testers and enthusiasts who understand the trade‑offs, ViVeTool provides a reliable way to explore the redesign immediately — but only on systems where you can afford to troubleshoot and roll back. Conclusion: the redesigned Start makes Windows 11 feel more like a modern, scrollable launcher and less like a split interface; the feature is available now in preview form and can be forced with community tools, but prudent backup, validation, and staged deployment remain the right operational posture for most readers.
Source: Windows Report
How to Enable the New Windows 11 Start Menu