How to Resolve WslRegisterDistribution Error 0x80370102 When Installing Linux Distro for WSL 2

Troubleshooting WSL 2 Installation Issues on Windows 10

Trying to install a Linux distribution in Windows Subsystem for Linux (WSL) 2 and running into issues? You’re not alone. The infamous error code 0x80370102 has stumped many Windows users looking to leverage the power of WSL 2.

In this post, we’ll walk through the common causes of the WslRegisterDistribution failed with error: 0x80370102 message and how to resolve them, drawing on insights shared in community forums. With the right fixes, you’ll have Ubuntu, Debian, or your preferred Linux distro up and running in WSL 2 in no time.

Enable Hyper-V for WSL 2

One of the most common culprits behind the 0x80370102 error is that Hyper-V is not enabled. Introduced in Windows 8, Hyper-V is Microsoft’s native hypervisor that allows you to run virtual machines (VMs) on Windows.

Hyper-V is a prerequisite for using WSL 2, which utilizes a lightweight VM to host the Linux environment. So if Hyper-V is disabled, the VM powering WSL 2 cannot start – triggering the 0x80370102 error.

What is error code 0x80073cfe?

Microsoft Store usually works just fine. But, sometimes while updating the apps on your system, you may notice this annoying error code “ ERROR_PACKAGE_REPOSITORY_CORRUPTED. Error Code 0x80073CFE “. After thorough research of the error message, we have concluded that a corrupted registry key is the reason you are experiencing this issue.

How do I fix 0x80370114 error?

When I was stuck at the 0x80370114 error, I needed to uncheck all three of Virtual Machine Platform, Windows Hypervisor Platform and Windows Subsystem for Linux options in Turn Windows features On or Off. Then click Apply, skip the suggested restart, then turn them all back on again, then Apply, this time with a restart.

Enabling Hyper-V is straightforward:

Open Programs and Features via the Run dialog (Windows + R then typeappwiz.cpl)
Click "Turn Windows features on or off"
Check the box for Hyper-V and click OK
Restart your PC

Once your computer boots back up, Hyper-V will be enabled and ready to support WSL 2.

Enable Virtualization in Your PC’s BIOS

If Hyper-V is already enabled but you’re still seeing the WslRegisterDistribution 0x80370102 error, the next thing to check is that virtualization is turned on in your BIOS.

This setting allows Hyper-V to leverage the virtualization capabilities of your processor. It may be labeled VT-x (Intel) or AMD-V (AMD) in your system’s BIOS.

Here’s how to enable it:

Reboot your PC and press the key to enter BIOS, usually Delete or F2
Navigate to the Security tab
Look for an option labeled Virtualization or VT and enable it
Save changes and reboot

With virtualization flipped on in BIOS, Hyper-V and WSL 2 should function properly.

Enable Nested Virtualization

If the previous suggestions don’t resolve the 0x80370102 error, nested virtualization could be the culprit.

How to fix wslregistrationdistribution failed error in Ubuntu?

Specifically, you need to enable Windows Subsystem for Linux before the Ubuntu app will install correctly. If you’ve forgotten to do that, you will get the ‘WslRegistrationDistribution failed’ error. To fix it, open Control Panel and select Programs. Select the Turn Windows features on or off option.

How do I fix windows 11 WSL error?

Press the Windows key to open the Start menu, type Microsoft Store and press Enter. Select My Library from the app’s bottom left corner. Find the Linux distribution app, such as Ubuntu, then click Launch and check whether the problem is solved. Sometimes Windows 11 WSL errors may happen because of a bug in your installed Linux distribution.

Nested virtualization allows you to run VMs within VMs. Since WSL 2 uses a VM, it requires nested virtualization support.

You can enable nested virtualization for WSL 2 by:

Opening an elevated PowerShell prompt
Running:

Set-VMProcessor -VMName <VMName> -ExposeVirtualizationExtensions $true

Replacing<VMName>with your WSL 2 distro name
Allocating at least 4GB RAM to the WSL 2 VM

With nested virtualization enabled, the Windows VM can properly run the WSL 2 Linux VM.

Restart the LxssManager Service

The LxssManager service powers the Windows subsystem for Linux and needs to be in working order. If it’s corrupted or crashing, that can manifest as the 0x80370102 error.

Restarting the LxssManager service can get WSL back up on its feet:

Open the Run dialog with Windows + R
Typeservices.mscand press Enter
Find LxssManager in the list and right-click it
Select Restart
Try installing your WSL 2 distro again

This should refresh the LxssManager service and potentially resolve any issues affecting WSL 2.

What is WSL error 0x80070032?

The WSL error in Windows 11 includes a variety of codes and warnings, and the most prevalent are WslRegisterDistribution Failed with errors: 0x80070032, 0x80370102, 0x8007023e, and 0x8007019e. Now that we’ve covered the causes and error codes, let’s go into the solutions. How we test, review and rate?

Why can’t I access my Ubuntu distribution?

This error has been known to occur after a distribution gets “partially” installed. From PowerShell (as a regular, non-admin user), try running: If it returns an Ubuntu distribution (and you aren’t able to access it), run: # WARNING: Destructive operation.

Enable the Virtual Machine Platform Feature

Finally, another avenue is ensuring the Virtual Machine Platform optional feature is enabled.

This provides the necessary Windows components for Hyper-V and WSL 2 virtualization, so if it’s disabled you can expect trouble.

Turn it on by:

Opening Programs and Features
Clicking "Turn Windows features on or off"
Checking Virtual Machine Platform
Restarting your system

With the Virtual Machine Platform box checked, Windows has what it needs for silky smooth WSL 2 experiences.

When All Else Fails

If you still can’t shake the "WslRegisterDistribution failed with error: 0x80370102" after trying all of the above solutions, don’t lose hope. Other users in your shoes found success by seeking further assistance from Microsoft’s technical support forums and Windows Insider channels.

Why did wslregisterdistribution fail with error 0x80370102?

WslRegisterDistribution failed with error: 0x80370102 Error: 0x80370102 The virtual machine could not be started because a required feature is not installed. When researching this error, and from reading the official WSL 2 install guide from Microsoft, the error always seems to be because the system doesn’t have virtualization enabled in the BIOS.

What does wslregisterdistribution failed 0x80370102 mean?

WslRegisterDistribution failed with error: 0x80370102 Error: 0x80370102 The virtual machine could not be started because a required feature is not installed. Press any key to continue… It means the key components required by the Windows Subsystem for Linux version 2 i.e Virtual Machine Platform is not enabled.

Why did wslregisterdistribution fail with error 0x8000000d?

WslRegisterDistribution failed with error: 0x8000000d Error: 0x8000000d An illegal state change was requested. Press any key to continue… ‘Windows Subsystem for Linux’ Windows Subsystem for Linux has no installed distributions. Use ‘wsl.exe –list –online’ to list available distributions and ‘wsl.exe –install ‘ to install.

We wish you the very best in getting WSL 2 up and running on your Windows machine! Let us know in the comments if any of these tips did the trick or if you discovered another fix.

References

What is WSL error 0x8007019e?

WSL (Windows Subsystem for Linux) is a free and optional feature of Windows 10 that allows users to run Linux programs on Windows. Users have reported seeing this error 0x8007019e as shown in the image below when opening the Linux command prompt. Once this error appears, the user is not allowed to use the WSL based terminal.

How do I fix installation error 0x80070003?

Press any key to continue… Referring to the doc : Installation failed with error 0x80070003 or error 0x80370102 Please make sure that virtualization is enabled inside of your computer’s BIOS. The instructions on how to do this will vary from computer to computer, and will most likely be under CPU related options.