Windows Mixed Reality improvements and known issues with Windows 10 Redstone 5 build 17686

Windows Mixed Reality improvements and known issues with Windows 10 Redstone 5 build 17686

Today Microsoft released a new Windows 10 Redstone 5 build for Windows Insiders and it contains a number of improvements for Windows Mixed Reality and one known issues that may want you to skip this build for now.

The main change is you no longer need a monitor connected to your PC when running Mixed Reality. So you could put a PC in a backpack and take Windows Mixed Reality with you on the go. You still need a monitor to do the initial setup but after that you are free to go monitor-less! The other change is a Camera Capture UI API so apps can capture photos of the Windows Mixed Reality environment.

Just a word of warning, after updating the Mixed Reality settings are not preserved so you will need to reset up your apps and objects:

In the new build:

This build no longer requires a physical monitor to be connected while running Mixed Reality in cases such as backpack PCs. Setting up WMR for the first time in Mixed Reality Portal and unlocking the PC on the sign in screen still, require a monitor to be connected initially. However, you can configure auto login to prevent needing to sign in for subsequent usage here. Using Windows Mixed Reality while standing requires setting up a room boundary.

Apps running in Windows Mixed Reality can now make use of the Camera Capture UI API to capture images of the mixed reality world using the system capture experience. Try running Mail in the Cliff House and inserting an image from your camera in a new message to share an image of the scenic view.

We’ve also made some adjustments to the mixed reality video capture experience in this build to make it easier to stop videos from the Start menu.

Known issue:

After update, Mixed Reality Portal will reinstall the Mixed Reality Software and environment settings will not be preserved. If you need your Mixed Reality home experience to persist, we recommend skipping this build until these issues are fixed.


Leave a Reply

Your email address will not be published. Required fields are marked *