Potentially similar issue to
viewtopic.php?f=6&t=109424.
I have a Windows 10 guest running on a Windows 10 (22H2) host. Left for lunch and came back to see the title critical error message, and the VM was stuck.
I am aware that I have this option set:
Code: Select all
bcdedit /set hypervisorlaunchtype auto
I use WSL2 and Docker, which don't work unless this setting is enabled. I have been trying to get VirtualBox to play nice. I also have Hyper-V and Windows Hypervisor Platform enabled on the host. There's a lot of conflicting information out there as to whether this can work, but I'll at least do due diligence and post logs if that possibly helps someone.