See attached graphic that illustrates our problem clearly.
TechGuy129 is our hero!!!!! Thank you for the speedy suggestions!
Unfortunately, re-registering the Microsoft.Windows.ShellExperienceHost and Microsoft.Windows.Cortana appX packages did NOT fix the problem for us. However, adding your exclusion to the snapvol.cfg did. After your suggestion, we spoke to the VMware tech support rep who worked with VMware engineers originally on this issue (months ago) and he recommended appending exclusions 2 - 4 (below) as well. Apparently those additional ones (2 - 4) helped to eradicate this same issue months ago but had no positive impact for us now. It seems that as Microsoft continues to make changes to their OS (e.g. deprecating the TileLayerDatabase) we anticipate needing to append new registry or path locations in the future.
exclude_path=\ProgramData\Microsoft\Windows\AppRepository
exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx
exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppReadiness
exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel
P.S. To test the above, login to your VM, browse to the following path, append the above, then log-out-log-in - viola! If this works, then you will need to apply this to everyone's write disks by uploading this change as a zip file into everyone's writable volume to correct this after they all log out/in.
C:\SnapVolumesTemp\MountPoints\.....snapvol.cfg
This is a common issue with app volumes.
First:
Try re-register the Microsoft.Windows.ShellExperienceHost and Microsoft.Windows.Cortana AppX Packages:
In Powershell:
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"}
If that works, you can add those lines to shellstart.bat file using powershell.exe -command "....."
Secondly:
Also, take a look at this post. it suggests adding
"
Basically, you just need to add this line to the snapvol.cfg on your writable template and/or existing writable:
exclude_path=\ProgramData\Microsoft\Windows\AppRepository
"
Windows 10 Start menu stops working after Windows 10 LTSB 2016 March Cumulative Update
TechGuy129 is our hero!!!!! Thank you for the speedy suggestions!
Unfortunately, re-registering the Microsoft.Windows.ShellExperienceHost and Microsoft.Windows.Cortana appX packages did NOT fix the problem for us. However, adding your exclusion to the snapvol.cfg did. After your suggestion, we spoke to the VMware tech support rep who worked with VMware engineers originally on this issue (months ago) and he recommended appending exclusions 2 - 4 (below) as well. Apparently those additional ones (2 - 4) helped to eradicate this same issue months ago but had no positive impact for us now. It seems that as Microsoft continues to make changes to their OS (e.g. deprecating the TileLayerDatabase) we anticipate needing to append new registry or path locations in the future.
exclude_path=\ProgramData\Microsoft\Windows\AppRepository
exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx
exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppReadiness
exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel
P.S. To test the above, login to your VM, browse to the following path, append the above, then log-out-log-in - viola! If this works, then you will need to apply this to everyone's write disks by uploading this change as a zip file into everyone's writable volume to correct this after they all log out/in.
C:\SnapVolumesTemp\MountPoints\.....snapvol.cfg