Fix Docker Engine Stopped Error on Windows 11: 6-Step Troubleshooting Guide
A step-by-step guide to resolve the Docker Engine stopped error on Windows 11 by enabling CPU virtualization, starting Docker Desktop Service, updating WSL, switching the Docker daemon, and launching Docker Desktop as administrator.
After installing Docker Desktop on Windows 11, the UI may continuously show "Docker Engine stopped." This article summarizes a six-step troubleshooting process adapted from a Zhihu post (https://zhuanlan.zhihu.com/p/663821762). All commands should be run with administrator privileges (Command Prompt, PowerShell, or Docker Desktop).
1. Verify Built-in Virtual Machine (Hyper-V)
Windows 11 typically includes Hyper-V. If missing, refer to the source link for installation instructions.
2. Enable CPU Virtualization in BIOS
Open Task Manager → Performance tab → CPU. Check the "Virtualization" field. If disabled, enter BIOS/UEFI to enable it. The author uses an ASUS motherboard with AMD CPU; the BIOS entry key is F2. ASUS provides a guide at https://rog.asus.com.cn/support/faq/1045141/. After enabling, reboot and confirm via Control Panel → Turn Windows features on or off that Hyper-V and Windows Hypervisor Platform are checked. A reboot is required for changes to take effect.
3. Start Docker Desktop Service
In an elevated Command Prompt or PowerShell, run: net start com.docker.service This starts the Docker Desktop Service. A screenshot shows the command succeeding.
4. Install or Update WSL
In PowerShell (admin), run: wsl --update This installs WSL if absent or updates to the latest version. The command may time out; retry a few times.
5. Switch Docker Daemon
Navigate to the Docker Desktop installation directory and invoke the CLI switch:
cd "C:\Program Files\Docker\Docker" .\DockerCli.exe -SwitchDaemonThe command may return an error such as "cannot find"; the author notes this is acceptable and does not prevent the fix.
6. Launch Docker Desktop as Administrator
Right-click the Docker Desktop shortcut and select "Run as administrator." The Docker Engine should now start successfully.
The author mentions that the original Zhihu post also described a persistent "Starting the Docker Engine" message, which they did not encounter.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Java Captain
Focused on Java technologies: SSM, the Spring ecosystem, microservices, MySQL, MyCat, clustering, distributed systems, middleware, Linux, networking, multithreading; occasionally covers DevOps tools like Jenkins, Nexus, Docker, ELK; shares practical tech insights and is dedicated to full‑stack Java development.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
