Table of Contents
WslRegisterDistribution Failed With Error: 0x80370114
In this article, we will explore how to resolve the “WslRegisterDistribution failed with error: 0x80370114” issue. If you’re encountering this error on your system while trying to install Linux on WSL, you’re not alone. This error typically occurs when the Hyper-V service is blocked during the Linux installation process. We’ll guide you through the steps to fix this problem and successfully complete your installation.
This error can occur for several reasons, with one of the most common being that Hyper-V is not enabled on your system. Specifically, the Hyper-V Host Compute Service (vmcompute.exe), which is responsible for keeping the Hyper-V service operational, may not be active.
Additionally, the Virtual Machine Worker Process (vmwp.exe), which is responsible for running instances in Hyper-V hosts, may also be disabled. In this guide, we’ll walk you through enabling both of these features using the CLI, followed by verifying their activation in the Program settings.
1. In the first step, you need to enable the Microsoft Windows Subsystem feature. To enable this feature, open CLI PowerShell (Terminal) in administrator mode and run:
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestartdism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestartDeployment Image Servicing and Management tool
Version: 10.0.19041.844
Image Version: 10.0.19044.2486
Enabling feature(s)
[==========================100.0%==========================]
The operation completed successfully.2. Afterward, restart your system. Once it has rebooted, proceed to the next step to verify that the features have been successfully enabled.
3. You need to first search and then open Windows Security.
4. Next, you need to go to App & browser control → click on Exploit protection settings under Exploit protection as highlighted below.
5. Under System settings Control Flow Guard (CFG) should be “On” by default and under Program settings, you need to make sure both vmcompute.exe and vmwp.exe are available with Control Flow Guard set to below.
- Override System Settings
- On
- Use Strict CFG
6. After verifying the programs under system settings and program settings, you can try starting Ubuntu again. You should now see that it starts successfully, as demonstrated below.
If, after following the steps above, you’re still encountering the same error, it may be necessary to check your default WSL version. Make sure your default WSL version is set to 2, then restart your system once more to see if this resolves the issue.
wsl --set-default-version 2Not a reader? Watch this related video tutorial:
