How to fix Docker Desktop is starting... in Docker

DockerINTERMEDIATEMEDIUMUpdated Dec 1, 2025ยท 532 views

This issue occurs when Docker Desktop gets stuck on the 'Starting...' screen and never fully initializes. It commonly affects Windows and Mac users after system updates, sleep/wake cycles, or when WSL/Hyper-V components become misconfigured.

Quick fix

Fixes Docker Desktop is starting...

wsl --shutdown
  1. Force quit and restart Docker Desktop
  2. Restart WSL (Windows only)
  3. Restart the LxssManager service (Windows only)
  4. Perform a full shutdown (not restart)
docker โ€” error
wsl --shutdown
Docker Desktop is starting...

What this error means

When you launch Docker Desktop, it needs to initialize several components: the Docker daemon, networking, and on Windows, the WSL 2 backend or Hyper-V virtual machine. The 'Docker Desktop is starting...' message appears while these components are being set up. When Docker gets stuck at this stage, it means one of these initialization steps has failed or is taking too long. On Windows, this is often related to WSL 2 issues, the LxssManager service, or conflicts with antivirus software. On Mac, it may be caused by HyperKit conflicts, corrupted VM state, or resource constraints. The Docker daemon logs (dockerd.log) usually contain details about what specifically failed.

Typical symptoms

  • Docker Desktop shows 'Docker Desktop is starting...' indefinitely
  • The whale icon in the system tray keeps animating but never turns green
  • Docker commands in terminal return 'Cannot connect to the Docker daemon'
  • The Docker Desktop window appears frozen or unresponsive
  • CPU usage may spike during the stuck startup
  • Docker worked fine before a system restart or update
  • Docker Desktop cannot be quit normally and requires force-close

Common causes

  1. WSL distributions (docker-desktop, docker-desktop-data) are corrupted (Windows)
  2. LxssManager service is not running or malfunctioning (Windows)
  3. Hyper-V or Virtual Machine Platform features are disabled (Windows)
  4. TiWorker.exe (Trusted Installer Worker) is blocking startup (Windows 11)
  5. Antivirus software is interfering with Docker initialization
  6. Docker VM state is corrupted after improper shutdown
  7. System woke from sleep while Docker was running
  8. Insufficient system resources (RAM, disk space)
  9. Docker settings file (settings.json) is corrupted
  10. Conflicting virtualization software (VirtualBox, VMware, HAXM)
  11. IPv6 configuration issues in WSL 2 mode
  12. Outdated Docker Desktop version with known startup bugs

How to fix "Docker Desktop is starting..."

1Force quit and restart Docker Desktop

Start with the simplest fix. On Windows, open Task Manager and end all Docker processes (Docker Desktop, Docker Desktop Service, docker.exe). On Mac, use Force Quit (Cmd+Option+Esc) or Activity Monitor.

Then restart Docker Desktop. If it's still stuck after 2-3 minutes, proceed to the next step.

2Restart WSL (Windows only)

Open PowerShell or Command Prompt as Administrator and run:

powershell
wsl --shutdown

Wait 10 seconds, then start Docker Desktop again. This terminates all WSL instances and forces a clean restart of the Linux subsystem.

3Restart the LxssManager service (Windows only)

The LxssManager service manages WSL distributions. Open Services (services.msc), find 'LxssManager', and restart it. Alternatively, run in PowerShell as Administrator:

powershell
Restart-Service LxssManager

If the service fails to start, try stopping it first, waiting 10 seconds, then starting it.

4Perform a full shutdown (not restart)

On Windows, a full shutdown clears more cached state than a restart. Hold Shift while clicking Shut Down, or run:

powershell
shutdown /s /t 0

After booting up, Docker Desktop often starts successfully. This is particularly effective for issues that appear after waking from sleep.

5Check for TiWorker.exe conflict (Windows 11)

The Trusted Installer Worker can block Docker startup. Open Task Manager, go to the Details tab, and look for TiWorker.exe.

If it's running with high CPU usage:
1. Right-click TiWorker.exe and select End task
2. Open Services (services.msc) and restart 'Windows Modules Installer'
3. Try starting Docker Desktop again

6Temporarily disable antivirus

Some antivirus programs interfere with Docker's virtualization. Temporarily disable your antivirus (Windows Defender, Norton, McAfee, etc.) and try starting Docker.

If Docker starts successfully, add Docker to your antivirus exclusions:
- C:\Program Files\Docker\Docker
- C:\ProgramData\Docker
- %LOCALAPPDATA%\Docker

7Unregister and recreate WSL distributions (Windows)

If the Docker WSL distributions are corrupted, remove them so Docker can recreate them:

powershell
wsl --unregister docker-desktop
wsl --unregister docker-desktop-data

