My question is, does anyone have an idea where this is coming from, what is the actual thing causing it, is it a bug on Windows' side, in WHP, that Microsoft has yet to address, or did they make some change in the implementation of WHP on these processors and these hypervisors (VMware, VirtualBox) have yet to adapt to it? It works neither in VMware, nor in VirtualBox. But, unfortunately, booting any VM does not work with the above setup on Ryzen 5000, I experience this problem too. These features activate Hyper-V on the underlying Windows install, so in order to use VMware, you are required to enable it integration with the Windows Hypervisor Platform which was relatively recently added. Virtualization based security (core isolation) possibly enabled in Windows Security Virtual Machine Platform possibly enabled Windows Subsystem for Linux 2 possibly enabled
Windows 11 build 22000.176, or largely any build that supports the Windows Hypervisor Platform VMware Workstation 16.1.2 Pro (the latest) or any version that supports the Windows Hypervisor Platform As far as I can tell, there are various reports online about how launching virtual machines fails on systems that meet this specific setup on a Ryzen 5000-series based CPU (I have a Ryzen 5900x, specifically):
0 kommentar(er)
