Quick answer: ShellExperienceHost.exe (Windows Shell Experience Host) is a genuine Windows process that draws parts of the interface such as the clock and calendar flyout, the notification area and, on Windows 10, the Action Center and Start menu visuals. It is safe when it runs from C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy. If it uses a lot of CPU or memory or stops responding, end it in Task Manager (Windows restarts it), turn off a slideshow desktop background and automatic accent color, run sfc /scannow and DISM, and re-register the app with PowerShell if the problem keeps coming back.
Applies to: Windows 11 and Windows 10.
In this guide
What ShellExperienceHost.exe does
Windows Shell Experience Host is a built-in system app that shows several “modern” pieces of the Windows interface: flyouts from the taskbar such as the clock, calendar, volume and network panels, notifications, and visual effects like transparency on those panels. On Windows 10 it also handles Start menu and Action Center visuals; Windows 11 moved more of this into separate processes such as StartMenuExperienceHost.exe, so how much it does depends on your version.
Normally it uses almost no CPU and a modest amount of memory, and it spikes briefly when you open one of those panels. Constant high CPU, steadily growing memory, or a “not responding” Start menu or taskbar are signs something is wrong.
Is it a virus?
The real file lives in C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy. To check, open Task Manager with Ctrl + Shift + Esc, go to the Details tab, right-click ShellExperienceHost.exe and choose Open file location. If it opens anywhere else, or you see a similar name with a spelling change, scan the PC; our guide on how to scan for malware covers the built-in tools.
Fix 1: Restart it
- Open Task Manager with Ctrl + Shift + Esc and select the Details tab.
- Right-click
ShellExperienceHost.exeand choose End task, then confirm. - Windows starts it again within a few seconds. Open the clock or notification flyout to make sure it comes back.
If the taskbar or desktop stops responding too, restart Windows Explorer from the Processes tab instead. A full restart of the PC is the next step if neither helps.
Fix 2: Turn off slideshow and automatic accent color
A slideshow wallpaper combined with an accent color picked automatically from the background is a well-known cause of high CPU in this process, because Windows recalculates colors and redraws panels each time the picture changes.
- Open Settings > Personalization > Background and change Personalize your background from Slideshow to Picture or Solid color.
- Open Settings > Personalization > Colors and set Accent color to Manual (on Windows 10, clear Automatically pick an accent color from my background).
- To test whether visual effects are involved, turn off Transparency effects on the same page.
If memory use is high across several interface processes, see Desktop Window Manager high memory; the same graphics driver and display issues often affect both.
Fix 3: Repair system files
Open Terminal (Admin) or Command Prompt (Admin) and run these commands one at a time:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannowDISM repairs the Windows component store first, then SFC uses it to replace damaged system files. Restart when both finish. If SFC can’t fix files while Windows is running, run it offline from recovery.
Fix 4: Re-register Windows Shell Experience Host
If the process crashes repeatedly, flyouts don’t open, or Event Viewer shows errors for Microsoft.Windows.ShellExperienceHost, re-register the app package. Open Terminal (Admin) with PowerShell and run:
Get-AppxPackage -AllUsers Microsoft.Windows.ShellExperienceHost | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}Red error text about a package in use is common and can usually be ignored; restart the PC afterwards and test again. This doesn’t remove any of your files or settings.
Other fixes
- Install Windows updates and the latest graphics driver from your PC or GPU maker. Many Shell Experience Host bugs were fixed in cumulative updates.
- Remove taskbar or Start menu customization tools (third-party Start menus, taskbar tweakers or skins). They hook into the same interface and are a frequent cause of crashes.
- Test a new user account: create one in Settings > Accounts > Other users. If the problem doesn’t happen there, your user profile is damaged and moving to the new account is the cleanest fix.
- If taskbar icons disappear along with these problems, see taskbar icons missing.
Don’t try to delete, rename or block ShellExperienceHost.exe. It’s part of Windows, and removing it breaks the taskbar flyouts and notifications.
Related guides
- Desktop Window Manager high memory: why it happens and 5 fixes
- WMI Provider Host (WmiPrvSE.exe): Is It a Virus and How to Fix High CPU
- Taskbar icons missing in Windows 11 or 10: how to get them back
- SFC offline: how to run sfc /scannow from recovery in Windows 11 and 10
Official sources: for more detail, see Microsoft’s own pages:
- Microsoft Support: Use the System File Checker tool to repair missing or corrupted system files
- Microsoft Learn: Add-AppxPackage
Frequently asked questions
Can I disable ShellExperienceHost.exe?
No, not safely. Windows needs it for flyouts and notifications, and it restarts automatically if you end it. Fix the cause instead.
Why does ShellExperienceHost use so much memory?
A slowly growing memory figure usually points to a bug fixed by a Windows update, a display driver problem, or a shell customization tool. Restarting the process frees the memory until the cause is fixed.
What’s the difference between ShellExperienceHost and StartMenuExperienceHost?
StartMenuExperienceHost.exe runs the Start menu itself in newer Windows versions, while Shell Experience Host handles other flyouts and notifications. If only the Start menu misbehaves, ending StartMenuExperienceHost.exe in Task Manager is the first thing to try.
Leave a Reply