The WslRegisterDistribution Failed With Error 0x80370102 is a common problem for those who use the Windows Subsystem for Linux feature. The primary solution to the error is to correctly configure the Lxssmanager.exe service in the Service Manager of your computer. Please read more about it in the article further.
WslRegisterDistribution Failed With Error 0x80370102
What causes WslRegisterDistribution Failed With Error 0x80370102 issue?
The WslRegisterDistribution Failed With Error 0x80370102 issue is caused when the Lxssmanager.exe service is inconsistent. However, the issue could also be caused if the Hyper-V settings are disabled or if you use an Insider build of Windows.
Try the following solutions sequentially to solve the problem:
1] Fix the status of the LXSS Manager service
The LXSS Manager service is responsible for managing the interaction between the Windows computer and the Windows Subsystem for Linux. If this service is disabled, you may encounter the Error 0x80370102 along with WslRegisterDistribution Failed. The solution is to restart this service and make it automatic. The procedure is as follows:
Search for “Services” in the Windows Search bar.
Open the Services app.
Scroll down to the LXSS Manager service in the list. Double-click the service to open its properties.
Change the Startup Type to Automatic.
Click on Start if the service is not already started.
Click on Apply and then on OK to save the settings.
2] Enable Hyper-V
The Hyper-V service is crucial to the working of Windows Subsystem for Linux. You will have to activate it before proceeding with further solutions. The procedure to activate the Hyper-V or Windows HyperVisor Platform service is as follows:
Press Windows + R to open the Run window.
Type the command APPWIZ.CPL in the Run window and hit Enter to open the Programs and Features window.
In the left pane, click on Turn Windows Features ON or OFF. If you encounter the prompt for administrator permissions, click on YES.
You will notice Windows Hypervisor Platform in the list.
Check the checkbox associated with Windows Hypervisor Platform.
Click on OK to save the settings.
Reboot your system and try accessing the Windows Subsystem for Linux once again.
3] Enable Nested Virtualization on your system
A lot of users confirmed that enabling Nested Virtualization will help you with fixing the issue. The procedure is as follows:
Search for PowerShell in the Windows Search bar.
Click on Run as administrator in the right pane to open the elevated PowerShell window.
Copy-paste the following command in the elevated PowerShell window and hit Enter to execute the command:
Set-VMProcessor <VMName> -ExposeVirtualizationExtensions $true
Reboot your system after executing this command and try to run Windows Subsystem for Linux once again.
By the time you exhaust all these 3 solutions, your problem should be fixed.
If this was helpful, then please let us know in the comment section below.
I am Karan Khanna, a technology enthusiast and Windows geek. Prior to starting my own channel, I worked with TheWindowsClub. I have previously worked as a vendor employee for Microsoft (on Unisys’s payroll) and helped top Microsoft employees with their technical issues.