Home/Troubleshooting guide
WSL virtualization error guide

WSL error 0x80370102 on Windows 11?

Short answer: error 0x80370102 means the WSL 2 virtual machine cannot start because Windows cannot use a required virtualization layer. Save your work first. Then confirm whether this is a physical PC or a guest virtual machine, check Virtual Machine Platform and the WSL feature, review the Hyper-V Requirements section from Systeminfo.exe, and verify firmware or host-level virtualization through the correct owner. Do not unregister the distribution or delete its virtual disk.

Windows laptop with an abstract layered virtualization diagram beside a paper troubleshooting checklist
Short answer. Microsoft maps 0x80370102 to a virtual machine that cannot start because a required feature is unavailable. On a physical PC, the missing layer is usually Virtual Machine Platform, firmware virtualization, or a hardware requirement. Inside a guest VM, the host may not expose nested virtualization. Check the layers in that order. Enabling the full Hyper-V role, deleting a distribution, or reinstalling Windows is not the default remedy.
Preserve the system first. Save open Windows, Linux, container, and virtual-machine work. Confirm that the authorized owner can recover the device before entering UEFI settings. Do not post a BitLocker recovery key, tokens, usernames, organization names, project paths, or private logs. On a managed device or hosted VM, stop at the administrator boundary.

Protect data and recovery access

Error 0x80370102 happens before a WSL 2 distribution can start its virtual machine. It does not mean the distribution data must be erased. Do not run wsl --unregister, delete ext4.vhdx, purge Docker data, remove WSL folders, or reinstall Windows to test this error.

If BitLocker or device encryption is active, make sure the authorized owner can reach the recovery process before a firmware change. Keep the recovery key private. The BitLocker recovery guide explains the ownership and evidence boundary without asking you to expose the key.

Record the exact error and current state

Copy the full error line, including 0x80370102, and record which command produced it. Note the Windows edition and build, whether WSL ever worked on this machine, and whether a Windows, firmware, virtual-machine, or security-policy change came just before the failure.

Run these read-only commands in Windows Terminal or PowerShell. Save the output privately.

wsl --version
wsl --status
wsl -l -v
systeminfo.exe

A command can fail because the WSL service cannot start. Keep that failure as evidence. Do not turn it into a reason to delete the distribution.

Separate a physical PC from a guest virtual machine

This branch matters. A physical Windows PC controls its own firmware virtualization setting. A Windows guest inside Hyper-V, VMware, a cloud service, or another host depends on that host to expose virtualization extensions.

Machine contextLikely control pointRight owner
Physical personal PCWindows features, CPU capability, and the PC or motherboard firmware settingThe authorized device owner using Microsoft and manufacturer instructions
Work or school PCManaged Windows features, firmware policy, security policy, and recovery controlsThe organization's administrator
Windows guest VMNested virtualization and CPU extensions exposed by the parent hostThe host, cloud, or virtualization administrator
Docker fails but ordinary WSL distributions startDocker Desktop, its WSL integration, or its data stateThe Docker Desktop startup guide

Check the two Windows features without adding more

Open Start, search for Turn Windows features on or off, and record whether Windows Subsystem for Linux and Virtual Machine Platform are selected. They are separate features. WSL 2 needs both.

Do not assume that the full Hyper-V role must be enabled. Microsoft's exact 0x80370102 guidance names Virtual Machine Platform and firmware virtualization. Adding unrelated virtualization features makes the result harder to read and can conflict with a managed configuration.

If one required feature is off and you are authorized to change it, save your work, select only the missing feature, accept the normal Windows restart, and repeat the same WSL command. On a managed PC, give the feature state to the administrator instead.

Read the Hyper-V Requirements section

Near the end of systeminfo.exe, Windows reports the Hyper-V Requirements section. Microsoft lists second-level address translation, VM monitor mode extensions, firmware virtualization, and data execution prevention among the relevant requirements.

Record each line exactly. A result that says a hypervisor has already been detected can change how Windows displays the individual requirement lines. It is evidence, not proof that every WSL layer is healthy.

