# Hyper-V, WSL2, VMware and VirtualBox on one Windows PC

> Understand why WSL2 needs virtualization, how Hyper-V coexists with VMware/VirtualBox, and what to check before disabling a feature.

**Tested on**

- Build: 26300.9457
- Edition: Pro (26H2)
- Architecture: x64
- Evidence: E1
- Verified: 2026-10-28

## The short answer

WSL2 is a lightweight VM. It needs the Windows hypervisor/virtual machine platform. Once that hypervisor is running, other VM products must either cooperate with it or use a slower compatibility path.

There is no universal “turn Hyper-V off for gaming” answer. If you need WSL2, Docker Desktop, Windows Sandbox or Hyper-V VMs, the hypervisor stays. If you need a specific VMware/VirtualBox feature, check that vendor’s current Hyper-V/WHPX guidance.

## What depends on what

| Feature | Needs hypervisor? | Notes |
|---|---|---|
| WSL2 | Yes | Virtual Machine Platform / Hyper-V |
| Docker Desktop (WSL2 backend) | Yes | Uses WSL2 |
| Windows Sandbox | Yes | Hyper-V-based |
| Hyper-V Manager/VMs | Yes | Direct |
| VMware Workstation/Player | Uses WHPX or its own mode | Check vendor docs; performance differs |
| VirtualBox | Check version/vendor | Hyper-V coexistence has historically been limited |
| Android emulators | Often | Some use WHPX/Hyper-V |

## Check the current state

```powershell
systeminfo | Select-String "Hyper-V"
Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
Get-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform
bcdedit /enum {current}
```

`hypervisorlaunchtype Auto` means the Windows hypervisor starts at boot. `Off` means it does not. Changing this requires a reboot.

## Coexistence rules

- **Do not disable Hyper-V to “fix” a game** unless you have measured the problem and do not need WSL2/Docker/Sandbox.
- **Use one VM stack at a time** for heavy workloads; running Hyper-V, VMware and VirtualBox simultaneously is a support and performance gamble.
- **Enable nested virtualization** only where the outer hypervisor supports it. On PVE, set CPU type `host` and expose VMX/SVM if you need it.
- **Check WHPX** for VMware/VirtualBox; a vendor may require a specific version or setting.
- **Do not stack “gaming tweaks”** that disable virtualization, VBS and Hyper-V at the same time. You will lose WSL2 and may weaken security.

> **Caution: Virtualization is not a performance switch**
>
> Disabling the hypervisor can change benchmark results, but it also removes WSL2, Windows Sandbox and Hyper-V. Decide by workload, not by a forum claim.

## If a VM refuses to start

1. Check the vendor’s Hyper-V/WHPX requirements for your exact version.
2. Confirm Virtual Machine Platform/Hyper-V state.
3. Check Windows features and reboot.
4. Try the vendor’s compatibility mode.
5. If you must switch modes, do it deliberately and record what stops working.

## Lab note

Our PVE host runs Windows VMs with `host` CPU and nested virtualization where needed. We do not run VMware/VirtualBox inside the Windows lab; this page is E1 guidance, not a coexistence test matrix.

## Sources

- [Microsoft — WSL install](https://learn.microsoft.com/en-us/windows/wsl/install)
- [Microsoft — Hyper-V virtualization](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/hyper-v-technology-overview)
- [Microsoft — Windows Hypervisor Platform](https://learn.microsoft.com/en-us/virtualization/api/)

---

Source: https://winbook.fyi/en/windows/dev/hyperv-coexistence/