Skip to content
FixingBook
Sign In
Verifiedintermediateest. 20 minutes

Fix WSL Error 0x80370102 The Virtual Machine Could Not Be Started

Windows Subsystem for Linux fails to start due to virtualization being disabled in BIOS or missing Windows features.

wslwsl2virtualizationhyper-verror-0x80370102

Confirmed working on: Windows 10 · Windows 11

Before you begin

Match the environmentUse this guide only for Windows 10, Windows 11 or a clearly compatible setup.
Protect recoveryBack up important data and save encryption or account recovery keys before changing system state.
Know when to stopMake one change at a time and stop if the result differs from what the guide describes.

Problem overview

WSL Error 0x80370102 occurs when the Windows Subsystem for Linux cannot launch its background virtual machine. WSL2 requires specific virtualization features enabled at both the hardware and operating system levels.

Common causes

  • Hardware virtualization disabled in the motherboard BIOS
  • Virtual Machine Platform feature disabled in Windows
  • Third-party hypervisors causing conflicts
  • Outdated Linux kernel update package

Solution 1: Enable hardware virtualization

  1. Restart your computer and press the designated key to enter the BIOS or UEFI settings. Common keys include F2, F12, Delete, or Esc.
  2. Locate the virtualization settings. Look for Intel Virtualization Technology (VT-x) or AMD-V.
  3. Set the virtualization option to Enabled.
  4. Save the changes and exit the BIOS.
Expert Tip

If you use VMware or VirtualBox, check their settings. Sometimes these programs lock the hypervisor and block WSL2 from starting.

Solution 2: Enable Virtual Machine Platform and Hyper-V

  1. Press the Windows key, type optionalfeatures, and press Enter.
  2. Check the box next to Virtual Machine Platform.
  3. Check the box next to Windows Hypervisor Platform.
  4. Click OK and allow Windows to download the required files.
  5. Restart your computer when prompted.

Solution 3: Set WSL default version via PowerShell

  1. Open PowerShell as an administrator.
  2. Enable the WSL feature directly using Deployment Image Servicing and Management:
dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
  1. Enable the Virtual Machine Platform:
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
  1. Restart your computer.
  2. Open PowerShell again and force WSL to use version 2:
wsl --set-default-version 2

Confirm the result

  1. Repeat the exact action that originally triggered the problem.
  2. Confirm the original error or symptom is gone and no new warning has appeared.
  3. If the guide changed a driver, service, package, or system setting, restart once and test again.
  4. If the result is worse or unexpected, stop. Reverse only the last change using its documented restore option; if none is documented, use your backup or qualified support.

Questions about this fix

Do I need Windows Pro to use WSL2?

No. WSL2 works on Windows Home, but it uses the Virtual Machine Platform instead of full Hyper-V.

Why did WSL work before but stop working now?

A BIOS update or installing third-party virtualization software like VMware can disable or conflict with WSL requirements.

Did this fix work for you?

Weighted Consensus Protocol

Consensus0%
Required100% (Weight 3)
Contributors0
Verified By YouNo
Your Weight--

Did this solution resolve your issue?

Confirming if this works strengthens verification statistics on the registry.

Sign In to VerifySign in required to verify

FixingTeam10,000 rep

Official Project Maintainers

The core engineering and moderation team behind FixingBook. We curate, verify, and maintain the standards of the troubleshooting ledger.

Spotted something outdated? Suggest an edit. Maintainers review submissions within 48 hours.
Share:XReddit

Discussion (0)

No comments yet. Share your experience or verify if this fixed your issue!

Join the Discussion