Error when running an installed WSL platform: WslRegisterDistribution failed with error: 0x80370102 [closed]

Question

I'm trying to install WSL2, but getting error above. Virtual Machine platform and Windows subsystem for linux are enabled, also kernel update installed. In BIOS intel virtualization is enabled. How to fix that?

Answer 1

It's worth verifying the machine meets the hardware requirements.

Buried in the WSL troublshooting page under "Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS" the first item is to check Hyper-V System Requirements.

WSL 2 uses a subset of Hyper-V for virtualization, so while you don't need Win 10 Pro, you do still need the hardware to be able to run Hyper-V.

At the time of writing, the docs say Hyper-V requires the following:

• 64-bit Processor with Second Level Address Translation (SLAT).
• CPU support for VM Monitor Mode Extension (VT-x on Intel CPU's).
• Minimum of 4 GB memory. As virtual machines share memory with the Hyper-V host, you will need to provide enough memory to handle the expected virtual workload.

A quick way to check requirements: run msinfo32.exe and under System Summary at the very bottom it notes the Hyper-V requirements:

...in my case, I'm out of luck as my processor lacks SLAT.

Answer 2

I went through the same situation as you. SVM(VT) is enable and Hyper-V option is enable but Can't use WSL2. My problem is rebooting problem. windows 10's reboot is not actual reboot. WSL2 does not complete installed. Try reboot with press shift key.

Answer 3

The issue might be that virtualisation is disabled in you compute. To enable, follow these steps:

1. Open a PowerShell console as Administrator.
2. Run the following command:

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

Ref: Microsoft's enable Hyper-V Docs

If still had this error, make sure hyper-V in CPU is enabled. For AMD CPUs, it's called SVM (in BIOS).

Answer 4

If you're inside a Virtual Machine, your VM may not be setup to run nested VMs:

Windows Nested Virtualization

Answer 5

The problem was in BIOS. You need to disable Limit CPUID Max to get it work.