This error arises when users try to install a Linux distribution to access via Windows Subsystem for Linux 2. After reviewing the user’s feedback and technical authorities in detail, users reported encountering the error message 0x80370102 when trying to install Linux Distro for Windows Subsystem for Linux 2 (WSL2). The error notification is as follows:
What Causes WSL Register Distribution Error 0x80370102?
This error is extremely new and is not encountered just in Linux distros. This error has also been encountered when trying to install the Debian distro as well. We have listed the causes of this problem after reviewing the user’s feedback and technical authorities in detail. This problem may arise due to any of the following reasons:
- Under-Development: This error arises when people try to run a Windows Insider Preview build. A user might be seeing defects or bugs in the build they are using, which is still under development.
- Upgrading WSL: A completely developed version with all the required fixes will support the subsystem. WSL 2 is under development and there are still bugs in it so switching from WSL 1 TO WSL 2 will cause this error.
- Virtualization Disabled: Virtualization is the process of creating a software-based, or virtual, representation of something, such as virtual applications, servers, storage, and networks. This error can occur if the virtualization setting was disabled in the BIOS under Security.
- Hyper-V: It is a Microsoft technology that allows users to create virtual computer environments, and run and manage multiple operating systems on a single physical server. So Wsl Register Distribution Error occurs when Hyper-V is disabled from the bios.
Solution 1: Enable Hardware Virtualization from BIOS
When users try to run Ubuntu in a VirtualBox without enabling the Hardware Virtualization then the system generates multiple errors such as audio performance issues, Wsl Register Distribution error, etc. A virtual machine emulates a computer system so anyone can run different operating systems and programs. Follow the steps below to enable Hardware Virtualization from BIOS:
- Click Start and then select Power Option and click Restart.
- Depending on your BIOS manufacturer, the key to log into BIOS will vary. Press Del, Esc, F1, F2, or F4 key on your keyboard as soon as the screen goes black. Note: If you don’t get in the first time, restart your PC and try another key.
- Find the CPU configuration section (Menu can be called Processor, CPU config, Chipset)
- Find the Virtualization setting and Enable it.
Note: (Virtualization settings can be named as Intel Virtualization Technology, AMD-V, Hyper-V, VT-X, Vanderpool, or SVM).
- Choose the option Save & Exit.
- The computer will reboot with Hardware Virtualization enabled. Check to see if the issue persists. If it does, follow the next method.
Note: Make sure your device supports hardware virtualization. You can see if Virtualization is enabled under the Performance tab of the Task Manager.
Solution 2: Enable the Hyper-V Role
Hyper-V enables administrators to make better use of their hardware by virtualizing multiple operating systems to run off the same physical server simultaneously. If we do not enable it, it generates an error while installing Linux distribution to access via Windows. Follow the steps given below to enable Hyper-V:
- Click Start, search the Control Panel, and open it.
- Click on Programs.
- Click on Program and Features.
- On the left panel, click on Turn Windows Feature on or off option.
- Check the Hyper-V option and click OK.
- Now Reboot your system for these changes to take effect. If this doesn’t help, then proceed with the next solution.
Solution 3: Expose Virtualization Extensions & Change RAM Settings
Nested virtualization is a feature that allows you to run Hyper-V inside of a Hyper-V virtual machine (VM). This helps run a Visual Studio phone emulator in a virtual machine, or testing configurations that ordinarily require several hosts. It has been reported that activating Nested Virtualization has worked out as a solution for many users online. Therefore, follow the steps given below to do so:
- Turn off your virtual machine in Hyper-V Manager.
- Press Win + X on the keyboard and select Windows PowerShell (Admin) from the pop-up list.
- Inside the PowerShell window, copy-paste this command to change the name and values to your VM processor.
Set-VMProcessor <VMName> -ExposeVirtualizationExtensions $true
- Press Enter to run it.
- Now right-click on your virtual machine in Hyper-V Manager and select Settings.
- Click on Memory in the left pane, untick Enable Dynamic Memory and double the RAM value e.g. 2048 > 4096.
- Start your virtual machine.
- Right-click on your virtual machine and select Connect. This will run Hyper-V and your system will restart. Try running Ubuntu again. This should finally fix your problem.