Windows 10: WslRegisterDistribution failed with error: 0x80370102

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



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 then try to install WSL, you need to enable nested virtualization. Launch PowerShell with admin permission, and execute the command as mentioned below.

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


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

Enable Hyper-V support at BIOS Level




Open the BIOS/UEFI and check for settings that may be called VT-x, AMD-V, SVM, Vanderpool, Intel VT-d, or AMD IOMMU. If it’s AMD, you need to check for AMD-V, SVM, and so on. For Intel, it is usually VT-x.

Follow the linked post to find out settings according to your computer. The list includes settings for Dell, Asus, Acer, 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 need to disable it.

The location of Limit CPUID Max will vary for each BIOS/UEFI. So make sure to look around to find where it has on your computer.

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.


This article WslRegisterDistribution failed with error: 0x80370102 first appeared on TheWindowsClub.com.

read more...

 

WslRegisterDistribution error 0x80370102

I am trying to install Ubuntu 20.04 LTS on my PC, but it fails with an error message.

Code:

Installing, this may take a few minutes...WslRegisterDistribution failed with error: 0x80370102Error: 0x80370102 Der virtuelle Computer konnte nicht gestartet werden, da ein erforderliches Feature nicht installiert ist.

Press any key to continue...

My laptop is an Acer E5-551G, running Windows Home version is 2004, build 19041.329. Virtualization is supported and enabled (though no special menu in the BIOS), Hyper-V is enabled and started.





The task manager also says that Virtualization is activated:





I have installed and activated WSL2 and installed the kernel update (https://aka.ms/wsl2kernel). WSL default version is set to 2.

What could be the reason for this error? I haven't found a resource explaining the error code in more detail.

Thank you in advance for any pointers.

Cheers,

Sascha

 

"Error" Installing Linux distro in windows 10 pro wsl2

WslRegisterDistribution failed with error: 0x80370102
Error: 0x80370102 The virtual machine could not be started because a required feature is not installed.

 

Resolving WslRegisterDistribution error 0x80370102 when installing Linux Distro for WSL 2?

# Encountering WslRegisterDistribution error 0x80370102 when installing Linux Distro for WSL 2

I am currently on the `Windows 10 Pro Insider Preview build 18922.rs_prerelease`, and am trying to install a Linux distribution to access via Windows Subsystem for Linux (2). I have tried this for both the Ubuntu and Debian distros and have encountered the
same error in each.

I have successfully downloaded both distros from the Microsoft store, but when I try to first "run" the Ubuntu or Debian "app" the respective console comes up and prints the following text:

Code:

Installing, this may take a few minutes...

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...
Pressing a key at this point automatically exits the console.

---

## Additional information:

- Using the `wsl -l` command shows no installed distros.

- I do have Hypervisor installed and running `bcdedit` does show that `hypervisorlaunchtype` is set to `Auto` in the `Windows Boot Loader` section.

- I did previously have Ubuntu installed and working under WSL 1 before switching to the Windows Insider Program Fast Ring and gaining access to WSL 2, but I was encountering another issue when trying to have it use WSL 2. After
trying to use the command `wsl --set-version Ubuntu 2` I was met with a request to "Enable the Virtual Machine Platform". I had already run `Enable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform` prior, according to the official microsoft
tutorial here https://docs.microsoft.com/en-us/windows/wsl/wsl2-install, but for good measure I did it again and got the same error, and Ubuntu was still on version 1 (I haven't explicitly mentioned it but I was restarting/shutting down when requested/suggested
by windows and tutorials, so I don't believe me not restarting is a cause). In hopes to find a workaround, I ended up uninstalling Ubuntu and hoping I could reinstall it and have it obey the default defined by the `wsl --set-default-version 2` command (suffice
it to say, this did not go as I'd hoped).

- This might be an unrelated issue, but when I initially attempted reinstalling Ubuntu, the Microsoft store had a bit of a fit and could not complete the download- encountering an 'unknown error'. I did a restart, tried again, and
got the same error, but then after telling it to 'try again' it succeeded. I had no such issues installing Debian from the store.

---

## Suggestions Welcome

I've searched for a bit and can't find mention of this error code in particular anywhere else.

In addition, is there anywhere I can look up/access these error codes in any sort of documentation? Ideally so I can make a better informed work-around attempt before bothering you all on here.

All help is appreciated!