Forum Discussion
MarkF26
Aug 06, 2020Brass Contributor
Critical Error on Session Hosts when clicking the Start Button
We started encountering the following errors on our Session hosts: ================================================= Critical Error: Your Start menu isn't working. We'll try to fix it the next t...
David Brophy
Apr 23, 2021Brass Contributor
Soo Kuan Teo Not wanting to dig up an old thread but hoping this will help someone with the same issue. I've logged it with support but they weren't able to figure it out unfortunately. Running Windows 10 2004.
I found that when running Get-AppxPackage in PowerShell as the user it would return no results.
As a workaround, not a fix, I manually added the packages at logon.
Add-AppxPackage -Register "C:\Windows\SystemApps\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown
Add-AppxPackage -Register "C:\Windows\SystemApps\Microsoft.Windows.Search_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown
Add-AppxPackage -Register "C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown
It's not flawless as if the user clicks on the Start Menu before the script kicks in then they get the same error and the explorer process needs to be restarted for Search to work (or logout and back in again). To get around that I ran the script instead of the explorer shell with explorer being launched at the end of the script.
A reboot clears the AppxPackage list again so the script needs to run at every logon.
If anyone has an actual fix it would be nice to know.
MarkF26
Apr 23, 2021Brass Contributor
After various updates to OS, and updates to the WVD Client, we are not experiencing this issue anymore.