Hello everyone.

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.
Options

The emulator is unable to connect...

Getting the latest files from a GitHub clone helped most of my initial errors, but this one has me stumped.

"The emulator is unable to connect to the device operating system: The emulator is unable to determine the host IP address..."

It takes some time after the emulator has launched and gone to the home screen, but Visual Studio eventually fails and reports "DEP0001: Unexpected Error: -2147466259"

Anyone else ? Any ideas?

Best Answer

Answers

  • Options

    Got that...and gladly fix it...not in the best way...but you can take a look at this thread... https://forums.hololens.com/discussion/238/dep6100-the-following-unexpected-error-occurred-during-bootstrapping-stage#latest

    --
    Blag.
    Developer Evangelist - Development Culture
    SAP Labs Silicon Valley.

  • Options

    Been through that thread without success. I tried everything except was unable to follow this procedure;

    Project panel HoloToolkit\Prefabs\SpatialMapping folder, find the RemoteMapping prefab

    I don't seem to have a HoloToolkit folder in the Unity project, nor can I find RemoteMapping prefab. What am I missing here?

  • Options

    Blag, thanks for the assist! I actually re-did the steps around deleting Hyper-V machines and got rid of the IP error. So that was the post I needed.

    I still have a missing .dll error, but that's a little more straightforward ;0]

    cc

  • Options

    ...I got rid of the IP error, now I get DEP6100: assembly manifest definition does not match the assembly reference... at least it's a new error ;-]

Sign In or Register to comment.