Fix WSL2 Error 0x80370102 in VMware
In this video, I show you how to fix the 0x80370102 error when trying to run WSL2 inside a Windows VM on VMware. The solution is simple—enable nested virtualization in VMware and turn on the required Windows features.
📌 Steps to Fix
1. Enable Nested Virtualization in VMware
Shut down your Windows VM completely
Right-click the VM → Settings
Go to Processors
Check "Virtualize Intel VT-x/EPT or AMD-V/RVI" (or "Enable nested virtualization" depending on your version)
Click OK
For Hyper-V:
If you're using Hyper-V as your host, open PowerShell as Administrator and run:
Set-VMProcessor -VMName "YourVMName" -ExposeVirtualizationExtensions $true
For VirtualBox:
In VirtualBox, go to Settings → System → Processor. Check 'Enable Nested VT-x/AMD-V'. Then boot up your VM.
2. Enable Required Windows Features
Start your Windows VM
Search for "Turn Windows features on or off" in the Start menu
Scroll down and check both:
☑ Virtual Machine Platform
☑ Windows Subsystem for Linux
Click OK and restart when prompted
3. Install or Launch WSL
After restart, open PowerShell as Administrator
Run: wsl --install
Once complete, restart your VM again
Launch Ubuntu from the Start menu
4. Verify Installation
wsl --list --verbose
You should see your distribution listed with version 2.
Image Source:
Hyper-V logo from https://commons.wikimedia.org/wiki/Fi...
VMWare logo from https://commons.wikimedia.org/wiki/Fi...
VirtuaBox logo from https://commons.wikimedia.org/wiki/Fi...
#WSL2 #VMware #LinuxOnWindows #NestedVirtualization #0x80370102 #WSL #WindowsSubsystemForLinux #VirtualMachinePlatform