WSL 2 error 0x80370102 prevents a distribution from starting

Troubleshooting guideSources checked: 2026-09-05FaultNote editorial team

What to do first

WSL 2 error 0x80370102 prevents a distribution from starting. CPU virtualization in UEFI/BIOS, Virtual Machine Platform, or nested virtualization may be disabled. Record the current state before changing it, use only the supported Windows path described below, and verify the same operation again after any required restart.

This is a general troubleshooting guide, not an announcement of a current outage.

Affected products and symptoms

Product: WSL 2
Versions and conditions: Windows 11 (confirm the edition and hardware requirements for the feature)
Error codes and identifiers: 0x80370102

Symptoms

WSL 2 error 0x80370102 prevents a distribution from starting.
The same condition can persist after a retry or restart.

Causes and conditions

CPU virtualization in UEFI/BIOS, Virtual Machine Platform, or nested virtualization may be disabled.

Before you start

Save open documents and allow time for a Windows restart if required.
Run administrative actions only on a personally managed PC or with administrator approval.
Save the diagnostic command output so the before and after states can be compared.

Precautions

Do not bulk-delete registry entries, system folders, credentials, or storage metadata.
Do not run unofficial scripts or unknown drivers with administrator rights.

WSL 2 troubleshooting sequence: Check the WSL version and affected distribution; Check the state with systeminfo.exe; Repair through the supported path; Check firmware virtualization and restart; Verify under the same conditions — Procedure overview created by FaultNote. Read the precautions and full instructions before changing settings. Read the full steps

Step-by-step instructions

01
Check the WSL version and affected distribution
#
In Windows PowerShell, run wsl --list --verbose and check that the affected distribution uses VERSION 2. Do not apply CPU virtualization changes to a WSL 1 issue. Save the full 0x80370102 message before continuing.
02
Check the state with systeminfo.exe
#
Check Hyper-V Requirements in systeminfo.exe and the virtualization state under Task Manager > Performance > CPU.
Command or path
```
systeminfo.exe
```
03
Repair through the supported path
#
In an elevated PowerShell window, enable Virtual Machine Platform with the command below. If it fails, record the error and make no further setting changes.
Command or path
```
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
```
04
Check firmware virtualization and restart
#
The DISM command below enables Virtual Machine Platform only. If CPU virtualization is disabled, follow the PC manufacturer’s model-specific UEFI instructions. Have your BitLocker recovery key available and leave unrelated Secure Boot and TPM settings unchanged. Restart Windows after feature installation succeeds.
05
Verify under the same conditions
#
Run wsl --status and repeat the original operation once under the same conditions. If it succeeds, verify again after a restart and record the setting that changed.
Check that no new critical event with the same timestamp and component appears in Event Viewer.
Command or path
```
wsl --status
```

Check the result

The feature starts, connects, or completes without the original error.
The verification command reports the expected enabled, healthy, or connected state.
The result remains correct after a Windows restart and no new matching critical event appears.

If the problem continues

If the same code persists, provide the full message, Windows build, command output, and occurrence time to the PC administrator or Microsoft Support.
If hardware requirements, organization policy, or server settings are responsible, ask the owner to make the change instead of bypassing it on the client.

Scope of this guide

Troubleshooting guide — Restore the feature so it starts, connects, or completes normally and passes the same verification after a Windows restart.

Frequently asked questions

Why does 0x80370102 persist when firmware virtualization is enabled?

Check Virtual Machine Platform and complete the required restart. If Windows itself is a VM, nested virtualization must be exposed by the physical host.

Does WSL 1 require CPU virtualization?

WSL 1 uses a different architecture. Run `wsl --list --verbose` first to confirm the distribution VERSION.

Official sources and dates

Troubleshooting Windows Subsystem for Linux ↗

Source publication or resolution date: Not specified. Sources checked: 2026-09-05. The check date is not the date the problem first occurred. Interface labels can vary between versions and display languages.

Related troubleshooting guides

← Search English guides