Table of Contents
WslRegisterDistribution Failed With Error: 0x80370114
In this article, we will see how to solve WslRegisterDistribution failed with error: 0x80370114 if you are also getting this error in your System. Sometimes when you are trying to install Linux on WSL then you might have observed this WslRegisterDistribution failed with error: 0x80370114. This error usually occurs when Hyper-V service is blocked during the linux installation.
Above error could occur due to multiple reasons, one of the most frequent reasons is that Hyper-V is currently not enabled in your System. This means Hyper-V Host Compute Service, aka vmcompute.exe which is responsible for making Hyper-V service up and running is currently not enabled.
Along with this, Virtual Machine Worker Process, aka vmwp.exe which is responsible for running the instances in Hyper-V hosts is also not enabled. So here we are going to enable both the features using CLI mode and then we will verify the enabled feature in Program settings.
1️⃣ In the first step, you need to enable Microsoft Windows Subsystem feature. To enable this feature, open CLI terminal in administrator mode and run:
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
Deployment 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️⃣ After that restart your system once. Once restarted, go to the next step to verify the enabled feature.
3️⃣ You need to first search 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
- Use Strict CFG
6️⃣ After validating the programs under system settings and program settings, if you now try to start Ubuntu again, you will notice that it will start successfully as shown below.
If after following above steps, you are still getting the same error then you need to check your default WSL version. You need to set your default WSL version to 2 and then restart the system one more time to see if it now fixed the issue.
wsl --set-default-version 2