WslRegisterDistribution failed with error: 0x80370102

Download PC Repair Tool to quickly find & fix Windows errors automatically

When installing WSL, if you receive an error saying—WslRegisterDistribution failed with fault: 0x80370102—then this post will help you lot resolve it. The Fault occurs for a couple of reasons. Nested Virtualization, a limit on the CPUID, Virtualization back up, and more.

WslRegisterDistribution failed with error: 0x80370102.
Mistake: 0x80370102 The Virtual machine could non be started considering a required characteristic is non installed

WslRegisterDistribution failed with error: 0x80370102

Follow these suggestions to fix the problem.

Enable Nested Virtualization
Enable Hyper-V support at BIOS Level
Disable limitation on CPUID

You will need admin permission and an understanding of BIOS to implement them.

Enable Nested Virtualization

If you have installed Windows in a VM and and so try to install WSL, y'all demand to enable nested virtualization. Launch PowerShell with admin permission, and execute the control as mentioned below.

                                  Ready-VMProcessor                                      -VMName                  <VMName>                    -ExposeVirtualizationExtensions                  $truthful

If this doesn't work, yous need to enable virtualization at the hardware level. This will depend on the BIOS or UEFI. More than on this on the official Microsoft Documents.

Enable Hyper-V support at BIOS Level

Open the BIOS/UEFI and check for settings that may exist called VT-x, AMD-5, SVM, Vanderpool, Intel VT-d, or AMD IOMMU. If information technology'southward AMD, you need to check for AMD-V, SVM, and so on. For Intel, it is normally VT-x.

Follow the linked post to discover out settings according to your computer. The list includes settings for Dell, Asus, Acer, and and so on.

Disable limitation on CPUID

When you turn on your computer, the OS executes CPUID instruction to determine the processor and its capabilities. CPUID uses when you are using a new processor with an old OS. Windows may have issues handling the CPUID information, and hence you lot need to disable it.

The location of Limit CPUID Max will vary for each BIOS/UEFI. Then brand sure to wait around to find where it has on your reckoner.

I hope the post was helpful to resolve the WslRegisterDistribution 0x80370102, which appears when installing WSL.

Similar WslRegisterDistribution failed with errors: 0xc03a001a | 0x80041002 | 0x800700b7 or 0x80080005 | 0x80070422 | 0x80370114 | 0x80070003 | 0x80070032 | 0x8007023e | 0x800701bc | 0x8007019e and 0x8000000d.

Related: Troubleshoot Windows Subsystem for Linux Error Messages and Codes.

Ashish is a veteran Windows, and Xbox user who excels in writing tips, tricks, and features on it to improve your day to day experience with your devices.