Fix the Black Screen Tornado

[Bridgebrain]

In one of the major updates, a feature that generates several pre-spun virtual machines for x86 applications was added. This feature causes a litany of issues, from disabling window management (displayfusion), rearranging and changing properties of displays at random, causing crashes if too many displays are active, performance problems, issues with content loading inside one of these false displays and being inaccessible to programs, and issues with the false displays being used as monitor sources instead of the actual monitors (such as with BigScreen). 

This problem has been reported by multiple users on Reddit and various microsoft forums, and reported through the feedback center. 

All we request is that the pre-pay virtualization be a togglable option in the WMR settings control panel, so that it's available to users who want it, and can be easily disabled by users who are encountering these problems.

[#2]

@Bridgebrain Could you link to those Reddit threads, or the feedback center reports? Do you know what the name of the offending feature is, or the update that caused it? I tried looking for 'em, but I'm having trouble pinning down anything with the terminology you used here.

[#3]

@koujaku https://www.reddit.com/r/WindowsMR/comments/ezlq19/when_i_launch_the_mixed_reality_portal_windows/

Here's the best description of the problem, and while there's a solution proposed we haven't seen anything about it since. There are other threads I could track down if you need more examples. I also have screen shots of the absolutely random problems it's caused with my monitors if you'd like, and I can track down my feedback ticket if it'll help

[#4 · Accepted solution]

@Bridgebrain Ok, seems like there's a registry key fix for that right here:
https://docs.microsoft.com/en-us/windows/mixed-reality/enthusiast-guide/using-microsoft-edge#monitor...

Have you tried that, is that the one you're referring to?

[#5]

@koujaku Just found it while scrolling through the replies. If we could get that as a toggle in settings, that'd be great, but I'm glad there's a solution out there now. 

[#6]

@Bridgebrain Cool! Sounds like it's a relatively recent development, so I guess we can give it some time for them to work it into a settings toggle :) Glad there's a workable answer for now!