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.

unable to launch hololens emulator


Has anyone seen the error as shown in the image attached. I have made sure all my bios settings are correct, I have used installation checklist from here: https://developer.microsoft.com/en-us/windows/mixed-reality/install_the_tools

but still I get this message whenever I try to bring up emulator either through hyper-v manager or through sample app from VS2017. I have also attached the screenshot of the physical graphics card and details about it

Answers

  • Check you have the hardware (BIOS) set up correctly as per https://blogs.technet.microsoft.com/iftekhar/2010/08/09/enable-hardware-settings-in-bios-to-run-hyper-v/

    For virtualizing desktops using RemoteFX, SLAT hardware is REQUIRED. The use of SLAT capable hardware offers significant performance improvements across the board and is especially important when using RemoteFX. These technologies are an extension to the traditional TLB that allow Hyper-V to use the hardware to handle multiple TLBs – one for each virtual machine. This is fundamental requirement for RemoteFX.

    SLAT is REQUIRED and recently some users found this was disabled in the corporate Desktop. When the Company IT tried to make it work they could not.

    When the user to the code copied for home on a DVD. Set up the modest PC and this worked fine.

    The problem was the company machines were 6 years old. The Users own PC circa 2015 is needed and a copy of Windows Professional connected to Insider group at Release level and Windows Developer enable is need in Windows 10 settings

Sign In or Register to comment.