Windows Shell Experience Host High CPU: Causes and Fixes
Windows Shell Experience Host is ShellExperienceHost.exe, a built-in Windows app that draws parts of the interface around the taskbar. What it draws depends on the build. On Windows 10 version 1809 and earlier it also hosted Start, and Microsoft then moved Start into its own process, StartMenuExperienceHost.exe, so on Windows 10 version 1903 and later and on Windows 11, a slow or broken Start menu is usually that other process. Shell Experience Host still runs on Windows 11, and crash reports tie it to the notification panel and the clock and calendar flyout. A short burst of CPU when you open those is expected; steady CPU with nothing open is worth checking, and the steps below go from a sign-out to repairing system files.
Which process does what
Microsoft announced the split in its Windows 10 Insider Preview build 18317 post in January 2019: "up until now Start in Windows 10 has been hosted by something called ShellExperienceHost.exe", and Start was being separated into "its own process, called StartMenuExperienceHost.exe", to simplify debugging and to keep problems elsewhere in the shell from taking Start down with them. Microsoft's current Start menu troubleshooting article uses the same boundary.
| Windows version | Start menu process | What Shell Experience Host does |
|---|---|---|
| Windows 10, version 1809 and earlier | ShellExperienceHost.exe |
Start, plus the other shell surfaces |
| Windows 10, version 1903 and later | StartMenuExperienceHost.exe, one per signed-in user |
Shell surfaces other than Start |
| Windows 11 | StartMenuExperienceHost.exe |
Still present; crash reports name the notification panel |
Microsoft does not publish a list of the surfaces Shell Experience Host draws on Windows 11. The clearest evidence is in the Application Error events people post when it crashes. A Microsoft Q&A report from Windows 11 25H2 (build 26200.6899) shows ShellExperienceHost.exe failing in Windows.UI.ActionCenter.dll when the notification panel opens, and a Windows 10 22H2 report shows it failing in ClockFlyoutExperience.dll when the calendar opens. On a Windows 11 test PC (build 26200), Shell Experience Host ran from C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy, next to StartMenuExperienceHost ("Windows Start Experience Host") and C:\Windows\System32\ShellHost.exe ("ShellHost"). Microsoft has not documented what ShellHost does, and this article does not guess at its role.
Check what it is doing
Open Task Manager with Ctrl + Shift + Esc, sort by CPU, and watch the row while you open and close notifications and the calendar. Then check the path and the package from PowerShell:
Get-Process ShellExperienceHost, StartMenuExperienceHost -ErrorAction SilentlyContinue |
Select-Object Name, Id, CPU, Path
Get-AppxPackage -Name Microsoft.Windows.ShellExperienceHost | Select-Object Name, Version, InstallLocation
The process should run from the package's install location inside the Windows folder. CPU in this output is total processor seconds since the process started, so compare two readings a minute apart instead of reading one number.
| You see | Likely cause | Try |
|---|---|---|
| A spike when notifications or the calendar open | Normal drawing | Nothing |
| Steady CPU with nothing open, since an update | A shell surface in a bad state | Sign out and back in, then install the next update |
| Notification panel or calendar will not open, Event ID 1000 logged | A crash, with the module named in the event | Note the module, update Windows, repair system files |
| Start does not open on 1903 or later | StartMenuExperienceHost, not this process | Use the Start steps below |
| CPU rises while a slideshow background changes | An older advice thread blames slideshows | Test with a single picture |
The last row comes from older third-party guides, not from Microsoft. Switching the desktop background from a slideshow to one picture in Personalization settings is a cheap test you can undo, nothing more.
Fix it in this order
1. Sign out and back in. Shell Experience Host runs in your session, so signing out ends it with the rest of the session and signing in starts a fresh copy. If the CPU stays normal afterwards, keep an eye on what you were doing when it climbed.
2. Install pending updates. Microsoft's Start troubleshooting checklist starts with two questions: is the PC on the latest feature and cumulative update, and did the issue start right after an update. winver shows the build. If the CPU started with an update, the next cumulative update is the first thing to install.
3. Read the crash. Microsoft's tip is to check the Application log for crashes "related to Start (for example, explorer.exe, Search, and ShellExperiencehost.exe)", Event IDs 1000 and 1001:
Get-WinEvent -FilterHashtable @{LogName='Application'; Id=1000} -MaxEvents 50 |
Where-Object Message -match 'ShellExperienceHost' | Format-List TimeCreated, Message
The Faulting module name tells you which part failed. For activation problems the same article points to the Microsoft-Windows-TWinUI/Operational log, searched for the package name.
4. Repair system files. In an elevated Command Prompt, run Microsoft's repair pair, DISM first:
DISM.exe /Online /Cleanup-image /Restorehealth
sfc /scannow
5. If Start is what is broken. On Windows 10 version 1903 and later and on Windows 11, Microsoft checks the Start package with Get-AppxPackage -Name Microsoft.Windows.StartMenuExperienceHost, and re-registers it from a non-elevated PowerShell window, so it is registered to you rather than to the administrator:
Add-AppxPackage -Path "C:\Windows\SystemApps\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\AppxManifest.xml" -Register -DisableDevelopmentMode
The same article warns that if the Start package is missing for every user, the quickest fix is a known-good configuration, rolling back the update, resetting the PC or restoring a backup, because "No method is supported to install Start AppX files."
What not to do
- Do not run scripts that re-register every built-in app for all users. Microsoft documents a targeted re-registration for Start only and calls other installs of Start's AppX files unsupported and unreliable.
- Do not take ownership of
C:\Windows\SystemAppsor delete a folder there to stop the process. These are Windows components. - Do not judge it by one CPU reading. A burst while the notification panel animates is its job.
Where Mole fits
Mole for Windows' Status page lists Shell Experience Host with its CPU, memory and I/O, and Why is this running? shows its program file and what started it. It runs from the Windows folder, so Mole marks it System and offers no Terminate or Force Quit. Each Optimize run begins by restarting the Start menu and Search: Mole ends the copies of StartMenuExperienceHost and the Search host that run from C:\Windows\SystemApps in your session, and Windows starts fresh ones on its own. It does not touch Shell Experience Host. Check and repair system files in the same run asks DISM about the Windows image, at most once every 30 days, and offers Repair system files when Windows reports it repairable. For related names, see Runtime Broker and Windows processes explained.
FAQ
What is Windows Shell Experience Host?
It is ShellExperienceHost.exe, a built-in Windows app that draws parts of the shell. On Windows 10 version 1809 and earlier it also hosted Start; later versions moved Start to StartMenuExperienceHost.exe.
Is Windows Shell Experience Host a virus?
The genuine one is Microsoft's package Microsoft.Windows.ShellExperienceHost installed inside the Windows folder. A file with that name elsewhere should be scanned with Windows Security.
Can I end Windows Shell Experience Host?
Signing out and back in restarts it cleanly. Ending it does not fix whatever made it busy, and Mole does not offer to end it.
Why does my Start menu not open?
On Windows 10 version 1903 and later and on Windows 11, Start is drawn by StartMenuExperienceHost.exe. Check that package with Get-AppxPackage, as Microsoft's Start troubleshooting article shows.