After installing Win10 and Citrix Profile Management 5.x you may notice that the Start menu cannot retain pinned items after restart and sometimes it may not even launch.

Here are the recommended steps to workaround this issue:

1. Ensure win10 version is not less than 10.0.10586.If it is 10.0.10586, then you need to install the latest Microsoft KB which contain a fix for the start menu crash issue. If it is greater than 10.0.10586, such as win10RS1 or later, there is no need to install the patch as the changes are included by default.
2. Modify the Events key to value 0x62 in these two locations:
   [TDL hive will exist only if above updates are installed]
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\ProfileNotification\TDL HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\WindowsNT\CurrentVersion\ProfileNotification\TDL
   Note:If you have permission issues to set this, take ownership of key first, change it from Trusted Installer to Domain admins or etc.)
3. Removed these two lines from the Citrix Profile Management INI file under VDA client if your Citrix Profile Management version is earlier than Citrix Profile Management 5.5. The Citrix Profile Management configuration INI file is located at C:\Program Files\Citrix\User Profile Manager\UPMPolicyDefaults_all.
   Note: If you have Citrix Profile Management 5.5 or greater the two folders are removed by default hence there is no need to remove them manually.
   
4. Add the TDL folder to be mirrored to ensure that the TDL database files are synced properly by Citrix Profile Management from the Microsoft Group Policy Management Console (Computer Configuration -> Policies -> Administrative Templates -> Citrix Components -> Profile Management -> File System -> Synchronization -> Folders to Mirror -> !ctx_localappdata!\TileDataLayer).
5. Ensure all the Citrix Profile Management policies are applied to VDA clients so that the Start Menu and the tile changes would function as desired between different VDA clients.

Note: Since Microsoft published some updates for windows 10 RS1(1607), the above solution does not work on windows 10 RS1. In this situation, you can upgrade the Windows 10 RS1 to Windows 10 RS2, and the above solution may resolve the issue.