Opening Docker Desktop BSOD with Hypervisor_Error

hi all,
I have a machine that all enable HyperV as

check result:

Starting diagnostics

[2024-11-07T13:40:28.571022800Z][com.docker.diagnose.exe.ipc] fab30c9a-diagnose -> \\.\pipe\dockerBackendApiServer BackendAPI
[2024-11-07T13:40:28.573137000Z][com.docker.diagnose.exe.ipc] (8f00b371) fab30c9a-diagnose C->S BackendAPI POST /idle/make-busy
[2024-11-07T13:40:28.573137000Z][com.docker.diagnose.exe.ipc][W] (8f00b371) fab30c9a-diagnose C<-S ConnectionClosed POST /idle/make-busy (0s): Post "http://ipc/idle/make-busy": open \\.\pipe\dockerBackendApiServer: The system cannot find the file specified.
[2024-11-07T13:40:29.579013400Z][com.docker.diagnose.exe.ipc] (8f00b371-2) fab30c9a-diagnose C->S BackendAPI GET /idle
[2024-11-07T13:40:29.585036000Z][com.docker.diagnose.exe.ipc][W] (8f00b371-2) fab30c9a-diagnose C<-S ConnectionClosed GET /idle (6.0226ms): Get "http://ipc/idle": open \\.\pipe\dockerBackendApiServer: The system cannot find the file specified.
[PASS] DD0027: is there available disk space on the host?
[SKIP] DD0028: is there available VM disk space?
[SKIP] DD0002: does the bootloader have virtualization enabled?
[SKIP] DD0018: does the host support virtualization?
[FAIL] DD0001: is the application running? Docker is not running
[SKIP] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[SKIP] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0024: is WSL installed?
[FAIL] DD0025: are WSL distros installed? WSL Distribution docker-desktop is missing
[PASS] DD0026: is the WSL LxssManager service running?
[FAIL] DD0029: is the WSL 2 Linux filesystem corrupt? prereq failed: are WSL distros installed?
[FAIL] DD0035: is the VM time synchronized? prereq failed: are WSL distros installed?
[FAIL] DD0017: can a VM be started? prereq failed: are WSL distros installed?
[FAIL] DD0016: is the LinuxKit VM running? prereq failed: is the application running?
[FAIL] DD0004: is the Docker engine running? prereq failed: is the LinuxKit VM running?
[PASS] DD0015: are the binary symlinks installed?
[FAIL] DD0031: does the Docker API work? prereq failed: is the Docker engine running?
[PASS] DD0013: is the $PATH ok?
[FAIL] DD0003: is the Docker CLI working? prereq failed: is the Docker engine running?
[FAIL] DD0005: is the user in the docker-users group? prereq failed: is the LinuxKit VM running?
[FAIL] DD0037: is the connection to Docker working? prereq failed: is the Docker engine running?
[FAIL] DD0014: are the backend processes running? prereq failed: is the LinuxKit VM running?
[FAIL] DD0007: is the backend responding? prereq failed: are the backend processes running?
[FAIL] DD0009: is the vpnkit API responding? prereq failed: are the backend processes running?
[FAIL] DD0010: is the Docker API proxy responding? prereq failed: are the backend processes running?
[SKIP] DD0006: is the Docker Desktop Service responding?
[FAIL] DD0030: is the image access management authorized? prereq failed: is the Docker engine running?
[PASS] DD0033: does the host have Internet access?
[PASS] DD0002: does the bootloader have virtualization enabled?
[PASS] DD0018: does the host support virtualization?
[WARN] DD0001: is the application running? Docker is not running
[PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[PASS] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0024: is WSL installed?
[WARN] DD0025: are WSL distros installed? WSL Distribution docker-desktop is missing
[PASS] DD0026: is the WSL LxssManager service running?
[WARN] DD0029: is the WSL 2 Linux filesystem corrupt? prereq failed: are WSL distros installed?
[WARN] DD0035: is the VM time synchronized? prereq failed: are WSL distros installed?
[WARN] DD0017: can a VM be started? prereq failed: are WSL distros installed?
[WARN] DD0016: is the LinuxKit VM running? prereq failed: is the application running?
[WARN] DD0004: is the Docker engine running? prereq failed: is the LinuxKit VM running?
[PASS] DD0015: are the binary symlinks installed?
[WARN] DD0031: does the Docker API work? prereq failed: is the Docker engine running?
[WARN] DD0032: do Docker networks overlap with host IPs? prereq failed: does the Docker API work?

Please note the following 11 warnings:

1 : The check: is the application running?
    Produced the following warning: Docker is not running

Is the Docker Desktop application running?

2 : The check: are WSL distros installed?
    Produced the following warning: WSL Distribution docker-desktop is missing

The Docker engine uses several WSL distributions. Therefore these must be installed.

3 : The check: are WSL distros installed?
    Produced the following warning: WSL Distribution docker-desktop is missing

The Docker engine uses several WSL distributions. Therefore these must be installed.

4 : The check: is the WSL 2 Linux filesystem corrupt?
    Produced the following warning: prereq failed: are WSL distros installed?

If the WSL 2 Linux filesystem is corrupt then Docker Desktop cannot start.
There is a known issue fixed in Windows Insider builds which can cause filesystem corruption, see:
https://github.com/microsoft/WSL/issues/5895 .

Try running "wsl --shutdown" to stop your WSL Virtual Machine. When it restarts it will
run a filesystem check and hopefully fix the problem.


5 : The check: are WSL distros installed?
    Produced the following warning: WSL Distribution docker-desktop is missing

The Docker engine uses several WSL distributions. Therefore these must be installed.

6 : The check: is the VM time synchronized?
    Produced the following warning: prereq failed: are WSL distros installed?

The VM time must be in sync with the host, otherwise Docker Desktop will not work correctly.

Ensure you are using a modern WSL 2 kernel (see "wsl --update"). If this problem persists,
try manually synchronizing the VM clock with "sudo hwclock -s".

7 : The check: can a VM be started?
    Produced the following warning: prereq failed: are WSL distros installed?

The Docker engine runs inside a Linux VM. Therefore we must be able to start Virtual Machines.

8 : The check: is the LinuxKit VM running?
    Produced the following warning: prereq failed: is the application running?

The Docker engine runs inside a Linux VM. Therefore the VM must be running.

9 : The check: is the Docker engine running?
    Produced the following warning: prereq failed: is the LinuxKit VM running?

The Docker engine manages all containers and images on the host. Check the dockerd.log to see why it failed to start.

10 : The check: does the Docker API work?
    Produced the following warning: prereq failed: is the Docker engine running?

If the Docker API is not available from the host then Docker Desktop will not work correctly.

11 : The check: do Docker networks overlap with host IPs?
    Produced the following warning: prereq failed: does the Docker API work?

If the subnet used by a Docker network overlaps with an IP used by the host, then containers
won't be able to contact the overlapping IP addresses.

Try configuring the IP address range used by networks: in your docker-compose.yml.
See https://docs.docker.com/compose/compose-file/compose-file-v2/#ipv4_address-ipv6_address


Please investigate the following 2 issues:

1 : The test: is the application running?
    Failed with: Docker is not running

Is the Docker Desktop application running?

2 : The test: are WSL distros installed?
    Failed with: WSL Distribution docker-desktop is missing

The Docker engine uses several WSL distributions. Therefore these must be installed.

But any time I try to open Docker Desktop I will get BSOD with Hypervisor Error.
I also tried

bcdedit /set hypervisorlaunchtype auto

and restart so many time but doesn’t work, also try to check or uncheck on using WSL2 but still.
Please help me on this, I’m totally stuck of this. I have few machine but only this one get this issue.
Thanks

What is your Windows version? Is it Desktop or Server? And What is the Docker Desktop version?

You can also try if you can install a WSL2 distribution from Microsoft Store

hi @rimelek
I’m using Windows 10 PRO on my desktop. Docker Desktop is the latest version.
My machine is a Dell Optiplex (NUC machine), I also try to

  • Open BIOS (F12 at start) and set virtualization - direct i/o to false
  • Windows Feature: mark “virtual Platform”
    But issue still the same.

Thank you

Without a version number, there is always a chance to talking about a different version when any of us thinks the latest is not the one that actually is the latest. And sharing the actual version number can also help other people when the latest is already a newer version. Please, share the exact version number as well.

I don’t see in your reply that you tried installing a WSL2 distribution from Microsoft Store. Can you try that too? If you choose WSL during the installation, WSL2 is a requirement. If you WSL2 virtual machines without Docker don’t work either, that is a different issue compared to whn only Docker Desktop fails to create its distribution.

It’s 4.35.1

I tried on Ubuntu and Debian as well but doesn’t work, thing gets more weird when I tried to install those distribution via “wsl --install” (default will be Ubuntu) it will get BSOD on starting Ubuntu windows and after restart when I tried to open Unbuntu it will show error on console"

WslRegisterDistribution failed with error: 0x80070050 Error: 0x80070050 The file exists.
The same with Debian.

I made Docker Desktop work by:

  • Installed version 4.21.1 (w/o check on WSL2)
    But it’s just temporarily solution by now because I can’t run some of my ubuntu base containter.

I have no idea by now, maybe it was an issue on some recently system changed:

  • I made only change by update Password of Admin account to make RDP working
  • I upgraded to Win 11 accidentally but revert to Win 10 right after that.
    Thank you

Looks like your WSL installation is not working properly. Have you tried to follow Microsoft’s WSL troubleshooting guide https://learn.microsoft.com/en-us/windows/wsl/troubleshooting?

First you need to bring your system to a state where registering and running distribution in WSL works. Once this work reliable, we can concentrate on the Docker Desktop aspects.