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.
Deployment error DEP6953
MSeifert
✭
Hello,
I have been developing for HoloLens for the past couple of months, and never had any issues deploying the applications I developed in Unity to the device using Visual Studio 2017.
Recently I have updated VS 2017 to the latest version (although I'm not sure this is related) and now whenever I try to deploy a project to the HoloLens (opening a solution and clicking Debug > Start Without Debugging) I get a strange error immediately when it starts deploying (after the Build phase is finished):
DEP6953: Failed to launch remote debugger with the following error: 'Command failed: 0x80070020'.
I have tried the following:
- Rebooting both my laptop and the HoloLens
- Repairing VS 2017
- Uninstalling VS 2017 completely and reinstalling
- Trying to deploy on a different HoloLens
- Deploying a different Unity project (the same happens for all projects now, new or old)
- Unpairing all devices from the HoloLens and pairing again
In all of these cases, the same error occurs.
I have entered the correct device IP in the project settings and I can access the HoloLens Device Portal using the browser by entering the same IP.
Any ideas?
Update: After doing a complete reset of both of my HoloLenses, it worked again. So it was an issue which suddenly affected both HoloLenses at the same time (inexplicably), and is apparently unrelated to my desktop environment.