Hello everyone.

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.

Mixed Reality Simulator is evil

HI,

I followed the instructions here, in order to set up the Mixed Reality Simulator on my Windows 10 machine (Enterprise, 64 bit, Build 15063.447) and right after turning on the simulation toggle (thus step 6), Windows went nuts. The desktop started flickering in < 1 Hz, as Windows was apparently trying to restart explorer.exe over and over again. I could do nothing anymore as no window kept focus, I even tried several fixes I found online (this flickering desktop issue seems to be quite frequent, although the cause is different), e.g. disabling Windows Error Reporting, I failed doing that, and ultimately I had to use a system restore point to fix this. I did this twice now, flipping this simulation toggle definitely destroys my explorer. Here are the Windows Event Logs I get over and over again:


Information (Winlogon, Event ID 1002)
The shell stopped unexpectedly and explorer.exe was restarted.

Information (Windows Error Reporting, Event ID 1001)
Fault bucket , type 0
Event Name: BEX64
Response: Nicht verfügbar
Cab Id: 0

Problem signature:
P1: explorer.exe
P2: 10.0.15063.447
P3: 951324bb
P4: HoloSI.PCShell.dll
P5: 10.0.15063.0
P6: bfebfc81
P7: 0000000000003448
P8: c0000409
P9: 0000000000000007
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE17F.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_explorer.exe_2d4def699407e74b3c924a85b1dfe7e98975b_10d58a87_29743433

Analysis symbol: 
Rechecking for solution: 0
Report Id: c093f4bc-fabc-408e-b94d-c81011c313dd
Report Status: 4196
Hashed bucket: 

Information (DbxSvc, Event ID 320)
Failed to connect to the driver: -2147024894, retrying in 1000 milliseconds

Error (Immersive-Shell, Event ID 5973)
Activation of app Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy!App failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.

Error (Application Error, Event ID 1000)
Faulting application name: explorer.exe, version: 10.0.15063.447, time stamp: 0x951324bb
Faulting module name: HoloSI.PCShell.dll, version: 10.0.15063.0, time stamp: 0xbfebfc81
Exception code: 0xc0000409
Fault offset: 0x0000000000003448
Faulting process id: 0x3414
Faulting application start time: 0x01d2f4d6473896e5
Faulting application path: C:\Windows\explorer.exe
Faulting module path: C:\Windows\System32\HoloSI.PCShell.dll
Report Id: 7394aa8e-01af-42d3-980c-c2f8a9acf95a
Faulting package full name: 
Faulting package-relative application ID: 

Information (Windows Error Reporting, Event ID 1001)
Fault bucket , type 0
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: explorer.exe
P2: 10.0.15063.447
P3: 951324bb
P4: HoloSI.PCShell.dll
P5: 10.0.15063.0
P6: bfebfc81
P7: 0000000000003448
P8: c0000409
P9: 0000000000000007
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_explorer.exe_2d4def699407e74b3c924a85b1dfe7e98975b_10d58a87_1fb8e841

Analysis symbol: 
Rechecking for solution: 0
Report Id: 7394aa8e-01af-42d3-980c-c2f8a9acf95a
Report Status: 4100
Hashed bucket: 

Any ideas what I could do?

Best Answer

  • FranklinChenFranklinChen admin
    edited July 2017 Accepted Answer

    in order to set up the Mixed Reality Simulator on my Windows 10 machine (Enterprise, 64 bit, Build 15063.447) and right after turning on the simulation toggle (thus step 6), Windows went nuts.

    @iko79 There are some known issues in Windows 10 15063 for MR development. Please upgrade your dev machine to the latest Insider Preview version(16232 currently)
    We can launch the Settings app, select "Update & Security", then "Windows Insider Program" and opt-in to Windows Insider Preview FAST Flights.
    Welcome to log issues using Feedback Hub App, please choose "Mixed Reality" category

Answers

  • FranklinChenFranklinChen admin
    edited July 2017 Accepted Answer

    in order to set up the Mixed Reality Simulator on my Windows 10 machine (Enterprise, 64 bit, Build 15063.447) and right after turning on the simulation toggle (thus step 6), Windows went nuts.

    @iko79 There are some known issues in Windows 10 15063 for MR development. Please upgrade your dev machine to the latest Insider Preview version(16232 currently)
    We can launch the Settings app, select "Update & Security", then "Windows Insider Program" and opt-in to Windows Insider Preview FAST Flights.
    Welcome to log issues using Feedback Hub App, please choose "Mixed Reality" category

  • This here did the trick, wasn't aware of the option:

    opt-in to Windows Insider Preview FAST Flights.

    May be a good idea to add this to the documentation. Thanks!

Sign In or Register to comment.