ErrorVaultHQ

Solved Error

How to Fix: Docker Desktop 'WSL 2 installation is incomplete'

Quick Fix

Update the WSL 2 kernel, then restart: 1. Close Docker Desktop. 2. Open PowerShell as Administrator (right-click Start, choose Windows Terminal (Admin) or Windows PowerShell (Admin)). 3. Run wsl --update and let it finish. 4. Run wsl --shutdown, then restart your PC. 5. Open Docker Desktop again — the error should be gone.

What this error means

Docker Desktop on Windows uses the WSL 2 (Windows Subsystem for Linux 2) backend by default. This message means Windows has the WSL feature turned on, but the Linux kernel component that WSL 2 needs is missing, outdated, or was never installed. The Linux kernel component is missing or outdated, and the fix is to run wsl --update in an elevated PowerShell, then restart Docker Desktop. This is the single most common cause, but a few other things (Windows version too old, WSL feature not enabled, virtualization off in BIOS) can trigger the same message.

Step-by-Step Guide

Fix 1: Update the WSL 2 kernel with wsl --update

  1. 1Close Docker Desktop completely (right-click its tray icon and choose Quit, if needed).
  2. 2Open an elevated PowerShell or Command Prompt. Press the Windows key, type cmd or PowerShell, then choose Run as administrator. Press the Windows logo key, type cmd, select Run as administrator to open a new terminal window.
  3. 3Run the update command: type wsl --update and press Enter. This pulls the latest WSL 2 Linux kernel package directly from Microsoft.
  4. 4Shut down WSL cleanly. Run wsl --shutdown so the update takes effect.
  5. 5Restart your computer. Kernel updates only fully apply after a reboot.
  6. 6Relaunch Docker Desktop and confirm startup. Relaunch Docker Desktop and confirm the whale icon starts without the error.

Fix 2: Manually install the WSL 2 kernel update package

  1. 1Install the WSL 2 kernel update package manually. If wsl --update fails, is unavailable, or you are on an older Windows build, install the kernel package by hand. Open the error dialog's link in Docker Desktop, or go directly to aka.ms/wsl2kernel in your browser. The WSL 2 Linux kernel is now installed using a separate MSI update package; click the link and follow the instructions to install the kernel update, then press Restart after installing the Linux kernel.
  2. 2Download the correct package for your CPU architecture (x64 for most PCs, ARM64 for Windows-on-ARM devices).
  3. 3Run the downloaded .msi file and approve permissions. Run the downloaded .msi file and approve the elevated-permissions prompt.
  4. 4Restart your PC and reopen Docker Desktop. Restart your PC, then open Docker Desktop again.

Fix 3: Make sure WSL 2 and its Windows features are actually enabled

  1. 1Open PowerShell as Administrator and run wsl --install. If updating the kernel does not resolve it, WSL itself may not be properly enabled. On a fresh system this installs the Virtual Machine Platform, the WSL feature, and a default Linux distro in one step.
  2. 2Check required Windows features are on. Open Control Panel > Programs > Turn Windows features on or off and confirm both Windows Subsystem for Linux and Virtual Machine Platform are checked. You can also enable them via command line with dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart and the equivalent command for VirtualMachinePlatform.
  3. 3Set WSL 2 as the default version by running wsl --set-default-version 2.
  4. 4Restart and reopen Docker Desktop.

Fix 4: Check your Windows version meets the minimum requirement

  1. 1Confirm your Windows build. Press Win + R, type winver, and press Enter. Windows 10 Home version 2004 / build 19041 or later supports Docker Desktop through the WSL2 backend.
  2. 2Run Windows Update to meet minimum requirements. Run Windows Update (Settings > Windows Update) if your build is older than this, since older builds lack the WSL 2 kernel features Docker needs.
  3. 3Reboot and retry the WSL update steps above once Windows is current.

Fix 5: Rule out BIOS virtualization and hypervisor conflicts

  1. 1Enable virtualization in BIOS/UEFI. If the kernel is up to date and the error persists, or WSL fails to actually boot, check hardware virtualization. Restart, enter BIOS/UEFI (commonly Del or F2 at boot), and enable Intel VT-x or AMD-V.
  2. 2Verify virtualization is enabled in Task Manager. Verify it is active in Windows via Task Manager > Performance > CPU, where 'Virtualization' should say Enabled.
  3. 3Close conflicting VM software such as older versions of VirtualBox or VMware Workstation that predate Windows Hypervisor Platform support, as these can prevent WSL 2's VM from starting.

When to get more specific help

Platform note: all of the above is Windows-specific; this error does not occur on macOS or Linux versions of Docker Desktop. Still stuck after a kernel update, feature check, and BIOS check? Run wsl --status to see your current kernel and WSL version, then reset Docker Desktop via Settings > Troubleshoot > Reset to factory defaults, or uninstall and reinstall Docker Desktop. Corporate/locked-down machines: if Microsoft Store access or outbound downloads are blocked by IT policy, your organization may need to push the WSL kernel update through its normal software deployment pipeline rather than via Store or aka.ms links — ask your IT/helpdesk team. Persistent low-level failures (WSL distro terminates abruptly, virtual disk errors, or the CPU lacks SLAT support) point to a hardware or Windows installation problem beyond Docker itself — in that case, search Docker's GitHub issue tracker (docker/for-win) or Microsoft's WSL GitHub repo for your exact error text, or open a new issue with your diagnostics ID.

Sources:

Heads up: this guide was drafted with AI assistance from the real sources listed below, and structured by our team for clarity. It may not cover every possible cause — if it doesn't fix your issue, let us know and we'll take a closer look. See how we create our fixes.

Was this fix helpful?

Related Error Fixes