Follow

Windows 10 LTSB 1607 Start Menu does not persist between sessions or it's inaccessible

Product: ProfileUnity-FlexApp

Product Version: All

Expires on: 365 days from publish date

Updated: August 7, 2017

 

Problem:

Windows 10 Start Menu is not accessible and does not persist between sessions. Only Right-Click works.

Symptoms:

Windows 10 Start Menu is accessible first login but on next login it is not accessible anymore. This is happening if ProfileDisk or Portability is configured. 

 

Possible Resolution(s):

For Windows 10 v1703 follow this (KB)

Type "winver" in cmd to find what version you have. 

Important: We have found that when VMware Optimization scripts are executed on Windows 10 LTSB the Windows 10 start menu will break. (Please check compatibility chart at the bottom of KB)

Old start menu rule must not be used with windows 10:

Verify that "Start Menu" Rule is set to save and restore only with "Windows 7" filter (or disabled). The windows 7 start menu can NOT be migrated to windows 10.

Example:

2017-02-23_12_16_27-lmconsole2_-_Remote_Desktop_Connection.png

A) When ProfileDisk is used to redirect profile to VHD or VMDK:

You must first open the master image and disable the App Readiness service and initiate a recompose for these steps to work within the pool.

User Defined scripts must be in place:

User defined scripts (Before ProfileUnity at Logoff) must be in place:

Type: Executable

File:

  • taskkill.exe /F /im iexplore.exe
  • taskkill.exe /F /im taskhostw.exe
  • taskkill.exe /F /im dllhost.exe
  • taskkill.exe /F /FI "USERNAME eq SYSTEM" /IM dllhost.exe
  • net.exe stop "AppX Deployment Service (AppXSVC)"
  • net.exe stop "Tile data model server"
  • net.exe stop "State Repository Service"
  • taskkill.exe /F /im taskhostw.exe

Example:

2017-02-23_14_54_59-Screen_Shot_2017-02-23_at_2.45.00_PM.png

 

In Application Launcher Module of the config:

Create 5 new App Launcher rules that run After Configuration Execution.  (Or import the attached "ProfileDisk" JSON file into the App Launcher module)

  1. They will all use the same settings from the screenshot with the exception of the Arguments field.

 

  1. /c sc config appreadiness start= demand
  2. /c net start "App Readiness"
  3. /c powershell.exe -executionpolicy bypass -windowstyle hidden -noninteractive -nologo Add-AppxPackage -ErrorAction SilentlyContinue -DisableDevelopmentMode "$env:windir\systemapps\ShellExperienceHost_cw5n1h2txyewy\appxmanifest.xml" –Register
  4. /c powershell.exe -executionpolicy bypass -windowstyle hidden -noninteractive -nologo Add-AppxPackage -ErrorAction SilentlyContinue -DisableDevelopmentMode "$env:windir\systemapps\Microsoft.Windows.Cortana_cw5n1h2txyewy\appxmanifest.xml" –Register
  5. /c powershell.exe -executionpolicy bypass -windowstyle hidden -noninteractive -nologo add-AppxPackage -ErrorAction SilentlyContinue -DisableDevelopmentMode "C:\Windows\ImmersiveControlPanel\appxmanifest.xml" –Register

B) When Portability is used in configuration:

Use VSS - Available only in ProfileUnity 6.5.8 or later.

In "Portability Management":

  • Use Portability Ruleset: "Windows 10 Start Menu 6.5.1"
  • Filesystem Rule: Replace Local Application Data TileDataLayer\Database

Example:

2017-02-23_12_05_04-lmconsole2_-_Remote_Desktop_Connection.png

In ProfileUnity configuration "Portability Settings":

Use Portability Rule with VSS option:

  • Filter: Widnows 10
  • Actions: Save, Restore
  • Ruleset: "Windows 10 Start Menu 6.5.1"
  • Save Using VSS
  • Apply Filesystem Rules
  • If redirecting "LocalApp Data" un-select "Only Apply To Local Shell Folders"

Example:

2017-02-23_12_11_58-lmconsole2_-_Remote_Desktop_Connection.png

Note: Exclude "TileDataLayer\Database" from general "Local Application Data" portability ruleset.

Note: User defined scripts are not needed when VSS is used, logoff scripts are only needed for "ProfileDisk" and can be paused.

In Application Launcher Module of the config:

Create 3 new App Launcher rules that run After Configuration Execution.  (Or import the attached "Portability" JSON file into the App Launcher module)

  • They will all use the same settings from the screenshot with the exception of the powershell command.  These are the 3 powershell commands for the rules, they should start with /c powershell.exe ........
    • /c powershell.exe -executionpolicy bypass -windowstyle hidden -noninteractive -nologo Add-AppxPackage -ErrorAction SilentlyContinue -DisableDevelopmentMode "$env:windir\systemapps\ShellExperienceHost_cw5n1h2txyewy\appxmanifest.xml" –Register
    • /c powershell.exe -executionpolicy bypass -windowstyle hidden -noninteractive -nologo Add-AppxPackage -ErrorAction SilentlyContinue -DisableDevelopmentMode "$env:windir\systemapps\Microsoft.Windows.Cortana_cw5n1h2txyewy\appxmanifest.xml" –Register
    • /c powershell.exe -executionpolicy bypass -windowstyle hidden -noninteractive -nologo add-AppxPackage -ErrorAction SilentlyContinue -DisableDevelopmentMode "C:\Windows\ImmersiveControlPanel\appxmanifest.xml" –Register

In the Folder Redirection module of the config:

  • Make sure you are NOT redirecting AppData\Roaming - This causes problems with the latest Windows 10 updates in conjunction with the Start Menu.

 

Start Menu 10 Compatibility Chart (LTSB vs Enterprise v1607):

2017-02-23_12_20_01-LWL-SupportInt_-_lukasz.mikosz_liquidwarelabs.com_-_Outlook.png

 

If the windows 10 Start Menu is corrupted on non-persistent machine make sure that all the settings in this KB are in place than follow the steps below:

Step 1) Logoff and back on again, if its not fixed, continue:

Step 2) Delete portability files associated with windows 10 start menu (and Delete ProfileDisk).

Step 3) Login.

 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.