Windows 10下Docker Desktop启动失败：Hyper-V与DEP相关问题求助

It sounds like you're dealing with a frustrating Docker Desktop issue that started right after enabling WSL 2 on your Windows preview device—especially since your other preview machine works fine, and everything ran smoothly before the update. Let's break down your situation and walk through targeted fixes to get your development workflow back on track.

What You've Already Tried (For Context) #

• Enabled Hyper-V and Data Execution Protection (DEP) (verified in BIOS and Windows Service Control Manager)
• Checked required Windows features in Programs and Features
• Reinstalled Docker Desktop and restarted your system multiple times
• Submitted an issue for the problem

Error Log from Failed Startup #

----------------------------------------
System.Runtime.InteropServices.WindowsRuntime Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.InteropServices.WindowsRuntime/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Runtime.InteropServices.WindowsRuntime.dll
----------------------------------------
Windows.Data Assembly Version: 255.255.255.255 Win32 Version: 10.0.10011.16384 CodeBase: file:///C:/WINDOWS/system32/WinMetadata/Windows.Data.winmd
----------------------------------------
System.ValueTuple Assembly Version: 4.0.3.0 Win32 Version: 4.6.26515.06 CodeBase: file:///C:/Program%20Files/Docker/Docker/System.ValueTuple.DLL
----------------------------------------
System.Collections Assembly Version: 4.0.11.0 Win32 Version: 4.6.25714.01 CodeBase: file:///C:/Program%20Files/Docker/Docker/System.Collections.DLL
----------------------------------------
Docker.Win32Helpers Assembly Version: 1.0.7257.10303 Win32 Version: CodeBase: file:///C:/Program%20Files/Docker/Docker/Docker.Win32Helpers.DLL
----------------------------------------
System.Net.Http Assembly Version: 4.2.0.0 Win32 Version: 4.6.26011.01 CodeBase: file:///C:/Program%20Files/Docker/Docker/System.Net.Http.DLL
----------------------------------------
System.Management.Automation Assembly Version: 3.0.0.0 Win32 Version: 10.0.19041.1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Management.Automation/v4.0_3.0.0.0__31bf3856ad364e35/System.Management.Automation.dll
----------------------------------------
PresentationFramework.Aero2 Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework.Aero2/v4.0_4.0.0.0__31bf3856ad364e35/PresentationFramework.Aero2.dll
----------------------------------------
System.Resources.ResourceManager Assembly Version: 4.0.1.0 Win32 Version: 4.6.25714.01 CodeBase: file:///C:/Program%20Files/Docker/Docker/System.Resources.ResourceManager.DLL
----------------------------------------
WindowsFormsIntegration Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/WindowsFormsIntegration/v4.0_4.0.0.0__31bf3856ad364e35/WindowsFormsIntegration.dll
----------------------------------------
System.Web.Http Assembly Version: 5.2.7.0 Win32 Version: 5.2.61128.0 CodeBase: file:///C:/Program%20Files/Docker/Docker/System.Web.Http.DLL
----------------------------------------
Docker.HttpApi Assembly Version: 2.1.0.40693 Win32 Version: 2.1.0.40693 CodeBase: file:///C:/Program%20Files/Docker/Docker/Docker.HttpApi.DLL
----------------------------------------
Microsoft.Owin Assembly Version: 4.0.1.0 Win32 Version: 4.0.80118.116 CodeBase: file:///C:/Program%20Files/Docker/Docker/Microsoft.Owin.DLL
----------------------------------------
Owin Assembly Version: 1.0.0.0 Win32 Version: 1.0 CodeBase: file:///C:/Program%20Files/Docker/Docker/Owin.DLL
----------------------------------------
HttpOverStream.NamedPipe Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Program%20Files/Docker/Docker/HttpOverStream.NamedPipe.DLL
----------------------------------------
HttpOverStream Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Program%20Files/Docker/Docker/HttpOverStream.DLL
----------------------------------------
HttpOverStream.Server.Owin Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Program%20Files/Docker/Docker/HttpOverStream.Server.Owin.DLL
----------------------------------------
Microsoft.Owin.Hosting Assembly Version: 4.0.1.0 Win32 Version: 4.0.80118.116 CodeBase: file:///C:/Program%20Files/Docker/Docker/Microsoft.Owin.Hosting.DLL
----------------------------------------
Anonymously Hosted DynamicMethods Assembly Assembly Version: 0.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/mscorlib/v4.0_4.0.0.0__b77a5c561934e089/mscorlib.dll
----------------------------------------
System.Web.Http.Owin Assembly Version: 5.2.7.0 Win32 Version: 5.2.61128.0 CodeBase: file:///C:/Program%20Files/Docker/Docker/System.Web.Http.Owin.DLL
----------------------------------------
System.Net.Http.Formatting Assembly Version: 5.2.7.0 Win32 Version: 5.2.61128.0 CodeBase: file:///C:/Program%20Files/Docker/Docker/System.Net.Http.Formatting.DLL
----------------------------------------
SMDiagnostics Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/SMDiagnostics/v4.0_4.0.0.0__b77a5c561934e089/SMDiagnostics.dll
----------------------------------------
System.Threading.Tasks.Extensions Assembly Version: 4.2.0.0 Win32 Version: 4.6.26606.05 CodeBase: file:///C:/Program%20Files/Docker/Docker/System.Threading.Tasks.Extensions.DLL
----------------------------------------
HttpOverStream.Client Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Program%20Files/Docker/Docker/HttpOverStream.Client.DLL
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging enabled.
For example:
<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.

