You start a virtual machine in VirtualBox and get an error such as “VT-x is not available” or “AMD-V is disabled,” or the machine runs extremely slowly with a green turtle icon in the status bar. Virtualization is enabled in the BIOS, so the message makes no sense. When Windows 10 PAGODA127 RESMI VirtualBox not working with Hyper-V causes these problems, Windows is already using the processor’s virtualisation features for itself.
Hyper-V is Microsoft’s own virtualisation platform. When it, or features built on it, are active, Windows takes control of the virtualisation hardware. Older VirtualBox versions could not run at all in that situation, while newer versions run through Hyper-V’s interface but much more slowly.
Hyper-V is turned on not only by the Hyper-V feature itself, but also by Windows Subsystem for Linux 2, Windows Sandbox, Virtual Machine Platform, Docker Desktop, and Memory Integrity.
Choosing which platform you need, and turning the others off, solves the conflict.
Why This Happens
VirtualBox conflicts for these reasons:
- The Hyper-V feature is enabled.
- WSL 2, Windows Sandbox, or Virtual Machine Platform uses the hypervisor.
- Memory Integrity, part of Core isolation, keeps the hypervisor running.
- An old VirtualBox version does not support running alongside Hyper-V.
The green turtle icon in VirtualBox means it is running through Hyper-V instead of directly on the hardware.
Start With These Basic Checks
Check what is active.
- Update VirtualBox to the latest version from virtualbox.org.
- In Control Panel > Programs, open “Turn Windows features on or off.”
- Look at Hyper-V, Virtual Machine Platform, Windows Hypervisor Platform, and Windows Sandbox.
- Decide whether you need them, for example for WSL 2 or Docker.
- If you do not, untick them and restart.
Going a Step Further
Turn off the hypervisor completely.
- Open Windows Security > Device security > Core isolation details and turn off Memory integrity, if you accept the security trade-off.
- Open Command Prompt as administrator and type bcdedit /set hypervisorlaunchtype off, then press Enter.
- Restart the PC.
- Start VirtualBox and check that the turtle icon is gone.
- To restore Hyper-V later, run bcdedit /set hypervisorlaunchtype auto and restart.
If you need WSL 2 or Docker, keep Hyper-V on and accept slower VirtualBox performance, or use Hyper-V for your virtual machines instead.
A Word of Caution
Turning off Memory integrity lowers protection against some attacks. Weigh that before disabling it, and turn it back on when you no longer need VirtualBox at full speed.
Final Thoughts
VirtualBox conflicts with Hyper-V because Windows already uses the virtualisation hardware. Update VirtualBox, disable Hyper-V-based features you do not need, and set hypervisorlaunchtype off for full speed.
