Fix WSL 2 Boot Failure After Windows Install

If you cannot boot into Linux via WSL after installing or updating Windows, the fix is usually to re-enable the Windows Hypervisor Platform and Virtual Machine Platform features, then update the WSL kernel. This article gives you a step-by-step repair path that works for most WSL 2 boot failures, plus the background you need to avoid repeating the problem.

Why WSL 2 Stops Booting After a Windows Update

WSL 2 runs Linux in a lightweight virtual machine using Microsoft’s Hyper-V hypervisor. When Windows updates, it can reset optional features, disable the hypervisor, or replace the WSL kernel with an incompatible version. The most common symptom is an error like “WSL 2 requires an update to its kernel component” or “The virtual machine could not be started because the hypervisor is not running.” In other cases, the wsl command works but the distribution never shows a prompt.

Another frequent cause is having third-party virtualization software (VirtualBox, VMware) that conflicts with Hyper-V, or having the Windows Hypervisor Platform disabled after a feature update. Windows 11 and recent Windows 10 builds both rely on the same set of virtualization features, so the repair steps are nearly identical.

Prerequisites: What You Need Before Starting

• Administrator access on the Windows machine (you’ll open PowerShell as admin).
• An internet connection to download the WSL kernel update if needed.
• At least 4 GB of RAM and a 64-bit CPU with virtualization enabled in BIOS (most modern PCs already have it).
• Windows 10 version 2004 or higher, or Windows 11. Older versions may need manual installation of the WSL 2 kernel.

If you are on Windows Server, the steps are the same but you may need to install the Hyper-V role separately. For most home users, the built-in Windows features are enough.

Step-by-Step Repair for WSL 2 Boot Failure

Follow these steps in order. Stop after each one and test with wsl -d <distro> (e.g., wsl -d Ubuntu) to see if the problem is resolved.

1. Open PowerShell as Administrator. Press Win, type PowerShell, right-click it and choose “Run as administrator”.
2. Enable the required Windows features. Run these two commands:
   dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
   If you are on Windows 11, also enable the Windows Hypervisor Platform:
   dism.exe /online /enable-feature /featurename:HypervisorPlatform /all /norestart
3. Restart Windows. A reboot is required even if the commands say “no restart needed”.
4. Set WSL 2 as the default version. After reboot, open PowerShell again (admin) and run:
   wsl --set-default-version 2
5. Update the WSL kernel. Run wsl --update (or wsl --update --web-download if the built-in update fails). This downloads the latest kernel from Microsoft. If you get an error, download the MSI package from the Microsoft WSL documentation page and run it manually.
6. Restart the LxssManager service (if still failing). In the same admin PowerShell, run:
   net stop LxssManager then net start LxssManager. This service manages WSL instances.
7. Check your distribution’s registration. Run wsl -l -v to list all distributions. If your distro shows as “Stopped” but won’t start, try wsl --terminate <distro> then start it again. If it shows as “None” under version, run wsl --set-version <distro> 2.
8. If nothing works, reset the WSL network stack. Run wsl --shutdown, then in admin PowerShell:
   netsh winsock reset and netsh int ip reset. Reboot and try again.

These steps cover about 90% of boot failures. The most common mistake is skipping the reboot after enabling features, or not running PowerShell as administrator.

Common Error Messages and What They Mean

• “WSL 2 requires an update to its kernel component” – The kernel is missing or outdated. Run wsl --update or install the MSI manually.
• “The virtual machine could not be started because a required feature is not installed” – VirtualMachinePlatform or HypervisorPlatform is disabled. Re-enable via DISM or Windows Features.
• “Error 0x80370102” – Virtualization is disabled in BIOS or Hyper-V is not running. Check BIOS settings (Intel VT-x or AMD-V) and ensure the Hyper-V hypervisor is running with bcdedit /set hypervisorlaunchtype auto (admin).
• “The service cannot be started” – LxssManager is stuck. Restart it as shown in step 6.
• “Windows cannot find ‘wsl.exe'” – The WSL feature is not fully installed. Re-run the DISM commands.

If you see “Please enable the Virtual Machine Platform” even after enabling it, check that your CPU supports nested virtualization if you are running Windows inside a VM (like on a cloud server).

How to Prevent This From Happening Again

• Pause Windows updates during critical work, but don’t disable them permanently – security patches matter.
• After any major Windows feature update (like 23H2 or 24H2), run wsl --update proactively.
• If you use third-party virtualization software, make sure it is compatible with Hyper-V. Newer versions of VirtualBox and VMware support running alongside Hyper-V, but older ones may disable it.
• Keep your WSL distributions updated: sudo apt update && sudo apt upgrade inside each distro.
• Create a Windows restore point before installing large updates so you can roll back if something breaks.

When to Consider Reinstalling WSL Instead

If you’ve tried all the steps above and still get boot failures, a clean reinstall often fixes corrupted configuration files. Backup your Linux files first (they are stored in a virtual disk, usually at %LOCALAPPDATA%\Packages\...\LocalState\ext4.vhdx). Then run:

1. wsl --shutdown
2. wsl --unregister <distro> (this deletes the distribution and all its files – only do this if you have backups)
3. wsl --install -d Ubuntu (or your preferred distro)

This is a last resort, but it works when the issue is a corrupted WSL configuration rather than a Windows feature problem. You can also try wsl --import to restore from a backup if you have one.

Frequently Asked Questions

Why did WSL break after a Windows update?

Windows updates can reset optional features, replace the WSL kernel, or change hypervisor settings. The most common trigger is a feature update that reconfigures virtualization, but even monthly cumulative updates can occasionally disable the VirtualMachinePlatform feature. Re-enabling the features and updating the kernel usually fixes it.

Do I need to enable Hyper-V to use WSL 2?

WSL 2 uses the Hyper-V hypervisor, but you don’t need to install the full Hyper-V role. The VirtualMachinePlatform feature is sufficient. However, if you have Hyper-V disabled entirely, WSL 2 won’t work. You can check with systeminfo – if it says “A hypervisor has been detected,” Hyper-V is active.

Can I use WSL 2 without enabling Virtual Machine Platform?

No. WSL 2 requires the VirtualMachinePlatform feature. If you don’t want to enable it, you can switch to WSL 1 using wsl --set-version <distro> 1, but WSL 1 lacks full system call compatibility and is slower for many tasks.

Will reinstalling WSL delete my files?

Running wsl --unregister deletes the entire distribution, including all files inside it. But simply running wsl --update or re-enabling features does not touch your files. Always back up the ext4.vhdx file before unregistering.

How do I check if my CPU supports virtualization?

Open Task Manager (Ctrl+Shift+Esc), go to the Performance tab, and select CPU. Look for “Virtualization: Enabled” in the bottom right. If it says Disabled, you need to enable Intel VT-x or AMD-V in your BIOS/UEFI settings.

What if I get an error about the WSL service not starting?

This usually means the LxssManager service is stuck. Run net stop LxssManager and net start LxssManager as admin. If that fails, reboot and try again. If it still fails, check the Windows Event Viewer for hypervisor-related errors.

Related

• Fix App Blocked by System Administrator in Windows
• Outlook Remove Stuck Email: 7 Fixes That Work
• Fix Graphics Card Not Detected in Windows 11