In today’s post, we will look at the anomaly and the possible solution – whereby a Microsoft Store app cannot start when one user installs an older version than the current version installed by another user in Windows 10. This issue can also occur when System Center Configuration Manager is used to deploy the older version of an offline app and then a user updates the app online from the Microsoft Store.
Windows Store app installed by multiple users fails to start
Consider the following scenario:
- User A signs into a Windows 10 computer, and installs a Microsoft Store app. For example, Minecraft Education Edition, installed by System Center Configuration Manager as an offline app. User A updates the app to a newer version online from the Microsoft Store and then signs out.
- User B signs in to the same Windows 10 computer and installs the older version of the app.
In this scenario, User A can no longer use the app when signed in. Also, User B when signed in, cannot update the app – and this is due to the older version of the app installed by User B has replaced shared files with older versions.
As prescribed by Microsoft, the following steps can fix this issue for users on a specific Windows 10 computer:
1. Confirm that the activationStore.dat file does not exist in the AppRepository directory. For example:
2. Run the following command to set the registry key for the specific application. For example for
reg add HKLM\Software\Microsoft\Windows\CurrentVersion\AppModel\StateChange\PackageList\Microsoft.MinecraftEducationEdition_126.96.36.199_x64__8wekyb3d8bbwe /v PackageStatus /t REG_DWORD /d 2
3. Copy the application.appx file to a local folder, for example:
4. Set the following command to redeploy the app to run each time that a user signs in.
For example for:
powershell.exe Add-AppxPackage -Path C:\Temp\Microsoft.MinecraftEducationEdition_188.8.131.52_x64__8wekyb3d8bbwe.appx
However, if you are using SCCM, Microsoft recommends you do not deploy the app package as a Configuration Manager application. For help choosing between online or offline app updates in SCCM, refer to this Microsoft guide.
KB3092053 states that this is caused due to leftover invalid entries in the registry, which causes a conflict when launching the installed or updated apps.
You could also download and run this Troubleshooter and see if it helps.
I hope you find this post informative enough!