Docker Desktop refuses to start because it can't find a hypervisor it's allowed to use. On Windows the cause is almost always one of three things: hardware virtualization is disabled in firmware (VT-x on Intel, SVM on AMD), a competing hypervisor has locked the CPU feature, or the Windows features Docker needs β€” Hyper-V, Virtual Machine Platform, WSL 2 β€” aren't switched on. The fix lives in UEFI/BIOS settings and Windows Features, not in Docker itself. If you're on a company-managed machine, the setting may be blocked by policy and only your IT admin can release it.

That message is blunt, and it shows up at the worst moment β€” usually the morning you need a container running. Work through the checks below in order. Most people solve it at step one.

Check Task Manager Before You Touch the BIOS

Task Manager tells you whether the CPU feature is on before you reboot into firmware. Open it with Ctrl+Shift+Esc, go to the Performance tab, click CPU, and look for "Virtualization" in the bottom-right block of details. "Enabled" means hardware virtualization is switched on and your problem is in Windows. "Disabled" means you need firmware access.

Two other fields matter on the same screen. "Hyper-V support" shows whether the platform exposes virtualization to Windows, and "Virtual machine" appears if Windows itself is running inside a VM. That last one explains a whole class of failures: Docker Desktop cannot nest inside another hypervisor unless the host explicitly passes virtualization through, and many corporate VDI setups don't.

Write down the CPU model while you're there β€” it's the line above the clock speed. Intel chips need "Intel Virtualization Technology" or "VT-x"; AMD chips need "SVM Mode" or "AMD-V." Knowing which brand you're on saves you hunting through the wrong menu later, because firmware vendors use different labels for the same switch.

If everything reads Enabled, skip the firmware section entirely and go to the Windows Features check. Running a reboot you don't need wastes five minutes and, on some laptops with BitLocker, triggers a recovery-key prompt if firmware settings change.

Enable VT-x or SVM in UEFI/BIOS: The Exact Menu Names

Firmware interfaces are not standardized, so the setting hides under different names per vendor. The table below covers the labels you'll actually see on the major brands. Enter firmware by restarting and pressing the setup key during boot β€” usually F2, Del, F10, or Esc, and the splash screen names it.

Vendor Setup key Menu path Setting label
Dell F2 Virtualization Support Virtualization
HP F10 System Configuration β†’ BIOS Virtualization Technology (VTx)
Lenovo (ThinkPad) F1 or Enter Security β†’ Virtualization Intel Virtualization Technology
ASUS Del or F2 Advanced β†’ CPU Configuration SVM Mode (AMD) / Intel Virtualization Technology
Acer F2 Advanced Intel Virtualization Technology / AMD-V
Microsoft Surface Volume Up + Power Security β†’ Device Security Virtualization (may be absent on some models)

The sequence is short. Restart the machine and tap the setup key before Windows loads. Navigate to the menu named for your vendor in the table above, highlight the virtualization entry, and change it from Disabled to Enabled. Save and exit β€” F10 is the common shortcut β€” and let Windows boot normally.

Failure handling matters here. If the setting is greyed out, the machine is likely under management: check with your IT department whether firmware is locked by password or policy. If you enable it and Windows still reports Disabled, your antivirus may be using its own hypervisor β€” more on that below. And if you're on a Surface or a locked-down corporate laptop where the option simply doesn't exist, virtualization may be disabled at the firmware level by the manufacturer, which no amount of menu-hunting will change.

One edge case: some laptops ship with "Intel VT-d" or "AMD IOMMU" separate from VT-x/SVM. Those are I/O virtualization features and aren't required for Docker Desktop, though enabling them is harmless. Don't confuse the two if the main switch is already on.

Turn On Hyper-V, Virtual Machine Platform, and WSL 2 in Windows Features

If Task Manager says virtualization is enabled, the gap is in Windows. Docker Desktop on Windows needs the Windows Subsystem for Linux 2 backend (the default) or the legacy Hyper-V backend, and both depend on Windows features being switched on. Press Win+R, type optionalfeatures, and press Enter.

In the Windows Features dialog, tick "Virtual Machine Platform" and "Windows Subsystem for Linux." If you're using the Hyper-V backend instead of WSL 2, tick "Hyper-V" as well β€” but note that Hyper-V and some third-party hypervisors conflict, which is the next section's problem. Click OK and let Windows install the components, then reboot when prompted.

After the reboot, open an elevated PowerShell window and confirm the pieces are live. Run wsl --status to check the default WSL version; it should report 2. Run wsl --update to pull the current kernel. If wsl --status errors out, the feature didn't install correctly and you should rerun the optional-features step.

The failure case that catches people: Windows 10 Home doesn't include Hyper-V, so the legacy backend isn't available at all. WSL 2 with Virtual Machine Platform does work on Home, which is why Docker Desktop's default backend matters β€” if you're on Home edition, stick with WSL 2 and don't waste time looking for the Hyper-V checkbox. Windows 11 Home behaves the same way.

