WSL2 Won't Start? Fix Virtual Machine Platform Error

That WSL2 error is annoying. Let's fix it.

You installed WSL2, tried to run a Linux distro, and got hit with the 0x80370102 error. I know that flat feeling. You just wanted to fire up Ubuntu, and instead you got a cryptic message about the Virtual Machine Platform not being enabled. Don't worry. The fix is straightforward.

First, turn on the Virtual Machine Platform

This is the number one reason for the error. Windows hides it in the old-school Windows Features dialog. Here's how to get there and flip the switch:

1. Press Windows Key + R, type optionalfeatures, and hit Enter.
2. In the Windows Features dialog, scroll down and find Virtual Machine Platform. It's between Virtualization-based security and Windows Hypervisor Platform on most builds. Check the box.
3. Also make sure Windows Subsystem for Linux is checked. It usually is, but double-check.
4. Click OK. Windows will install the needed files and ask you to restart.

Then set WSL2 as your default version

After the restart, open PowerShell as Administrator (right-click Start, choose Windows PowerShell Admin or Terminal Admin) and run:

wsl --set-default-version 2

If you get a message about needing the kernel update, run wsl --update first. But most modern Windows 10 and 11 builds have it baked in after enabling the platform.

Restart your distro

Now launch your Linux distro from the Start menu. If it still shows the error, run one more command in PowerShell Admin:

wsl --shutdown

Then start the distro again. That resets the WSL state and forces it to use the Virtual Machine Platform you just turned on.

Why this works

WSL2 is different from WSL1. WSL1 translated Linux system calls into Windows calls. It ran inside the existing Windows kernel. WSL2 runs a full Linux kernel inside a lightweight virtual machine. That VM needs the Virtual Machine Platform – it's the low-level component that handles CPU virtualization and memory management for the VM.

When you check that box, Windows enables the Hyper-V hypervisor and the virtualization stack that WSL2 relies on. Without it, WSL2 can't start the VM, so it throws error 0x80370102. Simple as that.

Less common variations of this issue

1. Virtualization disabled in BIOS

If you turned on the Virtual Machine Platform but still get the error, your CPU might have virtualization disabled in the BIOS. This is common on older gaming PCs or prebuilt office machines. Restart your computer, enter the BIOS (usually F2, F10, or Del during boot), and look for Intel Virtualization Technology (VT-x) or AMD SVM. Enable it, save, and boot back to Windows.

2. Hyper-V is off but needed

Some Windows 10 Pro and Enterprise builds need Hyper-V turned on for the Virtual Machine Platform to work properly. Go back to optionalfeatures and also check Hyper-V under the Hyper-V section. Restart again. This is a quirk of certain Windows builds, especially those that were updated from an older version.

3. Third-party antivirus blocking virtualization

Programs like VMware Workstation, VirtualBox, or even some antivirus suites can reserve the virtualization hardware. If you have VMware or VirtualBox installed, try exiting them completely (including background services). If you use Norton, McAfee, or Bitdefender, check their settings for virtualization-based security. You might need to temporarily disable it.

4. Windows Sandbox conflict

Windows Sandbox uses the same virtualization features. If you have it enabled (also in Windows Features), try disabling it temporarily. Sometimes they step on each other. Go back to optionalfeatures, uncheck Windows Sandbox, restart, and see if WSL2 works. You can re-enable Sandbox later.

How to prevent this from happening again

Once WSL2 is running, it usually stays that way. But a few things can break it:

• Windows major updates: Big feature updates sometimes reset your Windows Features. Keep the Virtual Machine Platform and Windows Subsystem for Linux checked. After an update, run wsl --shutdown once to reset things.
• Uninstalling other hypervisors: If you remove VMware or VirtualBox, restart your PC. Their virtualization drivers might leave behind traces that interfere.
• Changing BIOS settings: If you ever update your BIOS or reset it to defaults, remember to re-enable CPU virtualization.

That's it. You should have your WSL2 distro running now. If not, check the Windows Event Viewer under Applications and Services Logs > Microsoft > Windows > Kernel-Power for any hints. But 9 times out of 10, it's the Virtual Machine Platform checkbox. Enjoy your Linux terminal on Windows.