Forum Discussion
How do we install Store apps the proper way?
MicrosoftHi, I would suggest to refer to this article for more detail why UWP apps can't be installed in WVD environment: https://docs.microsoft.com/en-us/azure/virtual-desktop/windows-10-multisession-faq#how-do-i-make-sure-apps-don-t-disappear-when-users-sign-out
Why do my apps disappear after I sign out?
This happens because you're using Windows 10 Enterprise multi-session with a profile management solution like FSLogix. Your admin or profile solution configured your system to delete user profiles when users sign out. This configuration means that when your system deletes your user profile after you sign out, it also removes any apps you installed during your session. If you want to keep the apps you installed, you'll need to ask your admin to provision these apps for all users in your Windows Virtual Desktop environment.
How do I make sure apps don't disappear when users sign out?
Most virtualized environments are configured by default to prevent users from installing additional apps to their profiles. If you want to make sure an app doesn't disappear when your user signs out of Windows Virtual Desktop, you have to provision that app for all user profiles in your environment. For more information about provisioning apps, check out these resources:
andyjia
I feel like Microsoft doesn't understand the problem statement. The use of FSLogix is very similar to a UPD scenario where the user profile is stored on a central storage location so that the profile remains available to sessions created on different hosts.
It's commonplace for the local profile to be deleted post logoff, in fact many other problems can manifest if this isnt done.
Also, it seems like Microsoft is completely ignoring the fact that these same apps work fine for new users. On that thought, you can delete an old profile container (FSLogix reference), have that user logon and these apps now work again as expected.
The problem is that the application references in the profile (stored on a network location in a .VHD(x) and mounted ad logon) are not getting updated with the new application version information, effectively creating broken app references.
This configuration is pretty much the standard configuration for organizations that deploy Azure WVD and a Pooled Session Host config.
These references to FSLogix profile containers being the problem are counter productive to one of the hottest Azure solutions these days. We're following Microsoft guidance on the deployment! Is Microsoft suggesting that we no longer use FSLogix? What would happen if this same problem could be reproduced with a UPD?
Why cant Microsoft not admit that there's a significant problem with the way that these applications (MS Store Apps) get updated in an existing profile? That is the root of this problem, not FSLogix!