WSL2 & virtualization · 5 min read

Get your PC ready for WSL2

A practical checklist for firmware virtualization, Windows features, and error 0x80370102.

Start with the firmware setting

WSL2 uses virtualization. On AMD systems the firmware setting is often called SVM Mode; on Intel systems look for Intel Virtualization Technology or VMX. Use your motherboard’s documentation for the exact menu.

Install WSL on a supported Windows PC

Follow Microsoft’s current WSL installation instructions. On supported Windows releases, open PowerShell as administrator and run:

wsl --install

Restart when prompted. To inspect installed distributions and their WSL version, run:

wsl --list --verbose

If you see error 0x80370102

  1. Check that hardware virtualization is enabled in BIOS and reported as enabled in Task Manager.
  2. Check the Windows Virtual Machine Platform optional component and restart after enabling it.
  3. If Windows itself is running inside a virtual machine, verify that the host supports and exposes nested virtualization.
  4. Use Microsoft’s troubleshooting steps to inspect hypervisor configuration and other virtualization software.
A WSL2 error is not proof of an incorrect BIOS setting. Firmware virtualization, Windows components, the hypervisor, and nested virtualization are separate checks.

Original sources

Source-linked editorial summary · Reviewed 2026-10-22 · Not hardware-tested