We have decided to phase out the Mixed Reality Forums over the next few months in favor of other ways to connect with us.
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.
The plan between now and the beginning of May is to clean up old, unanswered questions that are no longer relevant. The forums will remain open and usable.
On May 1st we will be locking the forums to new posts and replies. They will remain available for another three months for the purposes of searching them, and then they will be closed altogether on August 1st.
So, where does that leave our awesome community to ask questions? Well, there are a few places we want to engage with you. 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. And always feel free to hit us up on Twitter @MxdRealityDev.
DEP6100 : The following unexpected error occurred during bootstrapping stage
On a Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz, 3400 Mhz, 2 Core(s), 4 Logical Processor(s) I install everything (I re-installed everything three times) I get this error when I run a HoloLens project made with Unity in the emulator (the emulator starts up and runs fine, the project wont deploy to it):
DEP6100 : The following unexpected error occurred during bootstrapping stage 'Connecting to the device 'F957827B-6FC8-4538-A5BA-3B3807152A56'.':
MissingMethodException - Method not found: 'Boolean Microsoft.Tools.Connectivity.RemoteDevice.Ping()'.
I tried the following (posting it because it did not help me but may help others):
1.Go to "Turn Windows features on or off"
6.You're a go
After I did that I got this error:
The solutions above did not work for me. I found out that the issue was with the Hyper v adapters so I decided to deleted them which caused hyper -v to create them again.
These are the steps
1.Run cmd as admin and enter the following commands
2.This will startup the device manager and show the list of hyper v network adapters
3.Right click and uninstall all hyper v network adapters
4.Open Hyper v manager and delete the virtual machines
5.From Virtual Switch Manager (right side of hyper-v manager), delete all internal switches
6.Restart the system and run visual studio and launch emulator
See this for more info http://www.gfi.com/blog/how-to-remove-hidden-network-adapters-from-virtual-machines/