WSL problems in Windows 11 usually come from one of four places: a disabled Windows feature, unavailable hardware virtualization, an outdated WSL package, or a damaged Linux distribution. Start by identifying which layer is failing instead of repeatedly running wsl –install.
Open PowerShell or Command Prompt and run:
wsl –status
wsl –version
wsl –list –verbose
These commands show the WSL configuration, installed WSL component versions, distributions, running state, and whether each distribution uses WSL 1 or WSL 2. The fixes below target the most common Windows 11 failures without immediately deleting your Linux files.
1. Update and restart WSL
The Windows WSL component and the packages inside Ubuntu, Debian, or another distribution are separate. Update WSL from Windows first:
wsl –update
wsl –shutdown
wsl –shutdown stops all running distributions and the WSL 2 lightweight virtual machine. Start your distribution again from the Start menu or with:
#1 Best Overall
wsl
If Microsoft Store access is blocked by your organization or network, download the WSL update directly from GitHub:
wsl –update –web-download
On current Windows 11 installations, this is normally preferable to installing the old standalone Linux kernel MSI. That legacy installer is mainly relevant to older, manual WSL installations.
2. Re-enable the Windows features WSL needs
WSL 1 requires Windows Subsystem for Linux. WSL 2 requires that feature plus Virtual Machine Platform. You do not generally need to enable the complete Hyper-V role for ordinary WSL 2 use.
Using Windows Features
- Press Windows + R, type optionalfeatures, and press Enter.
- Enable Windows Subsystem for Linux.
- Enable Virtual Machine Platform if you use WSL 2.
- Select OK and restart Windows.
Using elevated PowerShell
Right-click Start, select Terminal (Admin) or PowerShell (Admin), and run:
Free tools Windows power users keep installed
One-click scans. No signup required.
dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
Restart the computer before testing WSL again:
Restart-Computer
After restarting, check the distribution mode:
wsl -l -v
3. Fix virtualization errors, especially 0x80370102
Error 0x80370102 means that the WSL 2 virtual machine could not start because a required virtualization feature is unavailable.
Check these items in order:
- Virtual Machine Platform: confirm it is enabled using optionalfeatures or the DISM command above.
- UEFI/BIOS virtualization: reboot into your firmware settings and enable the option named Intel VT-x, Intel Virtualization Technology, AMD-V, SVM, or a similar setting.
- CPU capability: WSL 2 requires Second Level Address Translation (SLAT). Very old processors, including Intel Core 2 Duo models, cannot run WSL 2.
- Windows hypervisor startup: check whether Windows is configured to start its hypervisor.
Run this command in an elevated PowerShell or Command Prompt:
bcdedit /enum | findstr -i hypervisorlaunchtype
If it reports hypervisorlaunchtype Off, enable it:
bcdedit /set hypervisorlaunchtype Auto
Restart Windows and try the distribution again.
If Windows 11 is itself a virtual machine
WSL 2 needs nested virtualization when Windows is running inside another virtual machine. On a Hyper-V host, run:
Recommended Free Tools
Set-VMProcessor -VMName <VMName> -ExposeVirtualizationExtensions $true
Replace <VMName> with the name of the guest VM. The host must expose virtualization extensions to the Windows 11 guest. Azure virtual machines using Trusted Launch do not support the required nested-virtualization configuration for this scenario; Trusted Launch must be disabled.
Older third-party hypervisors can also interfere. VMware 15.5.5 or later and VirtualBox 6 or later can support Hyper-V-based configurations. Update older versions or temporarily close them while testing WSL.
4. Fix error 0x8007019e
This message usually appears as:
WslRegisterDistribution failed with error: 0x8007019e
It means the Windows Subsystem for Linux optional component is disabled.
- Open optionalfeatures from the Run dialog.
- Enable Windows Subsystem for Linux.
- Select OK and restart Windows.
Alternatively, run this command as administrator:
dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
Do not skip the restart. The feature may be installed but not fully active until Windows has rebooted.
5. Fix 0x80070003 during installation
For WSL installation error 0x80070003, Microsoft identifies the system drive as the important check. WSL normally runs from the Windows system drive, usually C:.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsOn Windows 11, open:
Settings → System → Storage → Advanced storage settings → Where new content is saved
Set the location for new apps to the system drive, then try the installation again. Avoid assuming that every distribution must permanently live in the root of C:; current WSL commands support a distribution location option. The system-drive setting is specifically relevant when diagnosing this installation error.
6. When wsl –install shows help instead of installing
The one-command installation behavior applies when WSL is not installed at all. If WSL is already present, wsl –install may display its help text instead.
List the distributions available for installation:
wsl –list –online
Then install a specific one:
wsl –install -d Debian
Replace Debian with a distribution name shown by the online list. If installation remains at 0.0%, bypass Store delivery:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
wsl –install –web-download -d Debian
After installation, the first launch asks you to create a Linux username and password. The Linux password is separate from your Windows password.
7. Repair the distribution and select WSL 2
First check what is installed:
wsl –list –verbose
For a distribution that is using WSL 1, set WSL 2 as the default for future installations:
wsl –set-default-version 2
Convert an existing distribution:
wsl –set-version Ubuntu 2
Replace Ubuntu with the exact name returned by wsl -l -v. Conversion requires Windows build 18362 or later, the Windows Subsystem for Linux feature, a restart after enabling it, and a working WSL 2 component. On current installations, update that component with:
wsl –update
To choose which distribution opens when you run only wsl:
wsl –set-default Ubuntu
Do not use unregister as a routine repair command:
wsl –unregister Ubuntu
This permanently deletes the distribution’s Linux filesystem, installed applications, settings, and files. Use it only after backing up anything important and only when you are prepared to reinstall the distribution.
8. Recover from failures after Windows Update or System Restore
Error 0x80040154 after a Windows update
Error 0x80040154 can occur when the Windows Subsystem for Linux feature becomes disabled during an update. Re-enable it through:
Control Panel → Programs and Features → Turn Windows features on or off → Windows Subsystem for Linux
Restart Windows, then run:
wsl –status
wsl -l -v
WSL stopped working after System Restore
Microsoft documents a more specific recovery sequence for this case:
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →- Delete the following task folder:
%SystemRoot%\System32\Tasks\Microsoft\Windows\Windows Subsystem for Linux
- Ensure the Windows Subsystem for Linux optional feature is enabled.
- Restart Windows.
- If the legacy distribution is still unusable, unregister it:
wsl –unregister <DistroName>
- Reinstall the Linux distribution from the Microsoft Store.
Do not delete that task folder if the optional feature is already fully installed and working; this procedure is intended for the documented System Restore failure scenario.
Rank #4
- Used Book in Good Condition
9. Fix error 0x80040306
Error 0x80040306 is associated with the unsupported legacy console.
- Open cmd.exe.
- Right-click the title bar and select Properties.
- Clear Use legacy console.
- Select OK, close Command Prompt, and launch WSL again.
10. Fix WSL networking problems
If WSL starts but has no network connection, first distinguish a general Windows network failure from a WSL-specific one. If Windows has internet access and the problem affects a work or enterprise machine, check for a stale virtual network adapter:
- Open Device Manager.
- Select View → Show hidden devices.
- Expand Network adapters.
- Right-click the ghosted network adapter.
- Select Uninstall Device.
Restart Windows and test WSL. Firewall and endpoint-security software can also block WSL networking. If the problem began after installing security software, temporarily test with that software disabled only according to your organization’s policy.
11. Update Linux packages inside WSL
A successful WSL launch does not mean that the Linux distribution is up to date. Run these commands inside Ubuntu or Debian:
sudo apt-get update
sudo apt-get upgrade
Run this Windows command separately to update WSL itself:
wsl.exe –update
Some Linux packages expect services or kernel features that WSL does not support in the same way as a conventional Linux installation. Microsoft specifically notes that udev can cause errors during apt-get upgrade. A package-upgrade error is therefore not automatically evidence that the Windows WSL installation is broken.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →12. Fix SSH private-key permission errors
If an SSH key is stored on a Windows-mounted path, SSH may see permissions that are too broad and show an error such as:
Permissions 0777 for ‘/home/user/.ssh/private-key.pem’ are too open.
For a user with UID and GID 1000, edit or create /etc/wsl.conf inside the distribution:
[automount]
enabled = true
options = metadata,uid=1000,gid=1000,umask=0022
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Best Value
Then leave Linux and restart WSL from Windows:
exit
wsl –shutdown
Open the distribution again and retry SSH. Keep sensitive keys in the Linux filesystem where possible; it avoids many Windows-mount permission surprises.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.13. Repair Windows system files for 0x8000FFFF
Error 0x8000FFFF is an unexpected or “catastrophic” failure that can occur while installing or using a distribution. Run the less destructive WSL reset first:
wsl –update
wsl –shutdown
If the error remains, open an elevated Command Prompt or PowerShell and run:
SFC /SCANNOW
DISM /Online /Cleanup-Image /RestoreHealth
Recommended Free Tools
SFC checks and repairs missing or corrupted Windows system files. DISM repairs the Windows component store used by Windows servicing. Restart after both commands complete, then test WSL again.
Quick diagnosis table
| Symptom or error | Most likely action |
|---|---|
| 0x8007019e | Enable Windows Subsystem for Linux and restart. |
| 0x80370102 | Enable Virtual Machine Platform, UEFI virtualization, and the Windows hypervisor. |
| 0x80070003 | Set new app storage to the system drive in Windows 11 Settings. |
| 0x80040154 | Re-enable Windows Subsystem for Linux after a Windows update. |
| 0x80040306 | Disable Use legacy console in Command Prompt properties. |
| 0x8000FFFF | Update WSL, shut it down, then run SFC and DISM. |
| wsl –install shows help | Install a named distribution with wsl –install -d <Name>. |
| SSH says permissions are 0777 | Configure metadata and a restrictive umask in /etc/wsl.conf. |
Windows 11 and WSL 2 requirements
| Requirement | Details |
|---|---|
| Windows version | WSL 2 requires Windows 11 or Windows 10 version 1903, build 18362 or later. |
| One-command install | wsl –install requires Windows 10 version 2004, build 19041 or later, or Windows 11. |
| Windows features | Windows Subsystem for Linux and Virtual Machine Platform. |
| Processor | SLAT support is required for WSL 2. |
| Firmware | CPU virtualization must be enabled in UEFI/BIOS. |
On older Windows builds, use Microsoft’s manual-install procedure rather than expecting wsl –install to work.
FAQ
Why does WSL stop working after I enable the features?
Restart Windows after enabling Windows Subsystem for Linux or Virtual Machine Platform. These features may not become active until the reboot is complete.
Does WSL 2 require the full Hyper-V feature?
No. Ordinary WSL 2 use requires Virtual Machine Platform, Windows Subsystem for Linux, hardware virtualization, and a functioning Windows hypervisor. The complete Hyper-V role is not generally required.
Free tools Windows power users keep installed
One-click scans. No signup required.
Will wsl –unregister repair my distribution?
No. It removes the distribution and permanently deletes its Linux filesystem. Back up your files first and use it only when you intend to reinstall that distribution.
How do I tell whether Ubuntu is using WSL 1 or WSL 2?
Run wsl –list –verbose or wsl -l -v. The VERSION column reports 1 or 2.
Why does WSL have no internet while Windows does?
A stale hidden network adapter, firewall, or endpoint-security software can block WSL networking. Show hidden devices in Device Manager, inspect Network adapters, and remove a ghosted adapter if appropriate.
The Bottom Line
Use wsl –status, wsl –version, and wsl -l -v before changing anything. Then update WSL, restart it with wsl –shutdown, verify the two Windows features, and check UEFI virtualization if WSL 2 cannot start. Match specific error codes to their documented fixes, and treat wsl –unregister as a destructive reinstall step rather than a general repair command.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
