If you are encountering the error code 0x80370102 on Windows 11, it can be frustrating. This error usually appears when you try to run Windows Subsystem for Linux (WSL) or enable virtualization features.
Fortunately, fixing this error is often straightforward. You just need to follow a few simple steps to resolve the problem.
This article will guide you step-by-step through easy and effective solutions to get your system running smoothly again.
By the end, you should understand why this error happens and how to prevent it in the future.
Quick Note Before You Start
Before diving into fixes, make sure to check the following:
- Your Windows 11 system is up to date with the latest updates installed.
- Your PC supports virtualization technology (most modern CPUs do).
- Virtualization is enabled in your system BIOS/UEFI.
- You have administrative rights on your computer, as some solutions require it.
These checks help ensure the troubleshooting steps will work correctly.
Step 1: Restart Your Computer
Sometimes, the simplest fix is to restart your PC. A fresh start can clear temporary glitches or stuck services that cause error 0x80370102.
To restart:
- Click the Start menu.
- Select the Power icon.
- Choose Restart.
After the reboot, try running WSL or the affected application again to see if the error persists.
Step 2: Enable Virtualization in BIOS/UEFI
This error often occurs because virtualization technology is disabled. Virtualization allows your PC to run virtual machines and is required by WSL 2.
To check and enable virtualization:
- Restart your computer.
- Press the key to enter BIOS/UEFI settings during startup (usually
Delete,F2, orEsc; check your PC’s manual). - Look for settings like “Intel Virtualization Technology,” “VT-x,” or “AMD-V.”
- Make sure virtualization is enabled.
- Save changes and exit BIOS/UEFI.
Enabling virtualization at this level lets Windows use features necessary for WSL and other virtual environments.
Step 3: Enable Required Windows Features
Windows 11 requires certain optional features to be enabled for WSL to work properly. These include the Windows Subsystem for Linux and Virtual Machine Platform.
Here is how to check and enable them:
- Press
Windows + R, typeoptionalfeatures.exe, and press Enter. - In the Windows Features window, scroll down and find:
- Virtual Machine Platform
- Windows Subsystem for Linux
- Check both boxes to enable these features.
- Click OK and wait for Windows to apply the changes.
- Restart your PC when prompted.
This step is important because without these features, WSL cannot function correctly.
Step 4: Update to the Latest WSL Version
Microsoft frequently updates WSL to fix bugs and improve performance. Running an outdated version might trigger errors like 0x80370102.
To update WSL:
- Open PowerShell as Administrator (right-click Start and select “Windows Terminal (Admin)” or “PowerShell (Admin)”).
- Run this command to update WSL:
- Wait until the update completes.
- Restart your computer.
wsl --update
Updating WSL ensures you have the latest fixes and features.
Step 5: Check Windows Services
Some necessary Windows services must be running to avoid error 0x80370102. Specifically, the “LxssManager” service manages WSL instances.
To check this service:
- Press
Windows + R, typeservices.msc, and press Enter. - In the Services window, find LxssManager.
- Make sure its status is “Running.” If not, right-click and select “Start.”
- Also, set its Startup Type to “Automatic” by right-clicking, choosing Properties, and selecting Automatic from the dropdown.
Running this service is vital for WSL to launch correctly.
Alternative Method: Reset or Reinstall WSL
If the above steps don’t work, you can try resetting or reinstalling WSL. Be aware that resetting may remove your installed Linux distributions.
To reset WSL:
- Open Settings > Apps > Apps & Features.
- Find your Linux distribution (e.g., Ubuntu).
- Click it, select Advanced options, then click Reset.
To completely uninstall and reinstall WSL:
- Open PowerShell as Administrator.
- Run:
- Then reinstall the distro from the Microsoft Store.
wsl --unregister <DistributionName>
Replace <DistributionName> with your Linux distro name (e.g., Ubuntu).
Frequently Asked Questions (FAQs)
What causes error 0x80370102 on Windows 11?
This error is primarily caused by virtualization being disabled or required Windows features missing. It can also occur if the WSL service is not running or if WSL is outdated.
How do I know if my PC supports virtualization?
Most modern CPUs support virtualization. You can check by opening Task Manager (Ctrl + Shift + Esc) > Performance tab > CPU section. Look for “Virtualization: Enabled” or “Disabled.”
Can I fix this error without accessing BIOS?
Sometimes yes, but if virtualization is disabled in BIOS, you must enable it there. Software fixes alone won’t work without hardware virtualization enabled.
Will resetting WSL delete my files?
Resetting a Linux distribution will delete all files and settings inside that distro. Backup important data before resetting.
Is this error related only to WSL?
Mostly yes, this error code is associated with virtualization-related issues, often encountered when running WSL or similar virtual environments.
When Nothing Works
If you have tried all the above steps and the error persists, consider these final options:
- Run the Windows Troubleshooter: Go to Settings > System > Troubleshoot > Other troubleshooters and run the relevant troubleshooters.
- Check for BIOS updates from your motherboard or PC manufacturer’s website, as newer BIOS versions may improve virtualization support.
- Visit the official Microsoft WSL documentation and support forums for advanced help: https://docs.microsoft.com/en-us/windows/wsl/
- Consider contacting Microsoft Support if the problem affects critical workflows.
Conclusion
Error 0x80370102 on Windows 11 is commonly caused by virtualization issues or missing Windows features required for WSL. By restarting your PC, enabling virtualization in BIOS, turning on necessary Windows features, and updating WSL, you can usually fix this error quickly.
Always make sure your system is up to date and that the LxssManager service is running properly. If needed, resetting or reinstalling WSL can also help resolve stubborn issues.
With these simple and detailed steps, you should be able to fix error 0x80370102 and continue using WSL or other virtualization tools without interruptions.