Docker Desktop Hyper-V conflicts — VirtualBox & VMware fixes

The exact symptoms

• VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)
• VMware Workstation and Hyper-V are not compatible.
• Hyper-V cannot be installed: A hypervisor is already running.
• Failed to power on virtual machine: This system has Hyper-V running.

The short version

• VirtualBox 7.0+ and VMware Workstation 16+ run alongside Docker Desktop without changes.
• VirtualBox 6.x and earlier, VMware 15 and earlier: update first; downgrading is not the answer.
• If you don’t need Hyper-V outside Docker Desktop (most people don’t), make sure Docker Desktop is on theWSL 2 backend, not Hyper-V backend. WSL 2 uses the Windows Hypervisor Platform instead, which third-party hypervisors integrate with cleanly.

How the layers actually fit together

The confusing part is that Hyper-V, WSL 2, and Windows Hypervisor Platform are three related but separate Windows features.

• Hyper-V — Microsoft’s full Type-1 hypervisor. Includes the Hyper-V Manager UI and is what Docker Desktop’s legacy backend uses.
• Windows Hypervisor Platform — a thin API for third-party hypervisors to plug into the same kernel-mode hypervisor. VirtualBox 7+, VMware 16+, and the WSL 2 backend all use this.
• WSL 2 — Microsoft’s Linux subsystem, which itself runs in a lightweight VM on top of the Windows Hypervisor Platform. Docker Desktop runs the engine inside one of these WSL 2 VMs.

Fix #1 — Update VirtualBox / VMware

90% of conflicts are resolved by upgrading. Newer releases targeted Hyper-V coexistence specifically.

• VirtualBox — 7.0 shipped with Hyper-V coexistence in 2022 and has been stable in 7.1 / 7.2.
• VMware Workstation — 16 added Windows Hypervisor Platform support in 2020 and 17 (current) is fully co-existence-friendly.

Fix #2 — Confirm Docker Desktop is on the WSL 2 backend

Docker Desktop → Settings → General. Make sure Use the WSL 2 based engine is checked. The Hyper-V backend uses the full Hyper-V hypervisor and is heavier on resources; WSL 2 uses the lighter-weight Windows Hypervisor Platform.

If Use the WSL 2 based engine is greyed out, your system likely doesn’t have WSL 2 installed yet. See WSL 2 troubleshooting.

Fix #3 — Verify the Windows feature flags

From admin PowerShell:

PS> Get-WindowsOptionalFeature -Online \
      -FeatureName VirtualMachinePlatform, HypervisorPlatform, \
                   Microsoft-Hyper-V-All

FeatureName        : VirtualMachinePlatform
State              : Enabled

FeatureName        : HypervisorPlatform
State              : Enabled

FeatureName        : Microsoft-Hyper-V-All
State              : Disabled

For Docker Desktop on WSL 2 + VirtualBox/VMware coexistence, you want VirtualMachinePlatform and HypervisorPlatform enabled, and full Hyper-V (Microsoft-Hyper-V-All) disabled. Full Hyper-V coexists less cleanly with third-party hypervisors than the lighter-weight platform alone.

To disable full Hyper-V if you previously turned it on:

PS> Disable-WindowsOptionalFeature -Online \
      -FeatureName Microsoft-Hyper-V-All -NoRestart

Reboot. Docker Desktop will continue working via WSL 2 and the Hypervisor Platform.

Fix #4 — As a last resort: switch backends

If a tool genuinely requires Hyper-V to be off entirely ( the old VirtualBox or pre-16 VMware case), you can take the opposite approach: keep Hyper-V off and accept that Docker Desktop only works on its Hyper-V backend, which currently also depends on Hyper-V. You’ll have to choose between Docker Desktop and your other hypervisor on the same boot.

The cleaner long-term answer is updating the third-party tool. Conflicts with old VirtualBox and VMware versions are the cited reason most teams move to the WSL 2 backend.

Verifying the fix

PS> docker info | findstr "Server Version"
 Server Version: 27.2.0

PS> VBoxManage --version
7.1.4r165100

PS> # Then start a VirtualBox VM and a Docker container at the same time:
PS> VBoxManage startvm "Ubuntu-24.04" --type headless
PS> docker run -d --name web -p 8080:80 nginx:alpine

If both run side-by-side, the conflict is resolved.

Frequently asked questions