WSL 2 Error 0x80370114: How to Fix Installing Linux

by | Blog

Trying to install a Linux distro on your Windows machine using WSL 2, and boom — you hit the dreaded error 0x80370114? Don’t worry. It’s a common issue and not as scary as it sounds. We’re going to break it down and fix it in a simple, fun way.

TL;DR

Error 0x80370114 usually means that the Windows Subsystem for Linux can’t access the Virtual Machine Platform. It’s most often caused by Hyper-V being blocked, disabled, or not functioning properly. To fix it, make sure Hyper-V and related virtualization features are enabled, and that no other virtualization tool (like VirtualBox or VMware) is interfering. A few small tweaks, and you’re on your way to running Linux on Windows happily!

What is WSL 2?

WSL stands for Windows Subsystem for Linux. It lets you run a real Linux terminal on your Windows computer. WSL 2 is the newer version, and it comes with better speed, performance, and compatibility.

It’s like having your cake and eating it too. Except in this case, the cake is a penguin-shaped command-line system.

What is Error 0x80370114?

This error usually appears when you try to install or run a Linux Distro in WSL 2. You might see:

Error: 0x80370114
The operation could not be started because a required feature is not installed.

Or a similar message that makes you want to throw your laptop into the sea.

But don’t worry. There’s a fix. Actually, there are several fixes. And we’ll go through them step by step.

Why This Happens

The error mostly happens for one of these reasons:

  • The Hyper-V feature is turned off or disabled.
  • Your computer’s BIOS settings don’t have virtualization enabled.
  • Another tool (like VirtualBox or Docker) is interfering.
  • There’s an issue with the WSL or VM Platform services.

Let’s start with the easiest fixes!

1. Enable Virtualization in BIOS

First things first. WSL 2 needs virtualization turned on at the hardware level. If it’s off in the BIOS, WSL 2 won’t work — no matter what you do on Windows.

Here’s what to do:

  1. Restart your PC.
  2. As it’s starting up, press the BIOS key. It’s usually one of these: Delete, F2, F10, or Esc.
  3. Look for something labeled Intel VT-x, AMD-V, or just Virtualization Technology.
  4. If it’s disabled, turn it ON.
  5. Save and exit BIOS.

This one setting confuses a lot of people, but it’s essential for WSL 2.

Image not found in postmeta
bios virtualization toggle

2. Enable Required Windows Features

WSL 2 needs a few Windows features you might not have active. Let’s turn them on:

  1. Open the Start Menu and search for “Turn Windows features on or off”.
  2. Make sure the following are checked:
    • Virtual Machine Platform
    • Windows Subsystem for Linux
    • Hyper-V (optional but recommended)
  3. Click OK and restart your computer if prompted.

If you like Command Prompt better, you can also open it as admin and run:

dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
dism.exe /online /enable-feature /featurename:Hyper-V /all /norestart

3. Make Sure WSL 2 is Set as Default

Sometimes the issue pops up because you’re accidentally trying to install a distro on WSL 1 instead of WSL 2. Let’s set WSL 2 as the default:

wsl --set-default-version 2

And if you already installed a distro, upgrade it like this:

wsl --set-version distroname 2

Replace distroname with something like Ubuntu, Debian, or whatever distro you’re using. You can check installed distros using:

wsl --list --verbose

4. Check That No Other Tools Are Fighting WSL

If you’re using other virtual machine software like:

  • VirtualBox
  • VMware Workstation
  • Old versions of Docker Desktop

They might not play well with WSL and Hyper-V.

Try shutting them off completely and then re-launch your Linux terminal.

If you suspect any of them are causing problems, uninstall them temporarily and test again.

5. Use PowerShell to Reset the LxssManager Service

WSL runs off a background service called LxssManager. If it’s stuck, WSL won’t work right.

Here’s how to restart it:

  1. Open PowerShell as administrator.
  2. Run this:
Restart-Service LxssManager

Now try opening your Linux distro again!

6. Update Windows and WSL

Newer versions of Windows fix tons of issues with WSL. Make sure your system is up to date:

  1. Go to Settings > Windows Update.
  2. Click Check for updates.

Also update WSL itself with:

wsl --update

7. Full WSL Reset (Last Resort)

Still stuck?

If nothing is working, you can reset WSL itself. WARNING: This might remove installed Linux distros, so back up anything important first.

wsl --unregister distroname

Then reinstall it from the Microsoft Store.

Or even nuke WSL and start fresh (careful!):

dism.exe /online /disable-feature /featurename:Microsoft-Windows-Subsystem-Linux /norestart
dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart

wsl command terminal linux, windows 11 setup

Bonus: Using WSLg for GUI Apps

Now that you’re running Linux again, why not have some fun?

Newer versions of WSL let you use full Linux GUI apps on Windows thanks to WSLg. Think GIMP, VS Code, even Firefox — all running like native apps.

Just install your favorite GUI app right in your WSL terminal:

sudo apt update
sudo apt install firefox

Then launch it by just typing:

firefox

Cool, right?

firefox linux gui wslg, windows desktop, terminal app

Conclusion

Error 0x80370114 can be annoying, but it’s definitely fixable. In most cases, it only takes a few setting tweaks. Follow the steps above, and you’ll have your Linux terminal up and running in no time.

Want a pro tip? Bookmark this page for next time. Or, better yet, pass it along to a frustrated friend.

Happy hacking!

Pin It on Pinterest