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.
Cliff House restarts at getting things ready, enters into an infinite loop
exit35
✭
I just received the Lenovo Explorer WMR headset.
I connected the headset and Windows 10 proceeded to automatically detect and install.
The tutorial works fine but once completed it attempts to load the Cliff House. I get a brief message "Getting Things Ready" and can see some white lines as the rooms begins to load but then I get a black screen for a few seconds and it restarts the process, "Getting things ready" followed by black screen and so on.
I tried uninstalling the Mixed Reality portal and re-installing, it didn't work. I followed the steps in the link below, the Reg entry is already set to 2.
I am told one of the benefits of WMR is its plug and play nature... sadly it has not been plug and play for me. Any advice would be greatly appreciated.
Specs, if any use, are i5-4690k, 16GB ram, nvidia 1070, Windows 10 64bit, ver 1709. Drivers are up to date.
Edit: Checked updates and everything is up to date.
Answers
Update: I have ran sfc /scannow as administrator and that has found zero violations. Really frustrated that this is not working.
Have you tried upgrade to the latest Windows insider build?
I had this same problem with my HP headset. Turned out it was my graphics card driver causing the problem. I had updated to Radeon Adrenalin 18.7.1, which was an optional driver. I had to roll back to 18.5.1 and then everything worked again.
Not saying this is always the answer but it's what worked for me.
Hope this helps someone with this frustrating problem