WSL_0x80370102_Solution

by

WSL_0x80370102_Solution

Complete Guide to Fixing 0x80370102 Error in WSL

Problem Description

When attempting to install or start Windows Subsystem for Linux (WSL), you may encounter the following error message:

WslRegisterDistribution failed with error: 0x80370102
Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS.

This error typically indicates that your system lacks the virtualization support required to run WSL 2. WSL 2 requires both the Virtual Machine Platform feature to be enabled and virtualization technology to be activated in your BIOS/UEFI.

Error Causes

The 0x80370102 error is primarily caused by:

  1. Virtualization feature not enabled in BIOS/UEFI
  2. "Virtual Machine Platform" feature not enabled in Windows
  3. Hyper-V feature may not be properly configured
  4. Hypervisor launch type setting is incorrect
  5. Potential conflicts with other virtualization software

Solution

Quick Fix Method (Recommended)

The most effective and straightforward solution is to enable the hypervisor launch type:

  1. Open Terminal or PowerShell as an Administrator
  2. Run the following command: 
    bcdedit /set hypervisorlaunchtype auto
  3. Restart your computer

This command sets the hypervisor launch type to automatic, which resolves most instances of the WSL 0x80370102 error. After completing the restart, you should be able to launch WSL normally.

Step 1: Enable Virtualization in BIOS/UEFI

If the quick method doesn’t work, ensure virtualization is enabled in BIOS:

  1. Restart your computer and press the specific key during startup to enter BIOS/UEFI settings (common keys include F2, Delete, F10, Esc, or F12, depending on your computer brand and model)
  2. In the BIOS/UEFI settings, locate the virtualization option, which may be named:
    • For Intel processors: Intel VT-x, Intel Virtualization Technology, Virtualization Extensions
    • For AMD processors: AMD-V, SVM Mode, Virtualization Technology
  3. Enable this option
  4. Save settings and exit BIOS/UEFI
  5. Restart your computer

Step 2: Enable Virtual Machine Platform in Windows

  1. Enable the Virtual Machine Platform feature using one of these methods:

Method 1: Via PowerShell

Open PowerShell as Administrator and run the following command:

dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart

Method 2: Via Windows Features

  1. Press Win+R, type "control panel" and press Enter
  2. Navigate to "Programs and Features" > "Turn Windows features on or off"
  3. Check "Virtual Machine Platform" and "Windows Subsystem for Linux"
  4. Click OK and restart your computer

Step 3: Enable Hyper-V (if applicable)

Some Windows versions may also require Hyper-V to be enabled:

  1. Open PowerShell (Administrator)
  2. Run the following command:
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

Step 4: Install WSL 2 Kernel Update

  1. Download and install the WSL 2 Linux kernel update package
  2. Restart your computer

Step 5: Set WSL 2 as the Default Version

  1. Open PowerShell (Administrator)
  2. Run the following command:
wsl --set-default-version 2

Verifying Virtualization is Enabled

You can confirm that virtualization is enabled through Task Manager:

  1. Press Ctrl+Shift+Esc to open Task Manager
  2. Switch to the "Performance" tab
  3. Select "CPU"
  4. Check the "Virtualization" status in the bottom right, which should display "Enabled"

Potential Conflicts

If you have other virtualization software installed (like VirtualBox or VMware), it may conflict with WSL 2. If you still experience issues after enabling all necessary features, try:

  1. Temporarily uninstalling other virtualization software
  2. Or updating these software to the latest versions that support Hyper-V

Conclusion

The 0x80370102 error can typically be resolved quickly by executing the bcdedit /set hypervisorlaunchtype auto command and restarting your computer. If this method doesn’t work, you can try enabling virtualization in your BIOS/UEFI, the Virtual Machine Platform feature in Windows, and Hyper-V. Remember that WSL 2 is based on virtualization technology, so ensuring all necessary virtualization support is enabled is crucial.

If you still encounter issues after completing the steps above, it’s recommended to check the official Microsoft WSL documentation or submit a problem report through the Windows Feedback Hub.

Leave a Comment