You installed Docker Desktop, everything looked fine — and then nothing. Docker refuses to start on Windows 11. The icon spins, shows an error, or just sits there doing nothing. If you're using WSL 2 (Windows Subsystem for Linux 2), there are a handful of very specific causes for this — and every single one of them is fixable.

This guide covers every known reason Docker fails to start on Windows 11 with WSL 2, in order from most common to least common. Work through them step by step.

⚠️ Before You Begin
Make sure your Windows 11 is fully updated before troubleshooting Docker. Go to Settings → Windows Update → Check for updates and install everything. Many Docker/WSL2 issues are fixed in Windows updates.

Why Docker Fails to Start on Windows 11 with WSL 2

Docker Desktop on Windows 11 relies on WSL 2 as its backend engine. When any part of that chain breaks — virtualisation, WSL, the Linux kernel, or Docker itself — Docker refuses to start. The most common causes are:

  • Virtualisation (VT-x/AMD-V) is disabled in BIOS/UEFI
  • Hyper-V or Virtual Machine Platform is not enabled in Windows
  • WSL 2 is not properly installed or is outdated
  • The WSL 2 Linux kernel needs updating
  • Docker Desktop version is outdated or corrupted
  • Windows Subsystem for Linux feature is disabled
  • Conflicting virtualisation software (VMware, VirtualBox)
  • Antivirus blocking Docker's network components

Step 1 — Enable Virtualisation in BIOS/UEFI

This is the most common root cause. Docker with WSL 2 requires hardware virtualisation to be enabled in your laptop's BIOS. Many laptops ship with it disabled by default.

How to check if virtualisation is enabled:

  1. Press Ctrl + Shift + Esc to open Task Manager
  2. Click the Performance tab
  3. Click CPU
  4. Look at the bottom right — find "Virtualisation"
  5. If it says Disabled — you need to enable it in BIOS

How to enable virtualisation in BIOS:

  1. Restart your laptop
  2. As it boots, press the BIOS key for your laptop brand (see table below)
  3. Navigate to Advanced → CPU Configuration (varies by manufacturer)
  4. Find Intel Virtualization Technology (Intel) or SVM Mode (AMD)
  5. Set it to Enabled
  6. Press F10 to save and exit
Laptop Brand BIOS Key Virtualisation Setting Name
Dell F2 Virtualisation Technology
HP F10 or Esc Virtualisation Technology (VTx)
Lenovo F1 or F2 Intel Virtualization Technology
Asus F2 or Del SVM Mode (AMD) or VT-x (Intel)
Acer F2 or Del Virtualization Technology
MSI Del SVM Mode
Samsung F2 Virtualisation

Step 2 — Enable Required Windows Features

Docker with WSL 2 requires three Windows features to be enabled. Missing any one of them causes Docker to fail silently.

  1. Press Win + R → type optionalfeatures → press Enter
  2. In the Windows Features dialog, make sure these are checked:
    • ✅ Hyper-V (all sub-items)
    • ✅ Virtual Machine Platform
    • ✅ Windows Subsystem for Linux
  3. Click OK and let Windows install them
  4. Restart your laptop when prompted
💡 Tip
If you can't see Hyper-V in the list, your Windows edition may not support it. Hyper-V requires Windows 11 Pro, Education, or Enterprise. Windows 11 Home doesn't have Hyper-V — but Docker Desktop still works on Home using WSL 2 without Hyper-V.

Step 3 — Update WSL 2 to the Latest Version

An outdated WSL 2 installation is one of the top causes of Docker startup failures in 2025–2026.

  1. Open Command Prompt as Administrator (search CMD → right-click → Run as administrator)
  2. Run: wsl --update
  3. Wait for the update to complete
  4. Then run: wsl --set-default-version 2
  5. Restart your laptop
  6. Try starting Docker again

If WSL is not installed at all, install it fresh:

  1. Open PowerShell as Administrator
  2. Run: wsl --install
  3. This installs WSL 2 with Ubuntu by default
  4. Restart when prompted

Step 4 — Set WSL 2 as Default Version

