Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
After a recompose, refresh, or rebalance operation with a persistent disk, Windows 10 start menu, search, store apps does not work to mouse clicks, starting with the logon.This issue can affect multiple version of Windows 10 intermittently, depending on applications used.The issue occurs on Linked-clone dedicated desktops with a persistent disk where the persistent disk is used to store app settings.
The article describes the known issues and workarounds of Windows 10 Start menu, Search, Store Apps issues. Important: We recommend you migrate from Horizon 7 to Horizon 8 as soon as possible. Horizon 8 offers numerous improvements in performance, scale, and experience for both Administrators and end users. Please see Ensuring a successful migration from Horizon 7 to Horizon 8 (89840) for additional advice as persistent disks are legacy technology and deprecated with Horizon 8
Windows Store Application can store various information into both Guest Operating System area and Persistent For example,The inconsistency for keys under the following keys can cause the start menu/store app issues when the OS area(under HKLM) is refreshed. (1) HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Notifications\< WNF NAME >(2) HKU\< SID >_Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\< APPID >\PSR\WnfStateName
Possible workarounds after the start menu corruption occurred:The following solutions may fix your corruption issue. Work through each solution with administrator privileges on the virtual machine where the start menu corruption occurred.If the first solution does not fix the issue, then continue with the next solution.1. Re-register store applications a. Run the following two cmdlets on PowerShell prompt. REG DELETE "HKCU\SOFTWARE\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData" /FGet-AppXPackage | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} 2. Clearing the store application cache. a. Run wsreset.exe command on command prompt. 3. The app troubleshooter a. Run the troubleshooter to resolve problems for Windows apps. For more information, see Microsoft Document. Possible workaround to prevent the issues:To prevent the issue, the following settings are required. Apply the following required workaround with administrator privileges in your main virtual machine. Do not skip the required steps. To make them effective, recompose operation for linked clones or re-provisioning for instant clones is required. 1. Disable Auto Download a. Edit the following registry in your main virtual machine.[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\WindowsStore] AutoDownload=dword:00000002 2. Disable Microsoft Consumer Experience a. Edit the following registry in your main virtual machine.[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\CloudContent] DisableWindowsConsumerFeatures=dword:00000001 3. Disable Windows Store InstallService (only for windows 10 - 1709 or later) a. Run the following commands on command prompt run as administrator in your main virtual machine.net stop InstallServicesc config InstallService start=disabled Optionally, we recommend applying the following optional workarounds if it is possible in your use-case to prevent the issues more effectively.1. Disable store applicationsThese workarounds must be applied to your main virtual machine as well and recompose or re-provisioning is required after applying the workaround to make them effectively. a. Remove appx packages cmdlet on PowerShell prompt in your main virtual machine.Get-AppxPackage –AllUsers | Remove-AppxPackageb. Disable wlidsvc service (Microsoft Account Sign-in Assistant) using services.msc in your main virtual machine or Block Microsoft Account using Group Policy.Note: You can NOT use Microsoft Account for this setting. If sysprep is used while creating a pool and you encounter the start menu issue, you may skip this step.c. Block Microsoft Store using Group Policy, "Turn off Store application". For more information, see Microsoft DocumentNote: You can still launch system apps, installed Windows apps and provisioned Windows apps, however you cannot download a new store application. Do NOT set "Disable all apps from Windows Store” on Group Policy, since it will disable all apps including built-in apps such as calculator. For more information, see Microsoft Document 2. Do not use sysprep for customizing when creating a linked clones pool because sysprep tries to update store apps in provisioned machine when the environment is connected to the internet, Use quickprep instead. For more details, see Microsoft Document.
About changing start menu layout after Windows 10 version 1703 or later.