The Mixed Reality Forums here are no longer being used or maintained.
There are a few other places we would like to direct you to for support, both from Microsoft and from the community.
The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.
For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality.
If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers, or in our Microsoft Tech Communities forums at https://techcommunity.microsoft.com/t5/mixed-reality/ct-p/MicrosoftMixedReality.
And always feel free to hit us up on Twitter @MxdRealityDev.
Failed to start package Microsoft.WindowsStore_8wekyb3d8bbwe!App
Hi There,
Last night while I was updating apps through the Microsoft Store app on the HoloLens, it looked like the Microsoft Store app had crashed and went missing from the app menu. Since then (having conducted a hard restart of the device), the Microsoft Store app remains missing from the app menu on the device.
I see the 'Microsoft Store' app listed as an option in the drop-down of apps through the developers portal however receive an error message when trying to launch the app:
'Failed to start package Microsoft.WindowsStore_8wekyb3d8bbwe!App'
Any help would be appreciated.
Thanks,
Jason
Best Answer
-
Options
Jason
✭✭
After 10 days, it looks like the Microsoft Store app has re-appeared in the app directory on the HoloLens and appears to work fine now. Not sure what would have happened however I'm thinking perhaps a system update fixed the issue? In my case, it looks like patience was the solution. I'm happy that I didn't reset the device as I would have lost all the content on the device.
0
Answers
After 10 days, it looks like the Microsoft Store app has re-appeared in the app directory on the HoloLens and appears to work fine now. Not sure what would have happened however I'm thinking perhaps a system update fixed the issue? In my case, it looks like patience was the solution. I'm happy that I didn't reset the device as I would have lost all the content on the device.