If you see error 0x80370102 when trying to register or start a WSL distribution on Windows 10, it usually means virtualization is disabled or the Windows Subsystem for Linux optional feature is not fully enabled. The fix is to enable virtualization in your BIOS/UEFI and turn on the required Windows features, then restart your PC.
What causes error 0x80370102?
This error appears when the Windows Subsystem for Linux (WSL) cannot start the virtual machine that runs the Linux distribution. WSL2 uses a lightweight virtual machine, and that VM needs the CPU’s virtualization extensions (Intel VT-x or AMD-V) to be available. The most common causes are:
- Virtualization is disabled in the BIOS/UEFI settings.
- The “Virtual Machine Platform” or “Windows Hypervisor Platform” optional features are not enabled.
- Hyper-V is disabled or not fully installed (if you’re using WSL2).
- Another hypervisor (like VirtualBox or VMware) is conflicting with Windows’ Hyper-V.
- Your CPU doesn’t support virtualization, or it’s an older model that lacks the needed instructions.
How to check if virtualization is enabled
Before changing settings, verify whether your PC already has virtualization enabled. Open Task Manager (Ctrl+Shift+Esc), go to the Performance tab, and select CPU. Look at the bottom-right corner for “Virtualization: Enabled” or “Disabled.” If it says Disabled, you’ll need to enter your BIOS/UEFI to turn it on. If it says Enabled, the issue is likely in the Windows features, not the BIOS.
You can also check via Command Prompt. Run systeminfo and look for the lines that mention Hyper-V requirements. If they all say “Yes,” virtualization is ready.
Step-by-step fix for error 0x80370102
Work through these steps in order. Most users find the fix after step 2 or 3.
- Enable virtualization in BIOS/UEFI. Restart your PC and press the key to enter setup (usually Del, F2, F10, or Esc, depending on your motherboard). Look for a setting called “Intel Virtualization Technology,” “Intel VT-x,” “AMD-V,” or “SVM Mode.” Set it to Enabled, save and exit. The exact location varies, but it’s often under Advanced, CPU Configuration, or Security.
- Turn on the required Windows features. Open Control Panel > Programs > Turn Windows features on or off. Make sure these are checked: “Virtual Machine Platform,” “Windows Hypervisor Platform,” and “Windows Subsystem for Linux.” If you’re using WSL1, you only need “Windows Subsystem for Linux,” but for WSL2 you need all three.
- Restart your PC. After changing features, Windows will ask to restart. Do it, then try launching your distribution again.
- Set WSL2 as the default version. Open PowerShell as Administrator and run
wsl --set-default-version 2. If you get a message about needing the Virtual Machine Platform, you missed step 2. - Update WSL. Run
wsl --updatein the same PowerShell window. This ensures you have the latest WSL kernel and components. - Check for hypervisor conflicts. If you use VirtualBox or VMware, their hypervisor can block WSL2. Either disable those programs’ hypervisor modules or uninstall them temporarily to test.
Why does WSL2 need virtualization?
WSL2 runs a real Linux kernel inside a lightweight virtual machine. That VM is managed by Windows’ Hyper-V hypervisor, which requires the CPU’s hardware virtualization extensions. Without them, the VM cannot start, and you get error 0x80370102. This is different from WSL1, which translated Linux system calls directly on the Windows kernel and didn’t need a VM. WSL2 gives better file system performance and full kernel compatibility, but it comes with the virtualization requirement.
If your CPU is from around 2005 or earlier, it might not support the required extensions. You can check your CPU model online, but most modern processors (Intel Core series, AMD Ryzen) support it.
What if virtualization is already enabled?
If Task Manager shows Virtualization: Enabled and you still get the error, the problem is likely the Windows features. Re-enable them by unchecking and re-checking the boxes. Sometimes a Windows update resets these features. Also, make sure you’re running Windows 10 version 2004 or later, as WSL2 requires that. To check your version, press Win+R, type winver, and look at the version number.
Another possibility is that your PC has “Core Isolation” or “Memory Integrity” enabled in Windows Security, which can interfere. Try turning it off temporarily to see if that helps. Go to Windows Security > Device Security > Core Isolation, and turn off Memory Integrity. If that fixes it, you may need to update your drivers or keep it off (though it’s a security feature, so weigh the trade-off).
Alternative: use WSL1 instead
If you cannot enable virtualization (e.g., your CPU doesn’t support it, or you’re on a locked company PC), you can still use WSL1. WSL1 doesn’t require a VM, so it works without virtualization extensions. To convert a distribution to WSL1, open PowerShell as Administrator and run wsl --set-version <distro-name> 1. Replace <distro-name> with the actual name (e.g., Ubuntu). You can list installed distributions with wsl --list --verbose.
Keep in mind that WSL1 has some differences: it doesn’t support all Linux kernel features, and file I/O on Windows drives is slower. But for many development tasks, it works fine.
Frequently Asked Questions
Will this error damage my PC or data?
No. Error 0x80370102 just means the Linux VM didn’t start. Your Windows files and installed distributions are safe. Fixing it won’t delete anything.
Do I need Hyper-V installed to use WSL2?
Yes, WSL2 uses the Hyper-V hypervisor, but you don’t need to install the Hyper-V management tools. The “Virtual Machine Platform” feature installs the necessary components automatically. You do not need to enable Hyper-V in the Windows features list separately.
Can I use WSL2 on Windows 10 Home?
Yes. WSL2 works on Windows 10 Home since version 2004. The Virtual Machine Platform feature is available on Home editions.
How do I know if my CPU supports virtualization?
Open Task Manager > Performance > CPU and look for “Virtualization.” If it says “Enabled,” your CPU supports it. If it says “Disabled,” it might still support it but is turned off in BIOS. If the line is missing, your CPU likely doesn’t support it, or it’s very old.
Why does the error appear when I try to install a new distribution?
The error can occur during installation because the distribution tries to start immediately after download. If virtualization is off, the start fails. Follow the fix steps above, then uninstall the distribution and reinstall it.
Is there a way to fix this without restarting?
No. Enabling virtualization in BIOS and turning on Windows features both require a restart. You cannot apply these changes without rebooting.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- How to View Wi-Fi Password on iPhone
- How to Stream on Twitch from PC
- GTM vs Facebook Pixel: What’s the Difference?
- Windows 10 Won’t Boot? Fix It in 30 Minutes
- Ubuntu 26.04 LTS Requirements & Hardware Checks
- ATK0100 Driver: Do You Need to Install It?