ShellExperienceHost.exe

Windows ProcessMicrosoft Corporation

Also called shellexperiencehost, windows shell experience host

WindowsSystem Component

Windows Shell Experience Host. On Windows 10 it backed Start, Action Center, and some clock flyouts as a packaged app.

What you need to know

This is the Windows 10 Start and tray experience host, not File Explorer.

ShellExperienceHost.exe is a packaged shell host. On Windows 10 it owns Start and Action Center surfaces. Windows 11 moved several of those jobs to StartMenuExperienceHost.exe.

Safe?: Yes, as a Windows package
Windows 11?: Start moved to other hosts
Should I end it?: Start or flyouts may close

Feex says

If Start is a black box on Windows 10, I restart ShellExperienceHost. On Windows 11 I start with StartMenuExperienceHost instead. Same anxiety, different host.

What is ShellExperienceHost.exe?

ShellExperienceHost.exe is Windows Shell Experience Host. It is an AppX package, not a System32 leftover. On Windows 10 it hosted Start, the clock flyout, and Action Center chrome.

What does it do?

It renders those experiences in a separate process so a Start crash does not take the whole desktop. File windows stay in explorer.exe.

Why is it running?

You opened Start, the calendar flyout, or Action Center on a Windows 10-style shell. On Windows 11 the process may still appear for leftover surfaces, but Start itself is a different host.

Is it safe?

Usually safe

The package is signed Microsoft. A ShellExperienceHost.exe sitting in a theme-crack folder is not the Windows host.

A legitimate copy normally runs from:

C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe

AppX system package, not System32
Windows 10 Start used this host
Windows 11 Start uses StartMenuExperienceHost.exe

Can I end it?

OK to restart Start

Ending the host closes Start or the flyout. Windows should start it again the next time you open that UI. Do not loop-kill it.

Can I remove it?

Do not delete the SystemApps folder. Repair the Start package or run the Start troubleshooter instead.

Should it start with Windows?

The shell starts the package on demand. Removing it from Startup Apps is the wrong tool.

Normal resource behavior

These are contextual labels, not universal averages.

CPU: Can spike when Start animations hitch or a tile feed misbehaves
Memory: Moderate for a UI host
Disk: Low
Network: Live tiles on Windows 10 could use the network

File information

ShellExperienceHost.exe file information
Executable name	ShellExperienceHost.exe
Common legitimate path	C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe
Publisher	Microsoft Corporation
Signature expectation	Signed by Microsoft Windows

Common problems

Start does not open on Windows 10

Restart ShellExperienceHost, then the Start troubleshooter. Reinstalling Office will not replace this package.

High CPU with a live tile

A mail or news tile that refreshes forever can keep this host awake. Unpin the tile as a test.

Troubleshooting

Diagnose before you change anything destructive.

Know which Windows you are on

Windows 11 Start bugs belong to StartMenuExperienceHost first. This article is the Windows 10-era host.

Re-register the package only after a broken Start

PowerShell AppX re-register is a repair, not a weekly script.

Technical details

ShellExperienceHost.exe technical details
Image name	ShellExperienceHost.exe
Package family	Windows SystemApps

Sources and verification

Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. How we research.

Microsoft Support: Start menu troubleshooter · Start host packages
Microsoft Learn: Windows · Primary Windows documentation
Foxhole process map · First-party samples on Windows PCs. Not a lab benchmark.

Was this article useful?

A yes or no is enough. Pick a reason if you want, or add a short note.