Understanding the Root Cause
WSL 2 relies on the Hyper-V architecture to run its lightweight utility VM. When you see 0x80370102, it means the operating system failed to start this virtual machine environment. Even if Intel VT-x or AMD-V is active in the UEFI/BIOS settings, Windows may be blocking access due to security features like Core Isolation or Memory Integrity. Additionally, third-party virtualization software such as VMware or VirtualBox can hijack the hypervisor lock, preventing WSL from initializing.
Verify Hyper-V Status
The first step is to ensure that the necessary Windows features are fully enabled. Open PowerShell as an administrator and run the following command to check the status of the virtual machine platform:
dism /online /get-featuresinfo /featurename:Microsoft-Hyper-VIf the state is Disabled, enable it using:
dism /online /enable-feature /featurename:Microsoft-Hyper-V /all /norestartAfter enabling, restart your computer. If the feature was already enabled, proceed to verify that the Hyper-V service is running by checking Services.msc for "Hyper-V Virtual Machine Management."
Disable Conflicting Hypervisors
One of the most common causes of this error is another application claiming exclusive access to hardware virtualization. If you have VMware Workstation, VirtualBox, or Android Studio installed, they may be interfering with WSL. You can test this by temporarily uninstalling these applications or disabling their hypervisor integrations.
For VMware users specifically, ensure that the vmware.exe process is not running in the background. If you do not need these applications, uninstalling them often resolves the conflict immediately. For more details on managing virtualization conflicts, you might find our guide on BIOS Popup Setup Interrupting Virtualization Every 2 Months helpful for understanding deeper hardware-level interruptions.
Enable Core Isolation and Memory Integrity
Windows Security includes a feature called Core Isolation which uses hardware virtualization to protect critical parts of your system. If this is disabled, WSL may fail to launch. Navigate to Settings > Update & Security > Windows Security > Device Security. Click on Core isolation details and ensure that Memory integrity is turned On. Toggle it off and back on again if it is already enabled to reset the configuration.
This setting forces Windows to re-evaluate the hypervisor availability during boot, which can clear stuck states that cause the 0x80370102 error.
Reset WSL Components
If the above steps do not work, the WSL installation itself may be corrupted. Open PowerShell as Administrator and execute the following commands to update and reset the subsystem:
wsl --update
wsl --shutdown
wsl --set-default-version 2The wsl --shutdown command kills all running WSL instances, ensuring a clean state for the next launch. After running these commands, try launching Ubuntu again from the Microsoft Store or via the terminal.
Re-register the Ubuntu App
Sometimes the specific app package registered in Windows becomes invalid. Find the package name for your Ubuntu version by running:
Get-AppxPackage *Ubuntu*Note the PackageFullName. Then, reinstall it using:
Add-AppxPackage -register "C:\Program Files\WindowsApps\[PackageFullName]\AppxManifest.xml" -disabledevelopmentmodeReplace [PackageFullName] with the actual string retrieved in the previous step. This forces Windows to re-register the application manifest, fixing broken links to the WSL backend.
Frequently Asked Questions
Why does my PC say virtualization is enabled but WSL still fails?
Hardware virtualization being enabled in BIOS only provides the foundation; Windows must also allow the OS to use it. Software locks, such as Core Isolation settings or conflicting third-party hypervisors, can block access even when the CPU feature is active.
Can I use WSL 2 with VirtualBox installed?
It is possible but difficult. VirtualBox typically requires exclusive control over the hypervisor. You can try configuring VirtualBox to use legacy drivers or disabling its own hypervisor layer, but uninstalling it is the most reliable solution for stable WSL performance.
What does error 0x80370102 mean exactly?
This error code specifically denotes a failure in the initialization of the Hyper-V virtual machine platform. It indicates that the WSL backend could not create the lightweight utility VM required to run Linux binaries.
How do I check if Hyper-V is actually running?
You can check the System Information tool by typing msinfo32 in the Run dialog. Look for "Hyper-V Requirements" at the bottom; if it lists "A hypervisor has been detected," then the platform is active. If it says none, there is a configuration issue.
Will resetting WSL delete my Linux files?
No, resetting the WSL component via PowerShell commands or reinstalling the app package does not delete your data stored in the Linux filesystem. Your files remain safe in the ext4.vhdx file, though it is always good practice to back up important data before major system changes.