Docker Desktop on Windows stays on starting or shows a WSL error
Docker Desktop - Unexpected WSL errorShort answer
On Windows, a failed start is nearly always virtualization. Check that it is on in the BIOS, that Virtual Machine Platform and WSL are enabled, and that the hypervisor launches at boot. Then check antivirus conflicts, and that your user is in the docker-users group.
Fix it fast
1Find out which cause you have
From PowerShell, confirm that WSL 2 itself works and that a hypervisor is detected. If the first line fails, Docker Desktop cannot start either.
wsl -d docker-desktop echo WSL 2 is working systeminfo | findstr /i hypervisor2Match what you see, then jump to its fix
- 1
HCS_E_HYPERV_NOT_INSTALLED or ERROR_NOT_SUPPORTED in the errorVirtualization, WSL 2 or Hyper-V is offFix - 2
Wsl/Service/RegisterDistro/CreateVm/HCS/ERROR_NOT_SUPPORTED, often right after a Windows updateAntivirus software conflicts with Hyper-VFix - 3
Docker Desktop - Access Denied dialog at startupYour user is not in the docker-users groupFix
- 1
What does the error look like?
Docker Desktop - Unexpected WSL errorHCS_E_HYPERV_NOT_INSTALLEDWsl/Service/RegisterDistro/CreateVm/HCS/ERROR_NOT_SUPPORTEDDocker Desktop - Access Denied
Cause 1 of 3
Virtualization, WSL 2 or Hyper-V is off
1Check
Causes are virtualization off in the BIOS, missing Windows features, or software that disabled Hyper-V. A hypervisor message in systeminfo means virtualization is on.
bcdedit /enum | findstr -i hypervisorlaunchtype2Fix
Turn on virtualization in the BIOS and enable Virtual Machine Platform and Windows Subsystem for Linux. If the hypervisor does not launch at boot, set it to auto from an administrative prompt and restart.
bcdedit /set hypervisorlaunchtype auto3Verify
After the restart, the WSL test line works.
wsl -d docker-desktop echo WSL 2 is workingConfirmed by docs.docker.com
Cause 2 of 3
Antivirus software conflicts with Hyper-V
1Check
Some antivirus products clash with Hyper-V. In Avast the culprit is hardware-assisted virtualization.
systeminfo | findstr /i hypervisor2Fix
Temporarily uninstall the antivirus software or add Docker to its exclusions. For Avast, clear Enable hardware-assisted virtualization under Menu, Settings, Troubleshooting.
# Avast: Menu > Settings > Troubleshooting > Enable hardware-assisted virtualization (clear)3Verify
Restart Docker Desktop.
wsl -d docker-desktop echo WSL 2 is workingConfirmed by docs.docker.com
Cause 3 of 3
Your user is not in the docker-users group
1Check
Open Computer Management as administrator and look at Local Users and Groups > Groups > docker-users.
# Computer Management > Local Users and Groups > Groups > docker-users2Fix
Add your account to the docker-users group, then sign out and back in.
# Add your user to docker-users, then sign out and back in3Verify
After signing in again, start Docker Desktop.
wsl -d docker-desktop echo WSL 2 is workingConfirmed by docs.docker.com
How do I stop it coming back?
- Restart Windows after enabling Hyper-V or WSL features.
- Check Docker's antivirus notes before a large Windows update.
- Run Docker Desktop in a VM only with nested virtualization on.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
Related fixes
Servers
Ubuntu on WSL will not start and shows error 0x800701bc
Error: 0x800701bc WSL 2 requires an update to its kernel component.
Error 0x800701bc is the code for the message that WSL 2 needs an update to its kernel component.
3 causes, each with a fixServers
apk cannot find py-pip in an Alpine Docker image
py-pip (no such package):
On current Alpine releases there is no package called py-pip.
2 causes, each with a fixServers
ng serve runs in the container but localhost:4200 does not open
The browser cannot open localhost:4200 although ng serve is running in the container
ng serve listens on localhost by default, which inside a container is the container itself.
3 causes, each with a fixServers
Angular routes return 404 from nginx when you refresh or open a link
The home page loads, but refreshing /some/route shows an nginx 404
Angular routes like /users/42 are not files, so nginx looks for them on disk and returns 404.
3 causes, each with a fixServers
AH00558: Apache in Docker cannot reliably determine its fully qualified domain name
Set the 'ServerName' directive globally to suppress this message
AH00558 is a warning, not a crash.
2 causes, each with a fixServers
Apache in a Docker container logs AH01114 when it proxies to a backend
AH01114: HTTP: failed to make connection to backend: api
Apache's proxy worker could not open a connection to the address in ProxyPass.
5 causes, each with a fix