If WSL 2 fails to install with error 0x80370102, Docker Desktop won't start, or a virtual machine app says hardware virtualization isn't available, the fix is often a single setting in your motherboard's BIOS. On AMD boards it's usually called SVM Mode; on Intel boards it's Intel (VMX) Virtualization Technology, often shortened to VT-x.
This guide is based on Microsoft's, Docker's and ASUS's official documentation. Forge PC hasn't tested every motherboard, and menu names vary between manufacturers, so check your board's manual if your screens look different.
Why you might need it
Virtualization lets your PC run other operating systems inside Windows. Microsoft says enabling it lets your device emulate a different operating system, such as Android or Linux. On a desktop PC, the usual reasons are:
Microsoft notes that many Windows devices already have virtualization enabled, and ASUS says Intel VMX is enabled by default on its Intel motherboards. So check first before you go into the BIOS.
Step 1: Check whether virtualization is already on
Docker's troubleshooting guide gives two quick checks:
Task Manager: press Ctrl + Shift + Esc, open the Performance tab and select CPU. Look for Virtualization in the details under the graph.
systeminfo: open Terminal and type systeminfo. If the Hyper-V section says "A hypervisor has been detected. Features required for Hyper-V will not be displayed", virtualization is enabled.
If virtualization is already enabled and WSL or Docker still fails, the problem is elsewhere: jump to the troubleshooting section below.
Step 2: Get into the BIOS (UEFI)
Microsoft's route works on any Windows 11 PC:
Open Settings > System > Recovery.
Next to Advanced startup, select Restart now.
Choose Troubleshoot > Advanced options > UEFI Settings > Restart (on some PCs this is labelled UEFI Firmware Settings).
Alternatively, press the setup key while the PC starts. On ASUS boards that's Delete (ASUS also mentions F2 on some models).
Microsoft's advice is worth repeating: only change what you need to in the BIOS, because adjusting other settings could stop Windows from starting.
Step 3: Turn on SVM Mode (AMD) or Intel VMX (Intel)
The exact menu path depends on the manufacturer. ASUS's instructions for its motherboards are:
AMD (Ryzen) boards:
Enter the BIOS and switch to Advanced Mode (press F7 if you start in EZ Mode).
Go to Advanced > CPU Configuration.
Set SVM Mode to Enabled.
Press F10 and confirm to save and restart.
Intel boards:
Enter the BIOS and switch to Advanced Mode (F7 from EZ Mode).
Go to Advanced > CPU Configuration.
Set Intel (VMX) Virtualization Technology to Enabled.
Press F10 and confirm to save and restart.
ASUS also notes that Intel virtualization comes in several parts, VT-x, VT-d and VT-c, depending on the board. For WSL 2, Docker and everyday virtual machines, the CPU setting above is the one that matters. On MSI, Gigabyte, ASRock and other boards, look for the same names (SVM, AMD-V, VMX, VT-x or "Virtualization Technology"), usually under CPU or overclocking settings, or search your board's manual. Microsoft's support page links to the instructions from major PC makers.
Step 4: Turn on the Windows features
The BIOS setting alone isn't always enough. Microsoft's WSL installation guide says you may need to enable the Virtual Machine Platform component. Open PowerShell as administrator and run:
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
Then restart. Microsoft says the wsl --install command, run in an administrator PowerShell window, enables the features needed for WSL by itself, so you only need the manual command if you're installing WSL another way.
Troubleshooting
WSL error 0x80370102 or 0x80070003: Microsoft's WSL troubleshooting page says to make sure virtualization is enabled in the BIOS and that the Virtual Machine Platform feature is turned on. It also notes WSL 2 needs a CPU with Second Level Address Translation (SLAT), which Microsoft says arrived with Intel's first-generation Core (Nehalem) processors and AMD Opteron, so any recent desktop CPU has it.
Docker Desktop still won't start: Docker says it needs both virtualization and either WSL 2 or Hyper-V. Its Windows requirements also list a 64-bit CPU with SLAT and 8GB of system RAM for WSL 2.
The option is missing or greyed out: update your BIOS (see our safe BIOS update guide) and check your board's manual.
The PC won't boot after changing settings: if you changed more than virtualization by mistake, clearing the CMOS resets the BIOS to defaults.
While you're in the BIOS, you may also want to check Secure Boot and TPM; our Secure Boot and TPM guide explains them.
Our verdict
To enable virtualization, check Task Manager or systeminfo first, because it's often already on. If it isn't, restart into the UEFI from Settings > System > Recovery, set SVM Mode (AMD) or Intel (VMX) Virtualization Technology (Intel) to Enabled under the CPU settings, save with F10 and make sure the Virtual Machine Platform feature is on. That fixes most WSL 2 and Docker Desktop start-up errors. Forge PC hasn't tested every board, so follow your manual if menus differ.