ShellExperienceHost issues are commonly related to Start menu, taskbar, or Explorer not starting or closing unexpectedly. Use the following steps to troubleshoot and repair it.
- Check for XAML dependency issues (enterprise/managed or virtualized devices) If this device is in an enterprise or virtualized environment and you see symptoms like:
- Explorer.exe crashes or shows a black screen
- Start menu fails to open
- Taskbar fails to appear
- XAML-based apps (Settings, UAC prompts, etc.) fail to open
Then the issue might be missing or unregistered XAML dependency packages.
For such environments, IT admins can:
- Manually re-register the missing packages in the affected user session using PowerShell:
Add-AppxPackage -Register -Path "C:\Windows\SystemApps\MicrosoftWindows.Client.CBS\_cw5n1h2txyewy\appxmanifest.xml" -DisableDevelopmentMode Add-AppxPackage -Register -Path "C:\Windows\SystemApps\Microsoft.UI.Xaml.CBS\_8wekyb3d8bbwe\appxmanifest.xml" -DisableDevelopmentMode Add-AppxPackage -Register -Path "C:\Windows\SystemApps\MicrosoftWindows.Client.Core\_cw5n1h2txyewy\appxmanifest.xml" -DisableDevelopmentMode - On non-persistent environments, run these registrations synchronously at logon (for example via a batch wrapper) before Explorer launches so that ShellExperienceHost and other XAML components can load correctly.
- If StartMenuExperienceHost / ShellExperienceHost is not installed or not activating If Start menu or shell components are failing and event logs show messages such as:
- "Package was not found"
- "Invalid value for registry"
- "Element not found"
- "Package could not be registered" for
Microsoft.Windows.StartMenuExperienceHostorMicrosoft.Windows.ShellExperienceHost
Then the recommended path is:
- Revert to a known-good configuration:
- Roll back the recent Windows update that introduced the problem, or
- Reset the PC to defaults (keeping files if desired), or
- Restore from a system backup where the shell was working.
- There is no supported method to manually install or side-load Start menu/Shell AppX packages on consumer systems; doing so is often unreliable and not recommended.
- General shell/Explorer troubleshooting steps If ShellExperienceHost failures manifest as “Explorer has stopped working” or similar shell instability, use these steps:
- Run System File Checker (SFC)
- Open an elevated Command Prompt (Run as administrator).
- Run:
sfc /scannow - Wait for the scan to complete and let Windows repair corrupted or missing system files.
- Scan for malware
- Run a full scan with installed antivirus.
- Optionally install and run Microsoft Security Essentials on supported systems to ensure no malware is interfering with shell components.
- Test in Safe Mode
- Boot into Safe Mode and try to reproduce the issue.
- If ShellExperienceHost/Explorer works in Safe Mode, a third-party startup item or driver is likely causing the problem.
- Perform a Clean Boot
- If the issue does not occur in Safe Mode, perform a clean boot and selectively disable startup items and services to identify the conflicting component.
- If the issue has persisted for a long time
- For long-standing shell/Explorer failures that are not resolved by SFC, malware scans, Safe Mode, or Clean Boot, perform an in-place upgrade/repair install of Windows to restore system components while keeping apps and files.
- When system apps broadly fail after an update If multiple system apps (Start, Edge, Cortana, etc.) fail after a feature update, install the relevant quality update or cumulative fix provided for that Windows version, or reinstall/repair Windows as recommended in the official guidance.
If these steps do not resolve the ShellExperienceHost crash, the next supported actions are:
- Reset this PC (keeping files) to repair the OS while preserving personal data, or
- Fully reinstall Windows from recovery media if corruption is severe.
References:
- KB5072911: Explorer, the Start menu, and other XAML-dependent apps might not start or close unexpectedly on some enterprise devices
- Start menu troubleshooting guidance
- Error: Windows Explorer has stopped working
- Some system applications don't work as expected after you upgrade to Windows 10 Version 1703