How to fix WSL 2 Error 0x80370102 – Virtualization Troubleshooting

The error 0x80370102 in WSL 2 (Windows Subsystem for Linux version 2) typically means that virtualization is not enabled on your system, or there’s a configuration issue preventing the WSL 2 virtual machine from starting.

When this occurs, you’ll usually see the message: “Error: 0x80370102 The virtual machine could not be started because a required feature is not installed.”

This comprehensive troubleshooting guide explains the root causes and provides step-by-step solutions to resolve WSL 2 virtualization errors on Windows 10 and Windows 11.

Read: How to run Windows software on Linux

Why Virtualization is Required for WSL 2

Unlike WSL 1, WSL 2 runs a genuine Linux kernel within a lightweight virtual machine. This architecture requires:

• Hardware virtualization support from your CPU (Intel VT-x or AMD-V)
• Proper BIOS/UEFI configuration with virtualization enabled
• Specific Windows features to be active

Let’s walk through each solution to fix the WSL 2 error code 0x80370102.

Step-by-Step Solutions to Fix WSL 2 Error 0x80370102

1. Enable CPU Virtualization in BIOS/UEFI Settings

This is the most critical step to resolve WSL virtualization problems:

1. Restart Your Computer and Enter BIOS/UEFI: During startup, press the appropriate key to enter the BIOS/UEFI setup (commonly Del, F2, F10, F12, or Esc – check your computer’s documentation if unsure).
2. Locate the Virtualization Settings: The setting is typically found in sections labeled:
   • CPU Configuration
   • Advanced Settings
   • Processor Configuration
   • Chipset Settings
   • Security Features
3. Enable Virtualization Technology: Look for and enable settings labeled:
   • Virtualization Technology (VT)
   • Intel VT-x (for Intel processors)
   • AMD-V or SVM (Secure Virtual Machine) for AMD processors
4. Save Changes and Exit: Save your BIOS/UEFI changes and allow your computer to restart.

2. Enable Required Windows Features for WSL 2

After enabling hardware virtualization, you need to configure Windows properly:

1. Open Windows Features: Search for “Turn Windows features on or off” in the Windows search bar and open it.
2. Enable These Required Features:
   • Virtual Machine Platform ✓
   • Windows Subsystem for Linux ✓
   • Hyper-V (May be automatically enabled with Virtual Machine Platform)
3. Troubleshooting Hyper-V Conflicts: If Hyper-V is already enabled and WSL 2 still fails, try disabling and re-enabling it.
4. Restart Your Computer: Windows will prompt you to restart after changing these settings.

3. Verify Virtualization Status in Windows

After restarting, confirm that virtualization is properly enabled:

Using Task Manager:

1. Press Ctrl+Shift+Esc to open Task Manager
2. Select the Performance tab
3. Check under CPU information for “Virtualization: Enabled“

Using Command Prompt:

Run this command to check virtualization status:

systeminfo

Look for “Virtualization Enabled In Firmware: Yes”

4. Update WSL to the Latest Version

Ensure you’re running the most current version of WSL:

wsl --update

5. Set WSL 2 as Your Default WSL Version

If you have both versions installed, set WSL 2 as the default:

wsl --set-default-version 2

6. Resolve Software Conflicts with WSL 2

Some third-party software can interfere with WSL 2 operation:

• Check for Conflicting Virtualization Software: Temporarily disable or update VirtualBox, VMware, or similar applications
• Review Security Software: Some antivirus or security tools may block Hyper-V or WSL 2 functionality
• Windows Sandbox Conflicts: If Windows Sandbox is enabled, try disabling it temporarily

7. Advanced BIOS/UEFI Virtualization Settings

If you continue experiencing WSL 2 error 0x80370102:

1. Check for Additional Virtualization Settings: Some motherboards have multiple virtualization-related options that all need enabling
2. Update Your BIOS/UEFI: An outdated BIOS/UEFI may have virtualization issues – check manufacturer website for updates
3. Reset BIOS to Default: If settings are corrupted, resetting to defaults and then re-enabling virtualization may help

Common Issues When Troubleshooting WSL 2 Virtualization

• Partial Virtualization Configuration: Both BIOS/UEFI and Windows features must be properly set
• Missing Restart Steps: Always restart after changing virtualization settings
• Hardware Limitations: Some older CPUs may not support the required virtualization features
• Windows Edition Constraints: Home editions may have different requirements than Pro/Enterprise
• Windows Updates: Ensure Windows is fully updated to support the latest WSL 2 features

Conclusion: Running Linux on Windows with WSL 2

By properly configuring your virtualization settings following this guide, you can resolve the WSL 2 error 0x80370102 and enjoy running a full Linux environment within Windows. This powerful developer tool enables seamless cross-platform development without dual-booting or using separate machines.

WSL 2 provides significant performance advantages over WSL 1, particularly for filesystem operations and cross-platform compatibility, making it worth the effort to properly configure your virtualization settings.