The new Microsoft Edge is now available for download, but customers can also wait for a future update to install it with Windows 10, following a measured roll-out approach over the next several months.
With this news, we wanted to let Windows Mixed Reality VR headset customers know what to expect from the new Microsoft Edge and show off pending updates for an improved browsing experience in Windows Mixed Reality.
The new Microsoft Edge adopts the Chromium open source project on the desktop to create better compatibility for customers and less fragmentation of the web for web developers. It will also support WebXR at launch, the new standard for creating immersive web experiences for VR headsets, in place of WebVR.
[!IMPORTANT] When you install Microsoft Edge on an up-to-date Windows 10 device, it will replace the previous (legacy) version on your PC.
Windows Mixed Reality VR headset customers who want to use the new Microsoft Edge in the mixed reality home should upgrade to Windows 10 Version 1903 or later for native support of Win32 applications (like the new Microsoft Edge) in the mixed reality home. Check Windows Update or manually install the latest version of Windows 10.
For the best possible Microsoft Edge experience in the mixed reality home, we also recommend waiting for some key Windows Mixed Reality optimizations for the new Microsoft Edge arriving with the 2020-01 Cumulative update for Windows 10 Version 1903 (or later), which should be available in Windows Update by the end of January.
[!IMPORTANT] If you opt to download the new Microsoft Edge before taking these updates, there will be some known issues with its behavior in Windows Mixed Reality (which you can read about below).
After taking the 2020-01 Cumulative update for Windows 10 Version 1903 (or later), virtual monitors will appear as generic physical monitors in Settings > System > Display during Windows Mixed Reality sessions. Some customers, especially with more than one physical monitor, may notice issues with desktop layout and input handling as a result.
Why this happens
Support for classic Win32 applications in Windows Mixed Reality was introduced with the Windows 10 May 2019 Update. To enable this support, a virtual monitor must be created to host the Win32 application. Each time a new Win32 application is launched, another virtual monitor has to be created. Unfortunately, creating a virtual monitor is an intensive task that can cause the headset display to briefly freeze. Customers offered feedback that this was an uncomfortable and disruptive experience. Because of feedback and increased Win32 application usage, we made the decision to pre-allocate three virtual monitors during startup of Windows Mixed Reality. This prevents disruption and enables customers to launch up to three concurrent Win32 applications without experiencing the headset display freeze.
Workaround
We’ve since received feedback that some customers, especially those with multiple physical monitors, would prefer to disable this virtual monitor pre-allocation. To give customers control, we’ve enabled a workaround that involves changing a registry key value, which is available with the following Windows Updates:
[!NOTE] Modifying registry key values is intended for advanced users.
[!WARNING] Disabling virtual monitor pre-allocation may result in your headset display briefly freezing when you launch a Win32 application (such as Steam, the new Microsoft Edge, or Google Chrome) in Windows Mixed Reality.
To disable virtual monitor pre-allocation:
Virtual monitors will now allocate when you attempt to launch a Win32 application in Windows Mixed Reality instead of pre-allocating. To reset this and re-enable virtual monitor pre-allocation, return the DWORD “Value data” to 1.