
If we create separate config files for each different build of Windows 10, we will not run the risk of issues of corruption. I found going from 1803 to 1809 would break UWP apps if the same packages folder was used between both builds.

(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 started looking into UEM settings we had configured.

I noticed that new UEM profiles weren’t experiencing the issue until after logging off for the first time and logging back on again. We also verified that Appx ‘s are provisioned correctly in our master image.Įvery user in our test environment experienced issues with UWP apps missing. I did check AppReadiness, Apps, AppxDeployment, AppxDeployment-Server logs in event viewer which show no indication of provisioning/Appx registration issues. Recently my test users have experienced an issue with UWP missing.

UEM is currently running in our VDI test environment with WinEnterprise before going live in production.

Recently we have decided to go with UEM for our project.