Even if WSL is installed, it might be running version 1 instead of version 2. Docker requires WSL 2.

  1. Open PowerShell as Administrator
  2. Run: wsl --list --verbose to see your current WSL distributions and versions
  3. If any show VERSION 1, convert them:
    wsl --set-version <distro-name> 2
    (e.g. wsl --set-version Ubuntu 2)
  4. Set default for future installations: wsl --set-default-version 2

Step 5 — Reinstall Docker Desktop Cleanly

A corrupted Docker Desktop installation is harder to diagnose but easy to fix with a clean reinstall.

  1. Open Settings → Apps → Installed apps
  2. Find Docker Desktop → click Uninstall
  3. After uninstall, manually delete these folders (they may remain):
    • C:UsersYourNameAppDataLocalDocker
    • C:UsersYourNameAppDataRoamingDocker
    • C:ProgramDataDocker
    • C:ProgramDataDockerDesktop
  4. Restart your laptop
  5. Download the latest Docker Desktop from docker.com/products/docker-desktop
  6. Install fresh and try starting

Step 6 — Check Docker Desktop Settings After Install

After a fresh install, verify Docker is configured to use WSL 2:

  1. Open Docker Desktop
  2. Click the gear icon (Settings) in the top right
  3. Go to General
  4. Make sure "Use the WSL 2 based engine" is checked
  5. Go to Resources → WSL Integration
  6. Enable integration with your installed Linux distro (e.g. Ubuntu)
  7. Click Apply & Restart

Step 7 — Fix the WSL 2 Kernel Update Error

If Docker shows an error like "WSL 2 installation is incomplete" or "Please install the WSL 2 kernel update package":

  1. Download the WSL 2 Linux kernel update package directly from Microsoft:
    Visit: aka.ms/wsl2kernel in your browser
  2. Run the downloaded installer
  3. Open PowerShell as Admin and run: wsl --set-default-version 2
  4. Restart Docker Desktop

Step 8 — Disable Conflicting Virtualisation Software

If you have VMware Workstation, VirtualBox, or any other virtualisation software installed, it can conflict with Hyper-V and WSL 2.

  • VMware: Update to VMware Workstation 16+ which supports Hyper-V coexistence
  • VirtualBox: Update to VirtualBox 6.1+ for Hyper-V compatibility — or disable Hyper-V when using VirtualBox
  • To disable Hyper-V temporarily: open CMD as Admin → run bcdedit /set hypervisorlaunchtype off → restart (run bcdedit /set hypervisorlaunchtype auto to re-enable)

Step 9 — Check Windows Defender / Antivirus

Some antivirus programs block Docker's network bridge components, preventing startup.

  1. Temporarily disable your antivirus
  2. Try starting Docker
  3. If it starts — add Docker Desktop to your antivirus exclusion list:
    • C:Program FilesDocker
    • C:UsersYourNameAppDataLocalDocker
    • \.pipedocker_engine
  4. Re-enable antivirus after adding exclusions

Step 10 — Reset WSL Completely (Last Resort)

If nothing else works, a full WSL reset clears all corrupted state:

  1. Open PowerShell as Administrator
  2. Run: wsl --shutdown
  3. Run: wsl --unregister Ubuntu (replace Ubuntu with your distro name)
  4. Run: wsl --install -d Ubuntu to reinstall fresh
  5. Restart Docker Desktop
⚠️ Warning
Unregistering a WSL distro deletes all files inside it. Back up any important data from inside your WSL environment before running wsl --unregister.

Quick Diagnosis Summary

Error Message Most Likely Cause Fix
Docker Desktop starting… (forever) Virtualisation disabled in BIOS Step 1
WSL 2 installation is incomplete WSL kernel not updated Step 7
Hardware assisted virtualization not enabled BIOS virtualisation off Step 1
An unexpected error occurred Corrupted Docker install Step 5
WSL distro not found WSL not properly installed Step 3
Docker Engine stopped Antivirus blocking Step 9
Error: context deadline exceeded WSL 2 crash or conflict Step 8

Still Not Working?

If you've tried every step above and Docker still won't start, the issue may be deeper — a Windows system file corruption, conflicting driver, or hardware limitation specific to your laptop model.

Our certified technician can connect to your laptop remotely, diagnose the exact cause, and fix it in under 30 minutes — without you needing to bring your laptop anywhere. Just ₹500 flat, no fix means full refund.

Get Remote Support — ₹500 →