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.
HP Mixed Reality - "Something went wrong, and we couldn't start Windows Mixed Reality"
cicorias
✭
Is there a better forum to post this in?
If the host if freshly booted, the Headset works fine. Once the app or the headset is reconnected, the "Mixed Reality Portal" shows the error: 
At that point, the only way to recover is rebooting the entire host PC.
What I do see in the System Eventlog are the same Error's related to DCOM failures and permission failures for Local Activation
This is a Fresh branch new HP z240, 64GB, NVIDIA GTX 1000 w 3GB, i7. So, seems like package registration is not proper.
Windows version 1703.16251.0 (Insider preview)
Before I start mucking around with dcomcnfg and package permissions, or registry permissions, is this a known problem and is there an easy fix?
Best Answers
-
Options
Jesse_McCulloch
admin
Build 16251 had a known issue with the Mixed Reality Portal where it would crash almost immediately for 97% of users. As of Wednesday there is a new build out with the fix in place, and it is considerably more stable. Please consider moving to the latest fast ring build if possible.
5
Answers
Build 16251 had a known issue with the Mixed Reality Portal where it would crash almost immediately for 97% of users. As of Wednesday there is a new build out with the fix in place, and it is considerably more stable. Please consider moving to the latest fast ring build if possible.
16257.1 build addresses the issue.