I hit this when installing Docker Desktop inside a Hyper-V virtual machine for a test lab:
"Virtualization support not detected. Docker Desktop couldn't start as virtualization support is not enabled on your machine."
Docker Desktop needs hardware virtualization (Intel VT-x or AMD-V) for its WSL 2 or Hyper-V backend. Inside a VM, the hypervisor hides those CPU features from the guest unless you turn on nested virtualization. On a physical PC, the usual causes are virtualization switched off in the BIOS or missing Windows features. Both cases are covered below.
Applies to: Docker Desktop on Windows 10 / 11, running on physical hardware, Hyper-V, VMware or Azure VMs.
Step 1: Find out where the problem is
Run this inside the machine where Docker is installed:
systeminfo | Select-String "Hyper-V Requirements", "Virtualization", "hypervisor"
- "A hypervisor has been detected" means virtualization is available. Skip to Step 4 (Windows features).
- "Virtualization Enabled In Firmware: No" on a physical PC means you need to turn it on in the BIOS/UEFI (Step 3).
- No virtualization listed inside a VM means nested virtualization is off (Step 2).
Task Manager shows the same thing: Performance → CPU → Virtualization: Enabled/Disabled.
Step 2: Enable nested virtualization (Docker inside a VM)
Hyper-V
Run these on the Hyper-V host, not inside the VM.
-
Shut down the VM. The setting can't change while it's running:
Stop-VM -Name "YourVMName" -
Expose the virtualization extensions to the guest:
Set-VMProcessor -VMName "YourVMName" -ExposeVirtualizationExtensions $true -
Microsoft lists Dynamic Memory as unsupported with nested virtualization, so turn it off and give the VM enough fixed RAM (at least 4 GB for Docker):
Set-VMMemory -VMName "YourVMName" -DynamicMemoryEnabled $false -StartupBytes 8GB -
Check, then start the VM:
Get-VMProcessor -VMName "YourVMName" | Select-Object ExposeVirtualizationExtensions Start-VM -Name "YourVMName"
ExposeVirtualizationExtensions should be True. Log in and start Docker Desktop again.
VMware Workstation / ESXi
With the VM powered off, open VM settings → Processors, tick Virtualize Intel VT-x/EPT or AMD-V/RVI (Workstation) or Expose hardware assisted virtualization to the guest OS (ESXi), then power on.
Azure VMs
Nested virtualization only works on VM sizes that support it. If the setting isn't available, resize the VM to a size that supports nested virtualization (check the VM size documentation), then follow the Windows feature steps below.
Step 3: Enable virtualization in the BIOS (physical PCs)
Restart into BIOS/UEFI setup and enable Intel Virtualization Technology (VT-x) or SVM Mode (AMD). It's usually under Advanced → CPU Configuration. Save and restart.
Step 4: Turn on the Windows features Docker needs
WSL 2 backend (the default):
wsl --install
Or enable the features directly:
dism /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
dism /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
Hyper-V backend (Pro / Enterprise only):
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All
Restart after enabling features.
Step 5: Make sure the hypervisor is set to start
Some tools, and some older troubleshooting guides, switch the Windows hypervisor off at boot:
bcdedit /enum | findstr -i hypervisorlaunchtype
If it says Off, turn it back on and restart:
bcdedit /set hypervisorlaunchtype auto
Still not working?
- Run
wsl --updateandwsl --statusto make sure WSL itself is current. - Restart the Docker Desktop Service and quit Docker completely (system tray → Quit) before reopening it.
- In nested setups, the host and the VM both need a recent Windows build. Nested virtualization on AMD CPUs requires Windows 11 or Windows Server 2022 or later on the host.
Related: Fix "This PC can't run Windows 11" for a Hyper-V VM · Create a new virtual machine in VMware Workstation