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.
How to diagnose "DEP0001 SmartDeviceException - BOOT_E_CONFIGURATION_ERROR [0x80131500]
I am learning HoloLens development and cannot get past an error deploying the Origami training app from the HoloLens 101E video.
When I start without debugging the emulator appears and reports this error
Microsoft HoloLens
The emulator is unable to connect to the device
operating system:
Object reference not set to an instance of an object.
Some functionality might be disabled.
Q: Is this referring to the fact that I do not have a hardware HoloLens device?
When I click Close on that error dialog, the emulator continues to load without error. But Visual Studio eventually reports error
"**DEP0001: Unexpected Error: SmartDeviceException - BOOT_E_CONFIGURATION_ERROR [0x80131500] Origami "
**
Is the following configuration supported? If so, what can I do to diagnose this? Thanks!
HoloLens Emulator 10.0.14393.0
Windows 10 Pro Insider Preview 16232.
Visual Studio Community 2017, version 15.2(26430.14)
.Net Framework 4.7.02523
My PC is a Surface Pro 4, 8 GB ram, i5.
==========
Thanks for any help
+tom
Answers
I am seeing the same issue - have you had any luck resolving this?
Same with me. Please give us a hint for a solution, if you've find one :-)
Thx
I suspect that the issue was due to my Surface Pro 4 video card not meeting the criteria for running Mixed Reality (it fails the test in Mixed Reality Portal - an app available in all Win 10 1709 systems). Since I wrote the post above I found two solutions:
1) Use my wife's laptop to run my new Mixed Reality headset.
2) Get a new job where my new laptop meets the specs.
-- Sorry I don't have a workaround for doing MR development using a Surface Pro 4.