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.
Windows updated to 1511 now DEP6100 with remote device
Hi! I have a workstation running ENT and it updated itself to 1511 and since then I have been unable to deploy to remote device. I have attempted reinstalling VS2015, windows SDK, Remote tools for VS2015U2, Unity, and Unity-Metro.
I still get the infamous DEP6100, I have searched the forums here and have noted that the version in the VS project settings only shows 10240 and not 10586. This points to an SDK issue correct?
I am able to successfully build to the emulator with no problem, and I can build to remote device from my laptop no problem as well as connect to the device portal therefore verifying the IP is correct.
Currently uninstalling everything, I previously reinstalled each component one at a time.
I find it odd the emulator works but not remote deploy. Also frustrating that an automatic update caused these issues.... the update occurred in the middle of the night and I did have projects open in both Unity and VS ( everything was saved but perhaps this is related? )
Any other suggestions?
Best Answer
-
Options
It would seem completely reinstalling all of the tools has solved the issue.
Thank you for your help!
5
Answers
The 10586 components aren't selected by default when installing VS2015U2. To fix/verify this,
Hi you need to relink developer mode to Visual Studio and HoloLens again as well as above
https://developer.microsoft.com/en-us/windows/holographic/Using_Visual_Studio.html#Enabling_Developer_Mode
Its Release,x86,Device to rebuild for the HoloLens device
It would seem completely reinstalling all of the tools has solved the issue.
Thank you for your help!
I had done this however it still was not showing up, I suspect its some odd issue that resulted from win 10 force restarting when it updated while VS was open. 10586 was recognized and working prior to the update. The first thing I tried was reinstalling just that component, and when that did not work I reinstalled VS entirely.