UEM: Non-Persistent VDI Deployment and Windows 10 UWP Apps Missing

Share on:


Recently we have decided to go with UEM for our project. UEM is currently running in our VDI test environment with Window 10 1803 Enterprise before going live in production. Recently my test users have experienced an issue with UWP missing. For example calculator, photos, paint3d. sticky notes, etc. I did check AppReadiness, Apps, AppxDeployment, AppxDeployment-Server logs in event viewer which show no indication of provisioning/Appx registration issues. We also verified that Appx ‘s are provisioned correctly in our master image.

Every user in our test environment experienced issues with UWP apps missing. I noticed that new UEM profiles weren’t experiencing the issue until after logging off for the first time and logging back on again. I started looking into UEM settings we had configured. (Most of our settings are still running on easy start configuration except for applications we have profiled) I realized if “Default Apps and FTA” were disabled the UWP apps never went away after multiple log offs. I might have found the solution, as none of my users have complained about the issue in the past couple of weeks.

Adding the following to the “Default Apps and FTA” config resolved our issue with UWP no longer provisioning at logon


We also found a couple of UEM Profiles affected by issue also needed to have any settings reset/delete if it contained any of the following RegistryTrees before the “solution” would work.


Not only did I need to reset/delete “Default Apps and FTAs.” but we ended up resetting/deleting “Windows Explorer” settings in the affected UEM Profiles because it contained the RegistryTree Settings.

Overview of the test environment

  • View 7.7
  • Windows 1803 (I have tested 1709 and 1809 which had the same issue)
  • UEM 9.6
  • App volume 2.15
  • Instant Clones
  • Desktop Pool – Floating

Creating a solution

Windows 10 UWP Settings between builds

Before we begin, I decided to create a new config file for Universal Windows Platform Apps for different builds of Windows 10. I found going from 1803 to 1809 would break UWP apps if the same packages folder was used between both builds. If we create separate config files for each different build of Windows 10, we will not run the risk of issues of corruption. This is why I don’t recommend adding “\Packages\” under “Default Apps and FTAs”.

Create UEM Conditions

Open VMware User Environment Manager Management Console

Go to Condition Sets tab and select Create

Name the Condition Set “Windows 1803”

Select Add and choose Registry Value

Registry Value Condition:

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ReleaseId Is Equal to 1803

Press OK and save the condition set

Repeat process to create condition sets for other Windows 10 builds.

Create UWP Apps config file

Open VMware User Environment Manager Management Console

Go to Personalization tab and select Create Config File

Select Create a custom config file and press next

Configure your location, file name, title and description.

Go to the UWP Apps 1803 config file and add the following under Import/Export tab.

1#Capture UWP settings 
2#If this entry is removed provisioning UWP Apps at logon will break in non-Persistent deployments.
4#Edge Config File already captures theses settings.

Go to DirectFlex tab and disable “Enable DirectFlex for this config file” and “Export at logoff ” for export moment.

Go to Advanced tab and enable “Process during logon and logoff”

Go to Conditions tab and add the condition set we created earlier for Windows 10 1803. Make sure to set when matched “Import and export” and otherwise “Do Nothing”

Save Config File and repeat the process for different Windows 10 builds if you environment has any.

Deploying the solution

We found any settings already captured in UEM with the following RegistryTrees needed to be reset/delete. In our case we needed to reset /delete “Default Apps and FTAs” and “Windows Explorer” settings inside the UEM Profiles already affected.


Log onto floating desktop pool and test UWP Apps

Log off once UWP Apps have been tested. Check UEM Profile and verify the config file is capturing packages folder at log off.

Log back into the floating desktop pool and verify UWP apps are still provisioned and settings are retained.

See https://kb.vmware.com/s/article/60282 VMware Knowledge Based article related to this issue.

Shorty after posting this article VMware created a KB article about “When migrating default apps and FTAs, Windows Store apps like ‘Calculator’ appear uninstalled.”

I ended up testing the KB configuration in my home lab. What I found is that it worked without capturing the packages folder under the end users appdata. However, I noticed without the packages folder sticky notes, calculator, etc settings were being reset after each log off/log on.

I created a new config called “KB60282” which contained the following

1#From VMware KB60282 https://kb.vmware.com/s/article/60282
5HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel

Final Configuration Updated Feb 2020

Default Apps and FTA

1#Capturing FTA and Default settings

UWP Apps 1809

1#Capture UWP settings. If this entry is removed provisioning UWP at logon might break.
5#Edge settings configured for this


2#From VMware KB60282 https://kb.vmware.com/s/article/60282
6HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel