Complete Guide to Fixing WSL Error 0x80370102: Virtualization Solutions

Understanding the Problem

When attempting to install, update, or start Windows Subsystem for Linux (WSL), users often encounter the following critical error:

WslRegisterDistribution failed with error: 0x80370102
Error: 0x80370102 The virtual machine could not be started because a required feature is not installed.
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 necessary virtualization support required to run WSL 2. Unlike WSL 1, which uses a translation layer, WSL 2 requires actual virtualization technology to create a lightweight virtual machine for Linux distributions.

Root Causes Analysis

The 0x80370102 error stems from several potential issues:

Primary Causes

Hardware Virtualization Disabled: Intel VT-x or AMD-V not enabled in BIOS/UEFI
Windows Features Missing: Virtual Machine Platform or Hyper-V components not installed
Hypervisor Configuration: Incorrect hypervisor launch type settings
System Incompatibility: Older hardware that doesn’t support required virtualization features

Secondary Causes

Conflicting virtualization software (VirtualBox, VMware)
Windows Security features blocking virtualization
Corrupt Windows system files
Insufficient system resources

Comprehensive Solution Guide

Method 1: Quick Fix (Recommended First Step)

This method resolves approximately 85% of WSL 0x80370102 errors:

Open Command Prompt/PowerShell as Administrator
- Press Win + X
- Select “Windows PowerShell (Admin)” or “Command Prompt (Admin)”
Execute the hypervisor command:

bcdedit /set hypervisorlaunchtype auto

Restart your computer immediately
Test WSL installation:

wsl --install Ubuntu

Why this works: This command configures Windows to automatically start the hypervisor at boot time, which is essential for WSL 2 operation.

Method 2: BIOS/UEFI Virtualization Setup

If the quick fix doesn’t resolve the issue, ensure hardware virtualization is enabled:

Step 1: Access BIOS/UEFI Settings

Restart your computer
Press the BIOS key during startup (varies by manufacturer):
- ASUS: F2 or Delete
- HP: F10 or Esc
- Dell: F2 or F12
- Lenovo: F1, F2, or Enter
- MSI: Delete or F2
- Acer: F2 or Delete

Step 2: Enable Virtualization Features

Look for these settings (names vary by manufacturer):

Intel Processors:

Intel VT-x Technology
Intel Virtualization Technology
Virtualization Extensions
VT-x

AMD Processors:

AMD-V
SVM Mode
AMD Virtualization Technology
Secure Virtual Machine

Enable the appropriate option
Save and Exit (usually F10)
Allow system to restart

Method 3: Windows Features Configuration

Ensure all required Windows features are properly installed and configured:

Option A: PowerShell Method (Recommended)

# Enable WSL feature
dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart

# Enable Virtual Machine Platform
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart

# Enable Hyper-V (Windows Pro/Enterprise only)
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

Option B: GUI Method

Press Win + R, type appwiz.cpl
Click “Turn Windows features on or off”
Enable these features:
- ☑️ Windows Subsystem for Linux
- ☑️ Virtual Machine Platform
- ☑️ Windows Hypervisor Platform
- ☑️ Hyper-V (if available)
Click OK and restart when prompted

Method 4: WSL 2 Kernel Update and Configuration

Download WSL 2 Linux kernel update:
Visit: https://aka.ms/wsl2kernel
Install the update package
Set WSL 2 as default version:

wsl --set-default-version 2

Verify WSL installation:

wsl --list --verbose

Advanced Troubleshooting

Verification Steps

Check Virtualization Status

Open Task Manager (Ctrl+Shift+Esc)
Navigate to Performance tab
Click CPU
Verify Virtualization: Enabled in bottom-right corner

System Information Check

# Check system info
systeminfo | findstr /i hyper

# Check Windows features
Get-WindowsOptionalFeature -Online | Where-Object {$_.FeatureName -like "*Hyper*" -or $_.FeatureName -like "*Virtual*"}

# Check WSL status
wsl --status

Conflict Resolution

Third-Party Virtualization Software

If you have other virtualization software installed:

VirtualBox: Update to version 6.1.16+ (supports Hyper-V)
VMware Workstation: Update to version 15.5.5+ (supports Hyper-V)
Docker Desktop: Ensure WSL 2 backend is selected

Windows Security Interference

Some security features may block virtualization:

Open Windows Security
Go to Device Security
Check Core Isolation settings
Temporarily disable Memory Integrity if enabled
Restart and test WSL

System Compatibility Check

Minimum Requirements

Windows Version: Windows 10 version 1903+ or Windows 11
Architecture: x64 processor
Memory: 4GB RAM minimum (8GB recommended)
Virtualization: Hardware virtualization support

Check Your System

# Check Windows version
winver

# Check processor architecture
wmic cpu get Name,AddressWidth,Architecture

# Check available memory
wmic computersystem get TotalPhysicalMemory

Alternative Solutions

If WSL 2 Continues to Fail

Option 1: Use WSL 1

WSL 1 doesn’t require virtualization:

# Install distribution with WSL 1
wsl --install --distribution Ubuntu --version 1

# Convert existing installation to WSL 1
wsl --set-version Ubuntu 1

Option 2: Reset WSL

Complete WSL reset and reinstallation:

# Unregister all distributions
wsl --unregister Ubuntu

# Reset WSL
wsl --shutdown
wsl --unregister docker-desktop
wsl --unregister docker-desktop-data

# Reinstall WSL
wsl --install

Registry Modifications (Advanced Users Only)

⚠️ Warning: Backup your registry before making changes

# Enable Hyper-V via registry (if Windows features method fails)
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\OptionalFeatures\Microsoft-Hyper-V-All" /v Installed /t REG_DWORD /d 1

# Enable Virtual Machine Platform via registry
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\OptionalFeatures\VirtualMachinePlatform" /v Installed /t REG_DWORD /d 1

Prevention and Best Practices

System Configuration Best Practices

Keep Windows Updated: Regular updates include WSL improvements
BIOS Updates: Ensure latest BIOS/UEFI for better virtualization support
Driver Updates: Keep chipset and CPU drivers current
Resource Management: Allocate sufficient RAM and storage for WSL

WSL Configuration Optimization

Create a .wslconfig file in your user directory for optimal performance:

# %UserProfile%\.wslconfig
[wsl2]
memory=4GB
processors=2
swap=2GB
swapFile=%USERPROFILE%\\AppData\\Local\\Temp\\swap.vhdx

Common Error Variations

Related error codes that may appear with similar solutions:

0x80370100: Virtual machine platform not enabled
0x80370101: Virtualization disabled in firmware
0x80370103: Virtual machine platform feature required
0x80370105: Hypervisor not running

When to Seek Further Help

Contact support if you encounter:

Persistent errors after following all steps
Hardware-specific virtualization issues
Corporate environment with restrictive policies
Legacy hardware compatibility problems

Useful Resources

Conclusion

The WSL error 0x80370102 is primarily a virtualization configuration issue that can be resolved through systematic troubleshooting. The quickest solution is often the bcdedit /set hypervisorlaunchtype auto command followed by a system restart. However, if this doesn’t work, the comprehensive approach of enabling BIOS virtualization, configuring Windows features, and installing necessary updates will typically resolve the issue.

Remember that WSL 2 requires modern hardware with virtualization support. If your system doesn’t meet these requirements, WSL 1 remains a viable alternative for most development tasks. Regular system maintenance, including Windows updates and driver management, will help prevent these issues from recurring.

For enterprise environments or complex setups, consider consulting with your IT department about virtualization policies and hardware requirements before implementing these solutions.

Fix WSL Error 0x80370102: Complete Virtualization Guide