If the processor does not support the required virtualization capabilities, a Windows feature toggle cannot add them. Do not flash firmware or replace hardware based on one copied result. Confirm the exact processor and system documentation.

Use the PC maker's firmware instructions

Microsoft's Windows 11 route is Settings, System, Recovery, Advanced startup, then Troubleshoot, Advanced options, UEFI Firmware Settings. The wording inside UEFI varies by manufacturer. Find the exact PC or motherboard model before changing anything.

Use the manufacturer's current instructions for Intel Virtualization Technology, Intel VT-x, AMD-V, SVM Mode, or the equivalent setting. Change only the required virtualization setting. Do not change storage mode, Secure Boot, TPM, boot order, memory timing, or unrelated security settings.

If the UEFI option is absent, locked, or controlled by an organization, stop. The device maker or administrator owns the next step. Do not attempt a firmware flash to make the option appear unless the manufacturer specifically requires it for that exact model and the authorized owner accepts the recovery risk.

Route a guest VM to the host owner

Microsoft says WSL 2 inside a virtual machine needs nested virtualization. The guest cannot expose the missing CPU extensions to itself. Changing more Windows features inside the guest will not fix a host that withholds them.

Give the host administrator the guest name, Windows build, exact 0x80370102 message, current WSL feature state, and the relevant systeminfo.exe lines. Microsoft documents a Hyper-V host command for exposing virtualization extensions, but it belongs on the parent host and requires authorization. Other hypervisors and cloud services use their own controls and eligibility rules.

Restart once and repeat the same command

After one authorized Windows-feature, firmware, or host change, restart as required. Run the same WSL command that produced 0x80370102. Record the new output and the time.

If the exact code clears, start the original distribution and confirm that it reaches its normal shell. Then stop changing the system. A successful WSL start does not prove that Docker, an IDE, GPU acceleration, networking, or every distribution is repaired.

If the exact code remains, recheck the recorded layer that was supposed to change. Do not stack a WSL update, distribution reinstall, boot-configuration edit, and registry change on top of one another.

Collect WSL evidence when every prerequisite appears present

Microsoft's WSL troubleshooting guide separates Linux userspace, the distribution, the WSL stack, and physical hardware. An error from wsl.exe that remains after the documented requirements appear satisfied belongs with WSL logs and Microsoft or the WSL project issue path.

Use Microsoft's current WSL troubleshooting guide to collect the requested logs. Redact private paths, account names, organization details, tokens, and distribution contents before sharing anything publicly.

Do not install a WSL prerelease merely because it is newer. WSL 3.0.2 was posted as a prerelease on October 5, 2026, but its listed change does not fix 0x80370102. Current WSL 3.0.1 reports also cover several unrelated performance, Docker, kernel, and networking failures. Those reports do not replace the exact error guidance.

Where OmniMend fits

On a supported Windows PC, OmniMend can help collect and arrange the Windows build, WSL version and state, feature record, systeminfo.exe result, exact error, restart, and retest. That record can make an administrator or support handoff shorter.

OmniMend cannot change UEFI, expose nested virtualization from a host, edit organization policy, recover a BitLocker key, or guarantee that WSL will start. Firmware, host, and managed-device actions remain with the authorized owner.

If you want a separate diagnostic record, see OmniMend's current Windows capabilities or download OmniMend. Read the privacy information before sharing a report.

Editorial sources

Checked October 9, 2026 against Microsoft's exact WSL error guidance, Windows virtualization steps, WSL architecture and nested-virtualization FAQ, hardware requirements, and WSL log and escalation guide. The WSL issue tracker was used for exact error wording and expected diagnostic fields. The current release list was checked so a prerelease would not be presented as the default remedy. OmniMend added the physical-PC-versus-guest split, data-preservation order, and one-change retest. No source supports deleting a distribution or promises one fix for every machine. OmniMend is not affiliated with Microsoft.

Keep the error record.
Find the missing layer.

Separate Windows features, firmware, hardware, and the parent host before changing WSL data.

Get OmniMend