How to Fix Start Menu Not Opening in Windows 11

End the process tree on StartMenuExperienceHost.exe in Task Manager. That single action fixes a large share of "Start menu won't open" cases in Windows 11, and it takes about five seconds once you know where to look. Here's why it works, and what to do when it doesn't.

Start in Windows 11 isn't part of explorer.exe the way it was in Windows 7. It's a separate packaged app, StartMenuExperienceHost, that explorer.exe launches and talks to. When you click the Start button and nothing happens — or it flickers open for a fraction of a second and slams shut — that separate process has usually crashed, hung, or gotten into a bad state, while explorer.exe itself is running just fine. Restarting the whole shell fixes it too, but killing the specific broken piece is faster and doesn't close your open File Explorer windows.

Kill and relaunch StartMenuExperienceHost

1. Press Ctrl+Shift+Esc to open Task Manager.
2. Click the Details tab.
3. Scroll to StartMenuExperienceHost.exe, right-click it, and choose End process tree.
4. Windows relaunches it automatically within a few seconds. Click Start again to test.

If it's not listed at all in Details, that means it's already dead rather than hung — go to File → Run new task, type explorer.exe, and let the whole shell restart instead.

Myth: "Just reset Windows" is the reliable fix

It isn't, and it throws away a lot of working software and settings to solve a problem that's usually much narrower. In four separate cases I've fixed for people who'd already tried a reset before calling me, the actual cause was one of: a corrupted StartMenuExperienceHost app-data folder tied to that specific user profile, a leftover registry key from a Start menu customization tool, or a search indexing stall. None of those needed a reset. Reserve it for after you've worked through the list below and confirmed the problem follows you into a brand-new local user account — that's the one test that actually tells you whether a reset would help.

Myth: it's always the most recent update's fault

Sometimes, yes — Microsoft Q&A threads show cases where a specific cumulative update (KB5068861 was one reported instance) introduced a StartMenuExperienceHost crash that only rolling back the update resolved, at least until Microsoft shipped a corrected build. But plenty of Start menu failures have nothing to do with the most recent patch and everything to do with a corrupted per-user cache, a third-party Start replacement tool, or search indexing. Don't uninstall your latest security update on a hunch — check Event Viewer first (Windows Logs → Application, look for Event ID 1000 or 1001 tied to StartMenuExperienceHost.exe) to see whether it's actually crashing, and note the timestamp against your update history before deciding it's the update's fault.

Reality: reset the per-user Start data if the crash follows one account

Create a second local user account (Settings → Accounts → Other users → Add account), sign into it, and test Start there. If it works fine in the new account, your original profile's Start menu cache is the problem, not Windows itself.

1. Navigate to C:\Users\%USERNAME%\AppData\Local\Packages\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy (substitute the actual folder name for the broken account) while signed into an account other than the broken one, or from Safe Mode.
2. Rename the LocalState folder to LocalState.OLD.
3. Sign back into the original account. Windows generates a fresh LocalState folder automatically.

This resets Start menu layout, pinned tiles, and some personalization for that account — not your files or installed apps — so expect to re-pin things afterward.

Reality: re-register the Start menu package

If Start is missing from the system entirely rather than just crashing, confirm the package is actually installed first. From a non-elevated PowerShell prompt:

Get-AppxPackage -Name Microsoft.Windows.StartMenuExperienceHost

If that returns nothing, re-register it from an elevated prompt:

Add-AppxPackage -Path "C:\Windows\SystemApps\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\AppxManifest.xml" -Register -DisableDevelopmentMode

Reboot and test. This re-registers the existing package files against your system — it isn't a reinstall and won't touch your data.

Reality: search indexing can jam the whole menu

Start's search box shares infrastructure with Windows Search, and a corrupted or badly stuck search index can make the entire Start UI hang while it waits on a query that never returns. Check first: press Win+R, run control.exe srchadmin.dll (or search "Indexing Options" from a working search elsewhere, like the taskbar search icon if that still opens). If Indexing Options shows the index status stuck or shows a much lower item count than you'd expect, rebuild it: Advanced → Rebuild. This can take from twenty minutes to several hours depending on how much you have indexed, and Windows will keep working with degraded search in the meantime. If Start responds normally as soon as you kill SearchHost.exe in Task Manager and test again immediately after, that confirms search was the bottleneck.

Symptom-to-fix reference

Symptom	Confirming check	Fix
Start flickers open then closes instantly	Event Viewer shows Event 1000/1001 for StartMenuExperienceHost.exe	End process tree on StartMenuExperienceHost, relaunch
Start does nothing at all when clicked	Package check returns nothing (Get-AppxPackage command above)	Re-register the Start menu package
Problem only happens on one user account	Works fine on a freshly created test account	Rename LocalState folder for that profile
Start hangs for several seconds before responding	Indexing Options shows a stalled or incomplete index	Rebuild the search index
Started right after installing a Start-menu customizer	Uninstalling the tool and rebooting restores normal Start behavior	Remove the third-party tool; don't chase a Windows-side fix

What I would not do

• Don't delete registry keys from a forum post before understanding what they hold. Removing StuckRects3 or the Explorer CloudStore key has resolved this for some people, but it also wipes taskbar position and pinned layout — treat it as a specific fix for a specific symptom, not a general-purpose one.
• Don't roll back a cumulative update on a guess. Confirm the crash timestamp actually lines up with the update install time in Event Viewer first; otherwise you're giving up a security patch for nothing.
• Don't run a full Windows Reset before testing a second local account. That single test tells you in five minutes whether the problem is profile-specific, which a reset would fix anyway without the collateral damage.
• Don't leave a third-party Start-menu replacement tool installed while troubleshooting. It changes what you're actually debugging.

Checklist before you give up and reset

• Ended StartMenuExperienceHost's process tree and retested
• Checked Event Viewer for Event 1000/1001 tied to the crash timestamp
• Tested Start on a fresh local user account
• Verified the Start menu package is actually registered
• Ruled out a stuck search index
• Removed any third-party Start replacement software, if installed

My honest take: if you've done all of the above and Start still won't behave, the profile reset (renaming LocalState) or an in-place repair install will fix the overwhelming majority of what's left. A full Reset This PC is rarely the actual answer here — it's just the option people reach for because it's visible in Settings, not because it's targeted at this specific problem.