sodcalculator

10 Tech How-To

WSL Not Working After Upgrading to Windows 11? Fixes

Guide 10-55330 · Updated · Step by step

If WSL stops working right after you upgrade to Windows 11, the usual culprits are a disabled Virtual Machine Platform, an outdated WSL kernel, or a leftover Windows 10 configuration. You can usually fix it in under ten minutes by re-enabling the required Windows features and updating WSL from the command line.

Why Upgrading Breaks WSL

Windows 11 ships with WSL 2 as the default architecture, but the upgrade process does not always carry over every component cleanly. The Windows Subsystem for Linux depends on two separate pieces: the optional Windows features (Virtual Machine Platform and Windows Subsystem for Linux) and the actual WSL kernel, which Microsoft now distributes as a separate MSI package or through the Microsoft Store. During a major upgrade, either piece can be left in a partially configured state. If you originally installed WSL on Windows 10 using the legacy wsl --set-version commands, the upgrade may preserve that older configuration, which then conflicts with Windows 11’s newer WSL service.

First: Check the Obvious

Before diving into reinstallations, run a quick diagnostic. Open PowerShell or Windows Terminal and type:

wsl --status
wsl --version

If wsl --version returns an error about a missing kernel or a malformed command, your WSL installation is outdated or corrupted. If wsl --status says the default version is 1, that is not necessarily a problem, but it explains why certain distributions behave differently. Also check whether the “Windows Subsystem for Linux” and “Virtual Machine Platform” features are still enabled:

  1. Press Windows + R, type optionalfeatures, and press Enter.
  2. Scroll to Virtual Machine Platform and Windows Subsystem for Linux.
  3. If either box is unchecked, check it, click OK, and restart.

Many post-upgrade failures are simply a feature that got disabled during the upgrade. Restarting after re-enabling is mandatory; the Hyper-V hypervisor will not load until the next boot.

Update WSL to the Latest Version

Windows 11 uses a modern WSL that is updated independently of the operating system. If you are still running the inbox version from Windows 10, it may lack the components needed for Windows 11. Open an elevated PowerShell (right-click Start, select “Terminal (Admin)”) and run:

wsl --update

This downloads and installs the latest WSL kernel and user-mode components from Microsoft. If the command fails, try the manual route:

  1. Go to the Microsoft Store and search for “Windows Subsystem for Linux”.
  2. Click Update or Get if it is not installed.
  3. After the store install, run wsl --version again to confirm.

If you get an error saying “WSL is not installed”, the store package may have been removed. In that case, install it from the store, then re-run wsl --update.

Re-register Your Distributions

Sometimes the WSL service works fine, but the individual Linux distributions fail to start because their registration points to a missing or incompatible filesystem. You can check what is installed with:

wsl --list --verbose

If a distribution shows as “Stopped” but will not start, or if it shows an error about a missing kernel, you can force a clean re-registration. This does not delete your files; it resets the WSL metadata for that distro. In PowerShell, run:

wsl --shutdown
wsl --unregister <DistroName>

Then reinstall the distribution from the Microsoft Store or by using wsl --install -d <DistroName>. Your home directory files are usually lost when you unregister, so back up anything important first. If you want to keep your files, copy the ext4.vhdx file from %LOCALAPPDATA%\Packages\...\LocalState before unregistering, then import it back with wsl --import.

Enable Virtualization in BIOS

WSL 2 requires hardware virtualization (Intel VT-x or AMD-V) to be enabled in the system firmware. Windows 11 does not automatically enable this if it was turned off in the BIOS. You can check whether virtualization is active by opening Task Manager, going to the Performance tab, and looking at the CPU section. If it says “Virtualization: Disabled”, you must:

  1. Restart your PC and press the key to enter BIOS/UEFI (usually Del, F2, or F10).
  2. Find the virtualization setting (often under Advanced, CPU Configuration, or Security).
  3. Enable it (sometimes called “Intel Virtualization Technology”, “SVM Mode”, or “VT-d”).
  4. Save and exit.

After booting back into Windows, run wsl --status again. If virtualization was the issue, WSL should now start normally. Note that some older CPUs or certain low-end laptops have this feature locked out; in that case you cannot run WSL 2 and must use WSL 1 instead.

Fall Back to WSL 1 (Temporary)

If you cannot enable virtualization (for example, on a work PC with locked BIOS), you can still use WSL 1. WSL 1 does not require a virtual machine; it translates Linux system calls directly on the Windows kernel. To convert a distribution to WSL 1, run:

wsl --set-version <DistroName> 1

This is a one-way conversion for that distro (you can convert back to version 2 later). WSL 1 is slower for heavy I/O tasks like package installs or git operations, but it works for most command-line tools. To make WSL 1 the default for new installs, run wsl --set-default-version 1. Keep in mind that WSL 1 does not support Docker Desktop’s WSL 2 backend or any tool that requires a real Linux kernel.

Common Error Messages and Their Fixes

  • “WSL 2 requires an update to its kernel component” – Run wsl --update from an elevated prompt, or download the kernel update MSI from Microsoft’s documentation page.
  • “The service WSL has not been started” – Open Services (services.msc), find “Windows Subsystem for Linux”, set its startup type to Automatic, and start it. If it will not start, run wsl --shutdown and reboot.
  • “The virtual machine could not be started because a required feature is not installed” – Re-enable Virtual Machine Platform in optionalfeatures and restart.
  • “Error code 0x80370102” – This usually means virtualization is disabled in BIOS or the hypervisor is not running. Check Task Manager and BIOS settings.
  • “The operation timed out” – Often a leftover WSL 1 network configuration. Run wsl --shutdown, then restart the LxssManager service in Services, or reboot.

Frequently Asked Questions

Will my Linux files be deleted if I update WSL?

No. Updating the WSL package (wsl --update) does not touch your distributions or their files. Unregistering a distribution does delete its filesystem, so only do that after backing up. The update only replaces the kernel and WSL service components.

Why does WSL work on Windows 10 but not on Windows 11?

Windows 11 expects the newer WSL architecture, which is delivered as a Store app or MSI. If you upgraded from Windows 10 with the older inbox WSL, the upgrade may not migrate the kernel correctly. Reinstalling the WSL package from the Store or running wsl --update usually resolves it.

Can I use WSL without Hyper-V?

WSL 2 requires the Hyper-V hypervisor, but you do not need to enable the full Hyper-V role. The “Virtual Machine Platform” feature is enough. If you cannot enable virtualization in BIOS, you can only use WSL 1, which does not need Hyper-V.

Is it safe to run wsl --unregister?

It is safe in the sense that it only removes the distribution’s registration and filesystem. It does not affect other distributions or your Windows system. However, it permanently deletes all files inside that distribution, so export your data first with wsl --export if you need to keep it.

Do I need to install a Linux distribution after upgrading?

Usually not. The upgrade should preserve existing distributions. If none appear in wsl --list, you may need to reinstall them from the Store, but your old files are likely still in the ext4.vhdx file and can be imported with wsl --import.

Why does WSL start but then immediately exit?

This often happens when the default user is misconfigured or the distribution’s init system fails. Try wsl --shutdown, then start the distribution with wsl -d <DistroName> -u root. If that works, your user account may be corrupted; you can reset it with wsl --manage <DistroName> --set-default-user <username>.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →