This is problematic because to keep performance fast under virtualization, the CPU exposes hardware a feature to accelerate virtual memory translation and now that feature is used by Windows and it cannot be shared and used by VirtualBox.
In turn, VirtualBox attempts to run a virtual machine inside the hypervisor virtual machine. Attempting to disable VPS lead me to pain and misery and in the end nothing worked.
#Windows 10 hyper v vs virtualbox Patch
Some hacks are floating around to patch the executable to allow the check to be skipped and it does appear to work (although I haven’t tested it myself). From my understanding, what this means is that running this program within a virtual machine isn’t supported or recommended.
This is the root cause of my woes.ĪMD Ryzen Master complains (see also this) that Virtualization Based Security (VPS) is enabled. When the hypervisor is used, Windows runs inside it, much like a guest OS runs inside a host OS in a virtual machine setup. It also allows isolation of various security components, further improving kernel safety.
This allows you to run virtual machines (without VMWare, VirtualBox, or some other similar program). Over the last few years, Windows has been roling out a hypervisor of its own: Hyper-V. I wasn’t too sure how it happened and I spent a good deal of time chasing what went wrong so I am documenting my process and result here in hope that it might help others as well. This weekend, I noticed that AMD Ryzen Master (a great tool to control your CPU when profiling code performance) and VirtualBox both stopped working for me under Windows 10.