When Another Hypervisor Has Locked the CPU Feature

Hardware virtualization is a single resource, and only one hypervisor can hold it at a time on some configurations. If you've enabled VT-x in firmware and Windows still reports it as unavailable, a competing product has claimed it. The usual suspects are third-party Android emulators, older VMware Workstation builds, VirtualBox with Hyper-V disabled in its own settings, and some endpoint-security agents that run their own lightweight hypervisor.

The diagnostic is the "Hyper-V support" field in Task Manager. If it says "Yes" but Docker still complains, the Windows hypervisor platform is present but Docker's backend isn't binding to it. If it says "No" while virtualization reads "Enabled," something else owns the feature.

Resolution depends on the culprit. For VirtualBox, the current release supports the Hyper-V platform and coexists with it β€” older versions did not. For Android emulators, check their settings for an explicit "Hyper-V" or "Windows Hypervisor Platform" compatibility toggle. For security software running a hypervisor, you generally can't disable it without breaking protection, so contact IT rather than fighting it.

One more conflict worth naming: enabling the legacy Hyper-V backend in Docker Desktop and then switching to WSL 2 without disabling Hyper-V can leave both fighting for the platform. Pick one backend in Docker Desktop's Settings β†’ General and stay with it.

Read the Docker Desktop Logs to Confirm the Real Cause

Docker Desktop writes a diagnostic log that states exactly which check failed, which beats guessing. On Windows the file sits at %LOCALAPPDATA%\Docker\log.txt, and the Settings β†’ Troubleshoot screen offers a "Gather diagnostics" bundle if you need to hand something to IT. Search the log for "virtualization" and read the surrounding lines.

The log distinguishes between "virtualization support not detected" (firmware or CPU feature missing) and backend errors like "WSL 2 is not installed" or "Hyper-V is not enabled." The message in the Docker Desktop window is generic; the log is specific. That distinction is the difference between a BIOS trip and a Windows Features trip.

If the log points at WSL, run wsl --shutdown and restart Docker Desktop before doing anything more drastic. A stale WSL instance is a common cause of a startup failure that looks like a virtualization problem but isn't.

If you're passing this to an admin, include the log excerpt and the Task Manager CPU panel screenshot. It tells them in ten seconds whether the fix is firmware, policy, or a Windows feature β€” and saves the round trip of them asking you to check again.

What IT Admins Can Unblock That You Cannot

On a managed device, several layers can override your local settings, and recognizing them prevents a lot of wasted effort. Group Policy can disable Hyper-V, Windows Defender Application Guard can occupy the hypervisor, and firmware passwords can lock the virtualization switch. None of these are fixable from your side, and none of them are Docker's fault.

Ask your admin for three specific things rather than a vague "please enable virtualization." First, confirm that VT-x or SVM is enabled in the machine's firmware. Second, confirm that Virtual Machine Platform and WSL 2 (or Hyper-V) are permitted by policy. Third, ask whether the endpoint security agent uses a hypervisor and whether Docker Desktop is on the approved-software list. The third question resolves most corporate failures on its own.

If you're running Windows 11 with Windows Sandbox or the Memory Integrity feature (Core Isolation) enabled, those use virtualization too. Memory Integrity, part of Windows Security under Device Security, runs the hypervisor and can coexist with Docker but sometimes needs a reboot after you change Hyper-V settings before Docker sees the platform cleanly.

The practical takeaway: when the message appears on a work laptop, the fix usually isn't technical knowledge, it's permissions. Get the log, name the three settings, and escalate with specifics.

Docker Desktop, WSL 2, and Hyper-V: Which Stack You Actually Need

People trip over this because Docker Desktop's message doesn't say which backend failed. The three stacks have different requirements, and matching your Windows edition to the right one is most of the battle.

Backend Windows editions Features required Typical use
WSL 2 (default) 10 Home, 10 Pro, 10 Enterprise, 11 Home, 11 Pro Virtual Machine Platform, WSL, firmware virtualization General development, Linux containers
Hyper-V 10 Pro/Enterprise, 11 Pro/Enterprise Hyper-V, firmware virtualization Windows containers, enterprise setups
Remote Any edition None locally Managed Docker environments, CI

WSL 2 is the default since Docker Desktop 2.x-era releases and the right choice for nearly everyone on Windows 10 or 11 Home. Hyper-V is required if you need Windows containers, which Home edition can't run. Remote mode sidesteps local virtualization entirely β€” worth considering if your machine is locked down.

The verdict splits cleanly. If you're on Home, use WSL 2 and don't chase Hyper-V. If you need Windows containers, you need Pro or Enterprise and the Hyper-V backend. If you can't change firmware or features at all, ask about a remote Docker host instead of fighting the local machine.

A real drawback of the WSL 2 default: it runs a full Linux VM under the hood, and its memory footprint grows with use. You can cap it in .wslconfig, but a machine with 8GB of RAM running Docker, WSL 2, and an IDE will feel the strain.

