Error Codes Wiki

WSL Error 0x80370102 — Virtual Machine Could Not Be Started

Errorsystem

Overview

Fix WSL (Windows Subsystem for Linux) error 0x80370102 when the virtual machine platform cannot start due to disabled virtualization or Hyper-V conflicts.

Key Details

  • Error 0x80370102 occurs when WSL 2 cannot start its lightweight virtual machine
  • WSL 2 requires hardware virtualization (VT-x on Intel, AMD-V on AMD) enabled in BIOS
  • The Virtual Machine Platform Windows feature must be enabled
  • Third-party virtualization software (VMware, VirtualBox older versions) may conflict with WSL 2
  • Windows Home edition supports WSL 2 — Hyper-V feature is NOT required

Common Causes

  • Hardware virtualization (VT-x/AMD-V) disabled in BIOS/UEFI
  • Virtual Machine Platform Windows feature not installed
  • Conflict with VMware Workstation or VirtualBox version that does not support Hyper-V coexistence
  • Windows version too old — WSL 2 requires Windows 10 version 1903+ (build 18362+)

Steps

  1. 1Enable virtualization in BIOS: restart > enter BIOS > Advanced > CPU Configuration > enable Intel VT-x or AMD-V
  2. 2Enable Virtual Machine Platform: PowerShell (admin) > 'dism /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart'
  3. 3Enable WSL feature: 'dism /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart'
  4. 4Restart after enabling features, then run 'wsl --update' to get the latest WSL kernel
  5. 5If using VMware/VirtualBox: update to versions that support Hyper-V coexistence (VMware 15.5.5+, VirtualBox 6.0+)

Tags

wsl0x80370102virtualizationvirtual-machinelinux

Related Items

More in System

Frequently Asked Questions

Open Task Manager > Performance > CPU. Look for 'Virtualization: Enabled'. If it says Disabled, you need to enable VT-x or AMD-V in your BIOS/UEFI settings.