Cannot run HoloLens2 Emulator -

[mwalus]

I created new Unity 2018.4.2 project and imported latest MRTK v2 (foundation and examples packages). I’m trying to run one of the demo scenes (HandInteractionExamples). I build app in Unity and opened project in VS and trying to run it in HoloLens2 Emulator but emulator cannot start. Error message is displayed:

[XDE:002] The emulator is unable to verify that the virtual machine is running:
Could not load file or assembly ‘Diskstream, Version=10.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)

I installed all the tools using this guide: Install the tools - Mixed Reality | Microsoft Learn

What is more interesting that I can run apps in HoloLens1 Emulator without any issues.
I’m running Windows 10 Pro 1903, Build 18362.175

[P_D_B]

@mwalus We’re hoping to post a new build soon that will resolve this issue, but we have a workaround you can use:

1. Open an Administrator command prompt.
2. Switch to the folder that contains sn.exe, which is part of the .NET Framework SDK. For example, this can be found in C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.7.2 Tools\x64
3. Run “sn -Vr Diskstream,31BF3856AD364E35”

After doing this, the emulator should now launch properly.

[Apaulture]

@P_D_B

@mwalus We’re hoping to post a new build soon that will resolve this issue, but we have a workaround you can use:

1. Open an Administrator command prompt.
2. Switch to the folder that contains sn.exe, which is part of the .NET Framework SDK. For example, this can be found in C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.7.2 Tools\x64
3. Run “sn -Vr Diskstream,31BF3856AD364E35”

After doing this, the emulator should now launch properly.

Unfortunately this did not work.

[P_D_B]

@Apaulture Did the sn command complete successfully? What error are you getting trying to launch the emulator?

[mwalus]

@P_D_B I think I tried that (I will double check it again). I opened “Developer Command Prompt for VS2017” in Administrative mode and registered Diskstream assembly successfully. I was able to see it on the list using command “sn -Vl”. But as far as I remember I was still getting the same error.

[mwalus]

@P_D_B

@mwalus We’re hoping to post a new build soon that will resolve this issue, but we have a workaround you can use:

1. Open an Administrator command prompt.
2. Switch to the folder that contains sn.exe, which is part of the .NET Framework SDK. For example, this can be found in C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.7.2 Tools\x64
3. Run “sn -Vr Diskstream,31BF3856AD364E35”

After doing this, the emulator should now launch properly.

I verified it once again and it worked OK. The crucial part is to use “sn” tool from directory you mentioned and previously I used “VS2017 Developer Command Prompt” which was using “NETFX 4.6.1” tools and not “NETFX 4.7.2” as you mentioned.
Thank you very much.

[P_D_B]

@mwalus

I verified it once again and it worked OK. The crucial part is to use “sn” tool from directory you mentioned and previously I used “VS2017 Developer Command Prompt” which was using “NETFX 4.6.1” tools and not “NETFX 4.7.2” as you mentioned.
Thank you very much.

Glad to hear it @mwalus . The updated build of the emulator is now available: https://docs.microsoft.com/en-us/windows/mixed-reality/hololens-emulator-archive. Version 10.0.18362.1021 is functionally identical to 10.0.18362.1019 but resolves the signing issue.

Once installing the 1021 build, you can also safely remove the workaround by running

sn -Vu Diskstream,31BF3856AD364E35

With 1021 installed, 1019 will also now work without the workaround, though since the two builds are otherwise identical there’s no benefit to using 1019.