I am running Windows 10 20H2 圆4 with SecureBoot and HVCI enabled. In most cases, it's not a complete showstopper any more, but it has dramatic impact on performance, reliability, or, in this example, on minimum system requirements. I don't know what the status is with VirtualBox, but for VMWare Workstation, there is this Both products have workarounds, but at least VirtualBox is still extremely flaky, and dramatically slower than it is when running Windows natively.Īsk me how I know (hint: I need both VirtualBox and WSL 2 for my work!) Overall, that seems like a pretty good architecture.Įxcept it breaks competing virtualization applications, such as VirtualBox or VMWare Workstation.

As long as you can live without HVCI and WSL 2 (and probably more features I haven't discovered yet). That is what allows HVCI, as well as a number of other Windows features, to work.Īll that happens behind the scenes, and you can disable it with a registry setting and a reboot. Hyper-V then runs Windows 10 as a virtual machine. Here is in more detail (but still simplified) what happens:īy default, when you boot Windows 10, you actually are booting Hyper-V first. This is not really new in Windows 11 Windows 10 already has a similar issue. HVCI will interfere with other hypervisors, such as VirtualBox or VMWare Workstation. It's probably not a complete showstopper, but for those who are affected, it can have a very big impact. Here is another tidbit that could become an issue for many people, especially software developers.

Virtualbox vs vmware .pdf