You press the Windows key. Nothing. You click the Start button. Nothing. The taskbar is there, your apps run fine, but the Start menu has simply gone on strike. It’s one of the most irritating Windows 11 problems because it feels like the whole system is broken when it’s really just one shell component misbehaving.
The good news: this is almost always fixable in under fifteen minutes, and the fixes below are ordered so the quick, safe ones come first. Work top to bottom and stop when the menu works again.
Why this happens
- Windows Explorer shell crashed or wedged. The Start menu lives inside the Explorer process; when Explorer hangs, the menu dies with it even though everything else looks normal.
- Corrupted Start menu app registration. The Start menu is an AppX package, and its registration can break during updates or after aggressive debloating.
- Damaged user profile. Profile corruption breaks shell components for one user while other accounts work fine.
- Recent Windows update conflicts. Feature and cumulative updates occasionally break shell registration, especially on systems with pending restarts.
- Third-party Start replacements or tweakers. Tools that skin or replace the Start menu hook deep into the shell and break with updates.
- Corrupted system files. Damaged shell DLLs or component-store corruption behind the Start menu’s XAML interface.
- Stuck Windows Search or shell services. The Start menu depends on Search and related services; when they wedge, the menu can refuse to open.
How to fix it
Work through these in order — most people are fixed by Fix 2 or Fix 3.
Fix 1: Restart Windows Explorer
The classic fix, and it works more often than you’d expect.
- Press Ctrl + Shift + Esc to open Task Manager. (If the taskbar is also unresponsive, press Ctrl + Alt + Del and choose Task Manager.)
- On the Processes tab, find Windows Explorer.
- Right-click it and choose Restart. Your taskbar will briefly disappear and reload.
- Try the Start button or Windows key. If the menu opens, you’re done — a one-off shell crash was all it was.
Fix 2: Restart the Start menu process directly
Windows 11 runs the Start menu in its own process, and you can bounce just that.
- In Task Manager’s Details tab, look for StartMenuExperienceHost.exe.
- Right-click it and choose End task. Don’t worry — Windows restarts it automatically within seconds.
- Wait about ten seconds, then try the Start button.
- If it opens now, the menu’s host process had wedged. This fix is also the fastest one to retry if the problem recurs.
Fix 3: Re-register the Start menu package
This repairs broken AppX registration without touching your data.
- Press Win + X and choose Terminal (Admin). (If Win+X doesn’t work, open Task Manager, choose Run new task, type
powershell, and tick Create this task with administrative privileges.) - Paste this command and press Enter:
Get-AppXPackage -Name Microsoft.Windows.StartMenuExperienceHost | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} - Wait for it to finish — it takes under a minute and may show red text that is safe to ignore.
- Restart the laptop and test the Start menu.
Fix 4: Repair system files with SFC and DISM
If re-registration didn’t stick, underlying system files may be damaged.
- In Terminal (Admin), run
sfc /scannowand let it complete. - Then run
DISM /Online /Cleanup-Image /RestoreHealth. - Restart and test. Run the re-registration command from Fix 3 once more after the repair, since DISM can restore files that still need re-registering.
Fix 5: Check for and finish pending updates
A half-applied update is a classic Start menu killer.
- Open Settings > Windows Update (press Win + I).
- Install everything pending, including optional updates, then restart — even if Windows doesn’t prompt you.
- After the restart, check Update history for failed updates. A repeatedly failing update may need the Windows Update troubleshooter or a manual download from the Microsoft Update Catalog .
- Test the Start menu after the system is fully updated and restarted.
Fix 6: Test with a new user profile
This tells you whether the problem is your profile or the system.
- Go to Settings > Accounts > Other users and click Add account.
- Create a local account (choose I don’t have this person’s sign-in information > Add a user without a Microsoft account).
- Sign out and sign in to the new account. If the Start menu works there, your original profile is corrupt.
- Move your files to the new profile (C:\Users\YourName to C:\Users\NewName) and make the new account your daily driver. Fixing a corrupt profile in place is rarely worth the effort.
Fix 7: Remove Start menu tweakers and shell mods
Third-party shell tools are a frequent hidden cause.
- Open Settings > Apps > Installed apps and uninstall anything that modifies the Start menu, taskbar, or Explorer (StartAllBack, Open-Shell, ExplorerPatcher, Windhawk mods, “Windows 11 tweaker” utilities).
- Restart and test. If the menu returns, the tool was the problem — check for an updated version compatible with your Windows build before reinstalling.
- Also check Task Manager > Startup apps for anything shell-related you don’t recognize and disable it.
Fix 8: Do an in-place upgrade repair
The last resort that keeps everything.
- Download the Windows 11 ISO from Microsoft’s software download page .
- Mount it, run setup.exe, and choose Keep personal files and apps.
- Complete the repair install and test the Start menu on first boot.
If the menu works in a new profile but you can’t migrate for some reason, or the in-place upgrade didn’t help, deeper profile or component-store damage is at play — but those cases are rare. For the step-by-step variant of this same problem, see our Start menu troubleshooting walkthrough , and if your issues extend to sign-in, the Windows 11 login loop fix covers the neighboring territory.
Closing
A dead Start menu feels like a dead system, but it’s usually just a wedged shell process or a broken app registration — both fixed in minutes with the steps above. Restart Explorer, re-register the package, repair the files, and only reach for the bigger hammers if the small ones don’t land.