Warning: This will delete all Docker containers, images, and volumes. Back up important data first using docker save and docker export.

After unregistering, restart Docker Desktop. It will recreate the distributions automatically.

8Delete Docker Desktop data (Mac)

On Mac, remove Docker's VM state and data:

bash
rm -rf ~/Library/Group\ Containers/group.com.docker
rm -rf ~/Library/Containers/com.docker.docker
rm -rf ~/.docker

Warning: This deletes all containers, images, and volumes. Restart Docker Desktop afterward to recreate a fresh environment.

9Reset Docker Desktop to factory defaults

If Docker Desktop can briefly open its UI before getting stuck, try resetting to defaults:

1. Open Docker Desktop settings (gear icon)
2. Click the Troubleshoot icon (bug icon)
3. Select 'Reset to factory defaults'

If you can't access the UI, delete the settings file manually:
- Windows: %AppData%\Docker\settings.json
- Mac: ~/Library/Group Containers/group.com.docker/settings.json

10Switch Docker daemon mode (Windows)

Try switching between Windows containers and Linux containers to reset Docker's state:

cmd
"C:\Program Files\Docker\Docker\DockerCli.exe" -SwitchDaemon

Run this twice to switch away and back to your original mode.

11Verify Windows features are enabled

Docker Desktop requires specific Windows features. Run in PowerShell as Administrator:

powershell
Get-WindowsOptionalFeature -Online | Where-Object {$_.FeatureName -match 'Hyper|Virtual|WSL'}

Ensure these are enabled:
- Microsoft-Windows-Subsystem-Linux
- VirtualMachinePlatform
- HypervisorPlatform (optional but recommended)

Enable any missing features:

powershell
dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart

Restart your computer after enabling features.

12Run Docker Desktop diagnostics

Generate a diagnostic report to identify the issue:

Windows (PowerShell as Admin):

powershell
& "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" gather -upload

Mac (Terminal):

bash
/Applications/Docker.app/Contents/MacOS/com.docker.diagnose gather -upload

This creates a diagnostics ID you can share with Docker support. Review the output for error messages.

13Reinstall Docker Desktop

As a last resort, completely remove and reinstall Docker Desktop:

Windows:
1. Uninstall from Settings > Apps
2. Run wsl --unregister docker-desktop and wsl --unregister docker-desktop-data
3. Delete C:\ProgramData\Docker and %LOCALAPPDATA%\Docker
4. Restart your computer
5. Download latest Docker Desktop from https://www.docker.com/products/docker-desktop
6. Install with default settings

Mac:
1. Drag Docker to Trash
2. Delete Docker data folders (see step 8)
3. Restart your Mac
4. Download and install fresh copy

Advanced notes

Checking Docker logs: The Docker daemon logs can reveal why startup is failing. On Windows, check %LOCALAPPDATA%\Docker\log\vm\dockerd.log. On Mac, check ~/Library/Containers/com.docker.docker/Data/log/vm/dockerd.log.

WSL memory limits: If Docker is slow to start due to memory pressure, create or edit %UserProfile%\.wslconfig:

ini
[wsl2]
memory=4GB
processors=2

Pause instead of quit: If Docker gets stuck after wake from sleep, use the Pause feature (right-click system tray > Pause) before putting your computer to sleep to prevent state corruption.

Docker in CI/CD: If running Docker Desktop in CI environments (not recommended), consider using Docker Engine directly on Linux or Docker-in-Docker containers instead.

Version-specific bugs: Docker has fixed several startup-related bugs in recent versions. Check Docker Desktop release notes for known issues affecting your version. Version 4.26+ addressed several slow/frozen startup issues.

Frequently asked questions

What does "Docker Desktop is starting..." mean?
When you launch Docker Desktop, it needs to initialize several components: the Docker daemon, networking, and on Windows, the WSL 2 backend or Hyper-V virtual machine. ' message appears while these components are being set up. When Docker gets stuck at this stage, it means one of these initialization steps has failed or is taking too long.
How do I fix "Docker Desktop is starting..."?
This issue occurs when Docker Desktop gets stuck on the 'Starting...' screen and never fully initializes. It commonly affects Windows and Mac users after system updates, sleep/wake cycles, or when WSL/Hyper-V components become misconfigured.
What causes "Docker Desktop is starting..."?
WSL distributions (docker-desktop, docker-desktop-data) are corrupted (Windows) LxssManager service is not running or malfunctioning (Windows) Hyper-V or Virtual Machine Platform features are disabled (Windows)
Is the "Docker Desktop is starting..." error serious?
It is a medium-severity error โ€” more of a blocker than a risk. The steps above resolve it.

Official resources & further reading