WSL Service Failed: Causes and Solutions in Windows

What the "WSL Service Failed" Error Means

The WSL Service Failed error (sometimes with code 0x80070057 or similar) is a message from the Windows system indicating that the Windows Subsystem for Linux service failed to start. It typically appears when attempting to launch a Linux distribution from the command line (wsl), the Start menu, or via wsl.exe. The exact error text may vary, but the essence is the same: the service responsible for launching the WSL 2 virtual machine or WSL 1 interface has crashed.

Symptoms:

• Running the command wsl or wsl [distribution] in PowerShell/CMD outputs an error.
• In the distribution list (wsl --list --verbose), the status is shown as Stopped or Error.
• The distribution's icon in the Start menu does not launch or closes immediately.

Common Causes

The WSL Service Failed error is usually caused by one of the following specific issues:

1. Corruption of WSL distribution files. The virtual disk files (.vhdx for WSL 2) or the distribution's root filesystem are corrupted, for example, due to an improper shutdown, disk failure, or manual interference in the C:\Users\<User>\AppData\Local\Packages\<Distro>\ folder.
2. Conflict or disablement of Hyper-V components. WSL 2 fully depends on the Virtual Machine Platform (Hyper-V). If the component is disabled, corrupted, or conflicts with other virtualization software (like older versions of VMware or VirtualBox), the WSL service cannot create a virtual machine.
3. Corruption of Windows registry entries related to WSL. Registry keys storing distribution configurations and paths may be damaged or contain incorrect data.
4. Insufficient permissions or blocking by antivirus/firewall. Starting the WSL service requires specific privileges. Antivirus software (especially with active real-time protection) or strict firewall policies can block the creation of a virtual network adapter or file access.
5. Outdated or corrupted WSL kernel version. The Linux kernel (wsl.exe and related components) was updated incorrectly or conflicts with the Windows version.
6. Insufficient system resources. Rare, but possible: if there is very little free space on the disk where WSL files are located, or not enough RAM to start the virtual machine.

Solutions

The methods below are ordered from the simplest and fastest to more complex. Start with the first and proceed to the next if the problem persists.

Method 1: Reinstall the Problematic Distribution

This is the fastest method if the issue is related to corruption of a specific distribution's files (e.g., Ubuntu, Debian). Warning: This method will delete all data and settings inside the distribution! Back up important files (in /home/<user> or other folders) via \\wsl$\<DistroName>\ in Windows Explorer.

1. Open PowerShell or Command Prompt as an administrator.
2. Find the exact name of your distribution:

   wsl --list --verbose
   

   Find the line for your distribution (e.g., Ubuntu-22.04). If its status is Stopped or Error, that's the one.
3. Unregister (remove) the distribution:

   wsl --unregister Ubuntu-22.04
   

   Replace Ubuntu-22.04 with your distribution's name. This removes the distribution's record from the WSL system and its virtual disk.
4. Reinstall the distribution:
   • Via Microsoft Store: Open the Store, find the desired distribution (e.g., Ubuntu 22.04 LTS), and click "Install".
   • Via command line (if Store is unavailable):

     wsl --install -d Ubuntu-22.04
     

5. Launch the distribution from the Start menu or with the wsl command. Set up the new user and password.

Method 2: Update and Repair WSL Components

If reinstalling didn't help or you don't want to lose data, try updating the subsystem itself and repairing system components.

1. In PowerShell (as administrator), run the command to force-update the WSL kernel to the latest stable version:

   wsl --update
   

2. Install the latest WSL version (if available):

   wsl --set-default-version 2
   

   (If you are on WSL 1, this will attempt to upgrade the configuration to WSL 2, which may also help).
3. Check the status of the WSL service:

   Get-Service -Name LxssManager
   

   If the status is not Running, start it:

   Start-Service -Name LxssManager
   

4. Run a Windows system file integrity check. In the same PowerShell:

   sfc /scannow
   

   Wait for completion (may take 10-20 minutes). If SFC finds and fixes files, restart your computer and check WSL again.

Method 3: Verify and Enable Windows Features

WSL, especially version 2, requires mandatory Windows components. Their absence or disablement is a common cause of service failure.

1. Press Win+R, type optionalfeatures.exe, and press Enter.
2. In the "Windows Features" window, find and ensure the following items are checked:
   • Windows Subsystem for Linux (mandatory).
   • Virtual Machine Platform (required for WSL 2).
   • Hyper-V (optional for WSL 2, but enabling it often resolves virtualization issues).
3. If any component was unchecked, check the box and click "OK". Windows will install the selected components and prompt you to restart your computer. Do so.
4. After restarting, check if you can launch WSL.

Method 4: Registry Cleanup (For Advanced Users)

Warning! Incorrect registry edits can make your system unstable. Create a System Restore point ("Control Panel" → "Recovery" → "Configure" → "Create").

Corrupted WSL-related registry keys can prevent the service from starting.

1. Press Win+R, type regedit, press Enter.
2. Navigate to:

   HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Lxss
   

3. Back up this key: right-click on Lxss → "Export", save the .reg file.
4. Inside Lxss, you will see subkeys with letters and numbers (e.g., {GUID}). Each corresponds to an installed distribution. Delete all subkeys inside Lxss (right-click → "Delete"). This does not uninstall your distributions from the system but clears old/corrupted entries.
5. Close the Registry Editor.
6. In PowerShell (as administrator), run:

   wsl --shutdown
   

   Then try launching your distribution again. WSL will automatically recreate the necessary registry entries.

Method 5: Temporarily Disable Antivirus and Firewall

Some third-party antiviruses (Kaspersky, Avast, McAfee, etc.) or Windows Firewall in strict mode can mistakenly block the WSL service or the creation of a virtual network adapter.

1. Temporarily disable your antivirus (usually via the system tray icon → "Disable protection for 10-15 minutes"). Do not disable it permanently!
2. Try launching WSL. If the error disappears, add exceptions for WSL folders in your antivirus settings:
   • C:\Windows\System32\wsl.exe
   • C:\Users\<YourName>\AppData\Local\Packages\
   • The folder containing virtual disks (by default %USERPROFILE%\AppData\Local\Docker\wsl\ or C:\Users\<User>\AppData\Local\Microsoft\WindowsApps\).
3. Also check Windows Defender Firewall with Advanced Security. Ensure there are no rules blocking wsl.exe or vmcompute.exe. Temporary disablement for diagnosis: open "Windows Defender Firewall" → "Turn Windows Defender Firewall on or off" → disable for private and public networks. Remember to re-enable it afterward!

Prevention

To minimize the risk of the WSL Service Failed error in the future:

• Do not disable Hyper-V and "Windows Subsystem for Linux" features in "Windows Features" if you use WSL 2.
• Do not manually delete or move distribution files from the AppData\Local\Packages\ folder. Use wsl --export and wsl --import commands for migration.
• Regularly update WSL and Windows. Run wsl --update monthly and install Windows updates, especially those related to the "Virtual Machine Platform".
• Back up important data from WSL to the Windows side (to the \\wsl$\<Distro>\home\<user>\ folder) before major Windows updates or changing distributions.
• If using WSL 2, monitor free space on your system drive (C:). Virtual .vhdx disks can grow. Clean up space inside the distribution (sudo apt clean, sudo du -sh /*) or shrink the disk size via wsl --shrink.