How to Fix WSL Register Distribution Error 0x80370102?

When you encounter the WSL Register Distribution Error 0x80370102, it typically prevents you from installing a Linux distribution on your Windows Subsystem for Linux (WSL). This error code means that the virtual machine required by WSL could not start due to a missing or disabled system feature.

Error Notification

 

The most common cause is that virtualization is either not enabled in the BIOS/UEFI settings or that the Hyper-V feature is disabled in Windows. Other potential issues include conflicts with Virtualization-Based Security (VBS) or problems with the WSL installation itself.

Now that we’ve covered the potential causes of the WSL Register Distribution Error 0x80370102, let’s move on to practical solutions that can help you resolve this issue and get your WSL environment up and running smoothly.

Solution 1: Enable Hardware Virtualization from BIOS

When users try to run Ubuntu in a VirtualBox without enabling Hardware Virtualization, the system causes multiple errors, such as audio performance issues and the WSL Register Distribution error. A virtual machine acts like a real computer, letting you use different operating systems and software on your device. 

  1. Click Start, then select Power Option and click Restart.
    Restarting PC
  2. Depending on your BIOS manufacturer, the key to log into the BIOS will vary. Press the 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.
  3. Find the CPU configuration section (Menu can be called Processor, CPU config, Chipset).
  4. Find the Virtualization setting and Enable it.Note: The Virtualization setting may be named Intel Virtualization Technology, AMD-V, Hyper-V, VT-X, Vanderpool, or SVM.
  5. Choose the option Save & Exit.
  6. 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 check if Virtualization is enabled under the Performance tab in the Task Manager.

Checking Virtualization

Solution 2: Enable the Hyper-V Feature

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 it is not enabled, an error may occur while installing a Linux distribution to access via Windows. 

  1. Click Start, search for Control Panel, and open it.
    Opening Control Panel
  2. Click on Programs.
    Opening Programs
  3. Click on Programs and Features.
  4. On the left panel, click on the Turn Windows Feature on or off option.
    Turning Windows Features ON or OFF
  5. Check the Hyper-V option and click OK.
    Checking Hyper-V
  6. Now Reboot your system for these changes to take effect. If this doesn’t help, 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 a Hyper-V virtual machine (VM). This helps run a Visual Studio phone emulator in a virtual machine or test configurations that ordinarily require several hosts. It has been reported that activating Nested Virtualization has worked as a solution for many users online. 

  1. Turn off your virtual machine in Hyper-V Manager.
  2. Press Win + X on the keyboard and select Windows PowerShell (Admin) from the pop-up list.
    Opening Windows PowerShell (Admin)
  3. Inside the PowerShell window, copy-paste this command to change the name and values to your VM processor.
    Set-VMProcessor <VMName> -ExposeVirtualizationExtensions $true
    Entering Command
  4. Press Enter to run it.
  5. Now right-click on your virtual machine in Hyper-V Manager and select Settings.
    Opening VM Settings
  6. Click on Memory in the left pane, untick Enable Dynamic Memory and double the RAM value e.g., 2048 > 4096.
    Changing Memory Settings
  7. Start your virtual machine.
  8. 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.
    Connecting VM
ABOUT THE AUTHOR

Kevin Arrows


Kevin Arrows is a highly experienced and knowledgeable technology specialist with over a decade of industry experience. He holds a Microsoft Certified Technology Specialist (MCTS) certification and has a deep passion for staying up-to-date on the latest tech developments. Kevin has written extensively on a wide range of tech-related topics, showcasing his expertise and knowledge in areas such as software development, cybersecurity, and cloud computing. His contributions to the tech field have been widely recognized and respected by his peers, and he is highly regarded for his ability to explain complex technical concepts in a clear and concise manner.