Hello,
Not sure if anyone else is experiencing this, but we are currently using a floating non-persistent pool running Windows 10 LTSB 2016 build (Build 1607). We are running App Volumes 2.12, and using both Appstacks and Writable Volumes UIA+profile template to support certain user-installed apps.
Starting last month, after updating the parent image with the latest cumulative update and creating a test pool to test out the changes with existing appstacks and writables, I found out that the start menu has stopped working altogether. Clicking on the start button doesn't show the menu at all. Curiously, clicking on the Search button does bring up the search menu.
The Event Logs seem to indicate that Microsoft.Windows.ShellExperienceHost AppX Package has been broken, with the following messages recorded on Application event log and Event Viewer -> Applications and Services Logs\Microsoft\Windows\Apps\Microsoft-Windows-TWinUI/Operational log every time I clicked on the start button.
Activation of app Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy!App failed with error: Invalid value for registry See the Microsoft-Windows-TWinUI/Operational log for additional information.
Activation of the app Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy!App for the Windows.Launch contract failed with error: Invalid value for registry.
I have already tried to re-register the Microsoft.Windows.ShellExperienceHost and Microsoft.Windows.Cortana AppX Packages, as it seems to be one of the remediation suggestions over the web, but alas, it didn't work. The powershell I tried running under elevated powershell prompt are:
Get-AppXPackage -Name Microsoft.Windows.ShellExperienceHost | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
Get-AppXPackage -Name Microsoft.Windows.Cortana | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
I tried to reset the TileDataLayer database too by stopping the State Repository and Tile Data Model server services, and deleting off the %localappdata%\TileDataLayer folder and let it recreate it, but no luck so far.
Because of this, I am stuck on leaving the Windows 10 build on 14393.693, which is based on January cumulative update. Also, this problem is still present with the recently released April cumulative update.
Anyone else having this problem?