WSL: WslRegisterDistribution failed with error: 0x80370102

Version

Microsoft Windows [Version 10.0.22621.1265]

WSL Version

  • WSL 2
  • WSL 1

Kernel Version

2

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

In Windows Features:

  • Hyper-V is fully selected (all subchecks selected)
  • Virtual Machine Platform is fully selected
  • Windows Hypervisor Platform is fully selected
  • Windows Subsystem for Linux is fully selected

In task manager, virutalization is fully enabled in my BIOS, confirmed via systeminfo, too:


Hyper-V Requirements:      VM Monitor Mode Extensions: Yes
                           Virtualization Enabled In Firmware: Yes
                           Second Level Address Translation: Yes
                           Data Execution Prevention Available: Yes
PS C:\WINDOWS\system32> ubuntu
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80370102
Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS.
For information please visit https://aka.ms/enablevirtualization
Press any key to continue...
PS C:\WINDOWS\system32> bcdedit /set hypervisorlaunchtype auto start
The operation completed successfully.

All of the online documentation takes me in loops or tells me to roll back to WSL 1.

The BIOS says I have virtualization enabled, the task manager says it…

I’ve disabled and re-enabled all of these checkboxes and rebooted, and I still cannot get WSL2 working on my Windows 11 box

Expected Behavior

I would expect ubuntu to load

Actual Behavior

PS C:\WINDOWS\system32> ubuntu
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80370102
Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS.
For information please visit https://aka.ms/enablevirtualization
Press any key to continue...
PS C:\WINDOWS\system32>
image image

Diagnostic Logs

No response

About this issue

  • Original URL
  • State: open
  • Created 4 years ago
  • Reactions: 4
  • Comments: 15

Most upvoted comments

I also have the same issue. When this problem occurred, both my Windows Sandbox and WSL2 stopped working properly. Then I found an article about fixing the Sandbox and resolved the issue by following these steps:

Uninstall Windows Sandbox.

Restart your computer.

Open Command Prompt (Run as administrator) and execute the following command:

bcdedit /set hypervisorlaunchtype Auto

Uninstall Hyper-V.

Restart your computer.

Install Hyper-V.

Restart your computer and verify that Hyper-V is working.

Install Windows Sandbox.

Restart your computer and verify that Sandbox is functioning properly.

The link: https://answers.microsoft.com/zh-hans/windows/forum/all/windows-10-打开windows/286f8a35-6a74-433c-b00f-bcd03812d180 I’m not sure why this solution is effective, but it did resolve the issue with my WSL2 not functioning properly.

I resolved the 0x80370102 error through the following steps:

  1. bcdedit /set hypervisorlaunchtype auto
  2. Disable the “Virtual Machine Platform” feature
  3. Restart your PC
  4. Re-enable the “Virtual Machine Platform” feature
  5. Restart your PC

for me it was enough:

  1. bcdedit /set hypervisorlaunchtype auto
  2. Disable the “Virtual Machine Platform” feature no need to restart your PC
  3. Re-enable the “Virtual Machine Platform” feature
  4. Restart your PC

I also have the same issue. When this problem occurred, both my Windows Sandbox and WSL2 stopped working properly. Then I found an article about fixing the Sandbox and resolved the issue by following these steps:

Uninstall Windows Sandbox.

Restart your computer.

Open Command Prompt (Run as administrator) and execute the following command:

bcdedit /set hypervisorlaunchtype Auto

Uninstall Hyper-V.

Restart your computer.

Install Hyper-V.

Restart your computer and verify that Hyper-V is working.

Install Windows Sandbox.

Restart your computer and verify that Sandbox is functioning properly.

The link: https://answers.microsoft.com/zh-hans/windows/forum/all/windows-10-打开windows/286f8a35-6a74-433c-b00f-bcd03812d180 I’m not sure why this solution is effective, but it did resolve the issue with my WSL2 not functioning properly.

Thanks for your answer. I was really stuck on that error. Following first 6 steps helped me to install sucessfully Ubuntu and run docker server on my Winddoows 11 machine