Last Wednesday, our 300+ Windows 11 workstations collectively went to hell. By 9 AM, the Helpdesk phone lines were saturated — everyone’s Start menu had silently switched to that new categorized card view, like an iOS App Library. Users couldn’t find anything. Productivity tanked.
The r/sysadmin subreddit was in the same boat. A post titled “How to revert Win11 new start menu back” blew up with sysadmins sharing their pain. This wasn’t a preview build. Microsoft pushed this change silently through the June Patch Tuesday cumulative update.
I spent three days testing five rollback methods. Here’s the hard truth.
What Actually Changed
Microsoft’s KB5040525 (or your June equivalent) quietly enabled a new Start Menu experience. The “All apps” list was replaced with category-based cards. It takes 3-5 seconds to load on older hardware. Search sometimes fails to find Control Panel.
Real user feedback (from our internal tickets and Reddit):
- “I can’t find Control Panel anymore, search doesn’t work”
- “The Start menu shows blank cards that take 5 seconds to load”
- “Our accounting team senior literally broke down, asked me to downgrade to Win10”
- Reddit sysadmin: “Microsoft forced this new Start Menu and it’s a productivity disaster”
This wasn’t an isolated incident. It was global. Microsoft’s official documentation barely mentions this change — just a single line in an obscure blog post saying “We are introducing a new categorized view in the Start menu.”
Method 1: Group Policy (Enterprise Gold Standard)
If you have domain controllers or local Group Policy Editor, this is the cleanest method. Zero third-party tools.
Steps:
- Open
gpedit.msc - Navigate to:
Computer Configuration -> Administrative Templates -> Start Menu and Taskbar - Find: “Remove common program list from Start Menu” and “Force classic Start Menu”
- Enable both policies
- Run
gpupdate /forceon affected machines
The catch: On some builds after the latest KB update, this policy simply doesn’t apply. I hit this wall — policy confirmed applied, Start menu unchanged.
If GP fails, move on.
Method 2: Vivetool CLI (Personal Machines or Emergency Fix)
This was the most discussed solution on Reddit, and ultimately what I used for the emergency fix.
Vivetool is a third-party utility that toggles Windows hidden feature IDs. Microsoft uses Feature IDs internally to control feature rollouts. Vivetool manipulates these IDs directly.
Steps:
- Download Vivetool from GitHub (search
thebookisclosed/ViVe) - Open CMD or PowerShell as Administrator
- Run:
vivetool /disable /id:47205210
- Restart explorer.exe or reboot
The ID 47205210 is the feature flag for the new Start menu. Disabling it reverts to the previous list view.
My test results: 4 out of 5 machines (Win11 23H2 and 24H2) worked immediately. One 24H2 latest preview build required disabling an additional ID 48433719.
Method 3: Registry Edit (No-Tool Solution)
If your security policy blocks third-party executables, go straight to the registry.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer]
"StartMenuClassic"=dword:00000001
Or batch-disable all related feature IDs:
$ids = @("47205210", "48433719", "48433720")
foreach ($id in $ids) {
reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\FeatureManagement\Overrides" /v $id /t REG_DWORD /d 0 /f
}
Warning: Registry edits require admin rights. Some IDs don’t exist on all Windows builds. Always validate on a test machine first.
Method 4: Uninstall the Specific Update (Temporary Patch)
If you want nothing to do with GPedit or registry hacks, just nuke the KB patch.
- Go to
Settings -> Windows Update -> Update history -> Uninstall updates - Find the latest KB (likely KB5040525 or similar)
- Right-click, uninstall, reboot
Problem: Next month’s Patch Tuesday brings it right back. This is a band-aid.
Method 5: Third-Party Start Menu Replacements (Not for Enterprise)
Tools like Start11 and StartAllBack can completely replace the Start menu. They work well.
But as a sysadmin, I don’t recommend them in managed environments:
- Per-machine licensing costs add up fast
- Audit and compliance headaches
- Microsoft can break these tools with any update
- Users become dependent on third-party software — future migrations get harder
Method Comparison
| Method | Best For | Persistence | Management Overhead | Risk Level |
|---|---|---|---|---|
| Group Policy | Domain/Enterprise | Persistent (until MS changes policy) | Low | Low |
| Vivetool | Personal/Emergency | Need to recheck after each update | Medium | Medium |
| Registry | No-tool environments | Persistent | Low | Medium |
| Uninstall update | Temporary fix | Lost on next update | Low | Low |
| Third-party tools | Personal enthusiasts | Ongoing dependency | High | High |
My Final Recommendation
For enterprise: Group Policy first, supplemented by periodic Feature ID status checks. If GP doesn’t work, deploy Vivetool via startup script.
For personal machines: Vivetool is the fastest fix. But remember — these IDs can change with major Windows releases. I recommend adding the disable command to a startup script, or running it manually after each Patch Tuesday.
One hard lesson: Always validate changes in a test ring before broad deployment. We pushed to all 300 machines at once. Helpdesk was down for two days.
FAQ
How do I revert the new Windows 11 Start menu?
The most reliable method is using Vivetool to disable Feature ID 47205210. For enterprise, use Group Policy.
Can I revert to the old Start menu design?
Yes. Disabling the new feature ID reverts to the previous list view. Note this is not the Windows 10 Start menu — it’s the original Windows 11 list-based layout.
How do I get the classic Start menu left on Windows 11?
Go to Settings -> Personalization -> Taskbar -> Taskbar alignment and select “Left”.
How to get old Windows Start menu?
If you want the classic Windows 10-style Start menu, you need third-party tools like StartAllBack or Start11. Native Windows 11 cannot fully replicate the Windows 10 Start menu.
When will Microsoft fix this?
This isn’t a bug — it’s a feature. Microsoft won’t “fix” it. They’ll keep pushing it. Our only option is to disable it via Group Policy or Vivetool.