Immersive headset known issues

This is the current list of known issues for Windows Mixed Realty developers targeting PC-connected immersive headsets. Check here first if you are seeing an odd behavior. This list will be kept updated as new issues are discovered or reported, or as issues are addressed in future software updates.

Graphics Card

Known issue as of Windows 10 Creators Update (15063)

Laptops with Nvidia 1060 graphics and an integrated GPU may experience a black screen when launching an immersive app built with Unity. This is due to the app rendering on the incorrect adapter. If you encounter this issue, check if in Nvidia settings it's set to use the discrete GPU only. If it is, change the setting back to "auto".

Windows Mixed Reality uninstall

Known issue as of Windows 10 Creators Update (15063)

Uninstall of Windows Mixed Reality features in the Settings app may unexpectedly fail, which could cause the Mixed Reality Portal app to be in an incomplete install state and prevent successful reinstall of Windows Mixed Reality features later.

To manually remove remaining Windows Mixed Reality components, restart your PC first, and then follow these steps:

  1. Remove the following registry values:
    Note: For HKEY_CURRENT_USER values, the registry value must be removed for each user who used Windows Mixed Reality. A complete cleaning would requires each user to log in and have the values removed.
    • Remove "FirstRunSucceeded" from HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Holographic
    • Remove "PreferDesktopSpeaker" and "PreferDesktopMic" from HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Holographic\SpeechAndAudio
    • Remove "DisableSpeechInput" from HKEY_CURRENT_USER\Software\Microsoft\Speech_OneCore\Settings\Holographic
    • Remove "DeviceId" and "Mode" from HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\PerceptionSimulationExtensions
  2. Remove "RoomBounds.json" from C:\Users\{username}\AppData\Local\Packages\Microsoft.Windows.HolographicFirstRun_cw5n1h2txyewy\LocalState
    Note: This file must be removed for each user who used Windows Mixed Reality.
  3. Remove the contents of the "SpatialStore" folder (but not the folder itself) from C:\ProgramData\WindowsHolographicDevices\SpatialStore
  4. Remove Feature-On-Demand CAB:
    Mixed Reality relies on a Feature-On-Demand CAB to run. This CAB is downloaded during a user’s initial experience and should be removed. To remove the FOD, open PowerShell as an Administrator and run:
    1. Dism /online /Get-Capabilities
      Note: Copy the Capability Identity that begins with Analog.Holographic.Desktop. If that capability can’t be found, then the FOD isn’t installed.
    2. Dism /online /Remove-Capability /CapabilityName:copied Capability Identity
  5. Restart your PC

Windows Mixed Reality boundary feature

Known issue for Windows Insider update (16189)

There is a bug preventing the room boundary from showing. If setting up a room, you cannot get through the learnings experience when first using the headset.

Workaround #1 – unplug Xbox controller during setup. Workaround #2 – skip boundary when running setup in the Mixed Reality Portal app.

In app experiences, the Boundary may not show up, even if defined during current/previous setup. Be sure to check if your boundary is showing. If the boundary doesn't show in the headset, use caution and there will be a fix in the next flight.