How to Fix ShellExperienceHost.exe High CPU After a Windows Update
ShellExperienceHost.exe drives the taskbar, Start menu, Action Center and notifications in Windows 11. High CPU after an update usually comes from a corrupted notification cache, a flood of app notifications, or a damaged shell component rather than a virus. Restart the process, clear the notification cache, install the latest updates and run SFC to repair system files. This illustrated guide covers 3 methods and 22 steps, with a separate picture for every step.
-
1. Confirm the process in Task Manager
Press Ctrl+Shift+Esc, open Processes, and check whether Shell Experience Host is genuinely using high CPU.
-
2. Verify the file location
Right-click Shell Experience Host and choose Open file location to confirm it sits in the Windows System32 folder.
-
3. Restart the process
Select Shell Experience Host and click Restart to reload the taskbar and notification components.
-
4. Open notification settings
Open Settings, System, Notifications, to review which apps are allowed to show alerts.
-
5. Silence noisy apps
Switch off notifications for apps that constantly post alerts and clear any that are stuck.
-
6. Enable focus assist
Turn on Do not disturb or a focus session to stop a flood of alerts from driving shell CPU.
-
7. Open File Explorer options
Open File Explorer, select the View tab, and show hidden items so the app data folder is visible.
-
8. Navigate to the packages folder
Browse to the local AppData Packages folder where shell and notification data is stored.
-
9. Find the shell package
Locate the folder for the shell experience package that holds the cached notification database.
-
10. Open the local state folder
Open the LocalState subfolder to reach the cached notification file used by the shell.
-
11. Close the process first
Return to Task Manager, select Shell Experience Host, and click End task so the cache file is not locked.
-
12. Delete the cache database
Delete the cached notifications database file; Windows will rebuild a fresh copy on next sign-in.
-
13. Sign out and back in
Sign out of Windows and sign in again to let the shell recreate a clean notification cache.
-
14. Check for updates
Open Settings, Windows Update, and click Check for updates to install the latest cumulative patch.
-
15. Install optional updates
Open Advanced options, Optional updates, and install any pending system or driver updates.
-
16. Open the update troubleshooter
Run the Windows Update troubleshooter from Settings if updates fail to install.
-
17. Open an elevated command prompt
Search for Command Prompt in the Start menu and choose Run as administrator.
-
18. Run System File Checker
Type the sfc scannow command and press Enter to scan and repair damaged Windows system files.
-
19. Run DISM restore health
Run the DISM restore health command to repair the underlying Windows image if SFC found errors.
-
20. Review event errors
Open Event Viewer and look under Windows Logs, Application, for shell-related errors after the update.
-
21. Check startup apps
Open Task Manager, Startup apps, and disable unnecessary tools that load into the shell at sign-in.
-
22. Restart the computer
Restart Windows so the updated shell components and repaired files load cleanly.