Verify the Fix and Handle the Reboot Loop

After enabling firmware virtualization and the Windows features, you expect Docker Desktop to start cleanly. When it doesn't, the culprit is usually a stale state rather than a missing setting. Close Docker Desktop from the system tray, run wsl --shutdown in PowerShell, and reopen it.

Confirm each layer independently before blaming Docker. systeminfo in an elevated prompt reports Hyper-V requirements at the bottom and will say whether virtualization is enabled in firmware. wsl --status confirms the WSL version. Docker Desktop's own Settings β†’ General shows which backend is selected. All three agreeing means Docker should start.

The reboot-loop failure case: if Windows prompts for a restart after enabling features and you skip it, Docker Desktop will keep failing because the components aren't loaded into the kernel. Restart properly, not with Fast Startup β€” shut down fully or use Restart, since Fast Startup can leave firmware-related changes unapplied.

Corrupted WSL distributions are another edge case. If wsl --list --verbose shows your distro in a broken state, wsl --unregister and reinstall it. Docker's containers live in a separate WSL distribution (docker-desktop and docker-desktop-data), so unregistering your own distro won't touch them.

Common Fixes That Waste Your Time

The internet is full of advice that doesn't apply, and knowing what to skip is as useful as knowing what to try. Reinstalling Docker Desktop almost never fixes a virtualization-support error, because the problem is below Docker in the stack. Save the download.

Disabling antivirus entirely is another bad idea β€” it's a security risk and rarely the actual cause. Check whether your security product has a hypervisor-based feature (many do) before disabling anything, and if it does, the fix is a configuration change or an IT conversation, not switching off protection.

Hyper-V "cleanup" scripts that force-disabled the feature and re-enabled it sometimes work, but they're blunt instruments. If you're running WSL 2, disabling Hyper-V is irrelevant to your problem. And "just buy a new laptop" advice ignores that most corporate laptops already support virtualization β€” it's switched off or blocked, not missing.

The one piece of folk wisdom that holds: some older BIOS versions on specific laptop models shipped with broken virtualization support that a firmware update fixed. Check your manufacturer's support site for a BIOS update if the setting exists but doesn't stick after saving.

FAQ

Does "virtualization support not detected" always mean I need to go into the BIOS?

No. Task Manager distinguishes the two cases in seconds. If the Performance β†’ CPU panel shows Virtualization "Enabled," the firmware is fine and your problem is Windows features or a competing hypervisor. Only a "Disabled" reading sends you into UEFI/BIOS.

Will enabling Hyper-V fix Docker Desktop on Windows 10 Home?

It cannot, because Windows 10 Home doesn't include Hyper-V. Home edition users should use the WSL 2 backend with Virtual Machine Platform, which is Docker Desktop's default. The Hyper-V option exists for Pro and Enterprise users running Windows containers.

Why does Docker Desktop work after a clean boot but fail after using an Android emulator?

Emulators like BlueStacks and some older VMware builds claim the hypervisor platform and may not release it cleanly. Close the emulator fully, run wsl --shutdown, then restart Docker Desktop. Current VirtualBox releases support Hyper-V coexistence, so updating it can remove the conflict.

Can I run Docker Desktop without enabling virtualization at all?

Only in remote mode, where Docker Desktop connects to a Docker engine on another machine or a cloud host. The local engine requires a hypervisor on Windows. On macOS, virtualization is also required, though the failure message reads differently.

My admin says virtualization is enabled but Windows reports it off β€” what gives?

A security agent or Group Policy is likely holding the hypervisor. Ask your admin specifically whether endpoint protection uses a hypervisor, and request that Docker Desktop be added to the approved list. This is a permissions fix, not a settings one.

How much RAM should I reserve for Docker Desktop with WSL 2?

There's no fixed number, but cap WSL 2's memory in .wslconfig at roughly half your total RAM on machines with 8GB, and Docker's own Settings β†’ Resources panel lets you set the container memory ceiling. Leaving both uncapped on an 8GB laptop causes swapping and slow startup.

Does Docker Desktop run on Windows 11 ARM laptops?

It does, using the WSL 2 backend, and it runs on Windows 11 ARM devices natively. The virtualization requirement is the same β€” firmware virtualization must be enabled, and Windows 11 ARM devices typically enable it by default.

What should I send my IT admin to speed this up?

Send the Docker Desktop diagnostic bundle from Settings β†’ Troubleshoot, plus a screenshot of Task Manager's CPU panel showing the Virtualization and Hyper-V support fields. Name the three settings you need confirmed: firmware virtualization, Virtual Machine Platform/WSL 2 policy, and security-agent hypervisor status.

The steps above are general troubleshooting guidance for a development tool, not a security or IT policy recommendation. On managed devices, follow your organization's IT procedures before changing firmware or system features, and consult your IT administrator rather than disabling endpoint protection. If a change to firmware triggers a BitLocker recovery prompt and you don't hold the key, stop and contact your IT help desk.