I experienced the same problem, at first thinking the Intel Alder Lake performance/efficient core architecture was at fault (someone else suspected that too at https://forums.virtualbox.org/viewtopic.php?t=108745), but then noticed the green turtle symbol and found https://forums.virtualbox.org/viewtopic.php?f=25&t=99390
I tried everything that the second VirtualBox thread mentioned:
bcdedit /set hypervisorlaunchtype off (although I couldn't do the full
power cycle since I can't remove the laptop battery)
DISM /Online /Disable-Feature:Microsoft-Hyper-V
I put Enabled to 0 under HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Control, DeviceGuard, Scenarios, SystemGuard.
I put EnableVirtualizationBaseSecurity and EnableVirtualizationBasedSecurity just in case there was a typo to 0 under HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Control, DeviceGuard.
I set Memory Integrity to Off
I checked BIOS settings, disabling Secure Boot and some features that seemed to offer additional security by using virtualization
...but I couldn't get the green turtle away, even after reboots. msinfo32.exe showed that virtualization-based security was still in use.
I think msinfo32.exe here is key tool: if it reports that virtualization-based security is in use, VirtualBox has no chance of working. Apparently VMWare works better, not sure why, either it's possible it integrates better with Windows virtualization support, or it's possible VMWare has more responsive emulation mode when emulated virtualization has to be used.
Naturally, I did check that virtualization was enabled in BIOS settings.
Then I found the solution:
-
Go to Control Panel, select Programs and Features, select Turn Windows features on or off
-
Remove Hyper-V
-
Remove Windows Hypervisor Platform
-
Remove Virtual Machine Platform
-
Save settings and reboot
In my case,
(Réponse tronquée)