Actionable Fixes to Resolve the Issue #

Since the problem began right after enabling WSL 2, the root cause is likely a misconfigured WSL 2 setup, a conflict between WSL 2 and Hyper-V, or corrupted Docker/WSL data. Here are step-by-step solutions to try:

1. Reset Docker's WSL 2 Distributions
   WSL 2 stores Docker's data in dedicated distributions, which can get corrupted after updates. Resetting them often fixes startup issues:

   • Open an elevated PowerShell or Command Prompt
   • Run these commands to shut down WSL and unregister Docker's WSL instances:

     wsl --shutdown
     wsl --unregister docker-desktop
     wsl --unregister docker-desktop-data
     

   • Restart Docker Desktop—it will recreate the WSL distributions from scratch.

2. Switch Docker Back to Hyper-V Backend
   If you don't need WSL 2 immediately, reverting to the Hyper-V backend might get Docker working again quickly:

   • Open Docker Desktop's settings
   • Navigate to Resources > WSL Integration
   • Uncheck the box for "Enable the WSL 2 based engine"
   • Click "Apply & Restart" to save changes.

3. Repair Your WSL Installation
   Windows updates can sometimes break WSL components. Repairing WSL might fix underlying issues:

   • Go to Settings > Apps > Apps & features
   • Locate "Windows Subsystem for Linux" in the list
   • Click it, select Advanced options, then hit Repair
   • Once the repair finishes, restart your system and test Docker again.

4. Clean Reinstall Docker Desktop (With Leftover Removal)
   A standard reinstall might leave corrupted files behind. Try a full clean install:

   • Uninstall Docker Desktop via Programs and Features
   • Delete these leftover folders (replace <YourUsername> with your actual username):
     • C:\Program Files\Docker
     • C:\Users\<YourUsername>\AppData\Roaming\Docker
     • C:\Users\<YourUsername>\AppData\Local\Docker
   • Restart your PC
   • Download the latest stable Docker Desktop installer and run it, choosing your preferred backend during setup.

5. Double-Check BIOS Virtualization Settings
   Occasionally, Windows updates can reset BIOS settings related to virtualization:

   • Reboot your PC and enter BIOS/UEFI (usually by pressing F2, Del, or Esc during boot)
   • Ensure options like Intel VT-x, AMD-V, Virtualization Technology, and Nested Virtualization are enabled
   • Save changes and boot back into Windows.

6. Check for Hyper-V and VirtualBox Conflicts
   Even though they worked together before, enabling WSL 2 might have altered Hyper-V's state. If you still use VirtualBox:

   • Open VirtualBox, go to File > Preferences > System
   • Confirm "Enable Nested VT-x/AMD-V" is checked (if your CPU supports it)
   • Note: If you switch back to WSL 2, you might need to disable VirtualBox temporarily—some systems can't run both Hyper-V and VirtualBox's native hypervisor at the same time.

Next Steps If Fixes Don't Work #

If none of these solutions resolve the issue, keep an eye on the issue you submitted—Docker's team is proactive about addressing preview build bugs. You can also check the Windows Event Viewer for more detailed logs (look under Applications and Services Logs > Docker) to get a clearer picture of what's failing.

内容的提问来源于stack exchange，提问作者R. Barrett