WSL: Cannot install WSL on latest Windows Insider dev build
Windows Version
Microsoft Windows [Version 10.0.26080.1400]
WSL Version
2.1.5
Are you using WSL 1 or WSL 2?
- WSL 2
- WSL 1
Kernel Version
N/A
Distro Version
N/A
Other Software
Docker Desktop (Docker version 25.0.3, build 4debf41)
Repro Steps
I recently updated to the latest Windows Insider dev build, which is Windows 11 Insider Preview 10.0.26080.1201 (ge_release_upr). After updating Windows, I ran wsl --update, which caused the “Catastrophic failure” error and completely broke my WSL setup. It seems like the failed update uninstalled WSL and I can’t reinstall it.
Expected Behavior
I expected WSL to install successfully.
Actual Behavior
Running any WSL command produces the following output.
Windows Subsystem for Linux must be updated to the latest version to proceed. You can update by running 'wsl.exe --update'.
For more information please visit https://aka.ms/wslinstall
Press any key to install Windows Subsystem for Linux.
Press CTRL-C or close this window to cancel.
This prompt will time out in 60 seconds.
Operation aborted
Running wsl --update or wsl --install produces the following output.
Downloading: Windows Subsystem for Linux 2.1.5
Installing: Windows Subsystem for Linux 2.1.5
Catastrophic failure
Manually downloading the MSI from the GitHub releases shows these error messages.
Diagnostic Logs
Logs from running wsl --install: WslLogs-2024-03-19_19-06-02.zip
WSL install logs from temp folder: wsl-install-logs.txt and MSI65cb2.LOG
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 2
- Comments: 26 (1 by maintainers)
After some messing around, I found a workaround for this issue. I installed the old v1.2.5 version using the MSIX bundle, and then I updated through several in-between releases (using the MSIX bundles only, I don’t remember the exact order) until I got to the latest v2.1.5. Everything seems to be working fine now. Attempting to reinstall v2.1.5 through the MSI instead of the MSIX bundle still breaks everything for me, though, so it does not look like the core issue here is resolved.
@MatthewL246 - Thank you for the tip of installing an older version of WSL first.
I was also getting the “catastrophic failure” error and took about 2 hours of trial and error with many of the suggestions on the Internet, until I found your workaround. It worked for me. Thanks!
Scott
I’m getting the same error code 0x80073CFB for updates for WSL via the store (I’m on the latest stable 11 update). I think it started occurring after I manually updated via
wsl --updaterecently. I can’t afford to uninstall my environment so would like to know if there are alternative workarounds or fixesSome additional notes:
msiexec /uninstall wsl.2.1.5.0.x64.msi, which fully uninstalls WSL.wsl.2.1.5.0.x64.msi, it fails to install. The installer createsC:\Program Files\WSLandD:\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_2.1.5.0_x64__8wekyb3d8bbwe\. After clicking the OK button on the error dialog, it deletesC:\Program Files\WSLbut the WindowsApps directory sticks around.Microsoft.WSL_2.1.5.0_x64_ARM64.msixbundle, it shows the error “App installation failed with error message: Deployment of package MicrosoftCorporationII.WindowsSubsystemForLinux_2.1.5.0_x64__8wekyb3d8bbwe was blocked because the provided package has the same identity as an already-installed package but the contents are different. Increment the version number of the package to be installed, or remove the old package for every user on the system before installing this package. (0x80073cfb).” Presumably, this is because of the failed installation in step 2.D:\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_2.1.5.0_x64__8wekyb3d8bbwe\as TrustedInstaller to revert this failed installation.Microsoft.WSL_2.1.5.0_x64_ARM64.msixbundleand it installs successfully, creatingD:\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_2.1.5.0_x64__8wekyb3d8bbwe\(but nothing in Program Files). However, running WSL shows the error “Class not registered. Error code: Wsl/CallMsi/Install/REGDB_E_CLASSNOTREG”.Remove-AppxPackage -AllUsers MicrosoftCorporationII.WindowsSubsystemForLinux_2.1.5.0_x64__8wekyb3d8bbwe.D:\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_2.1.5.0_x64__8wekyb3d8bbwe\andC:\Program Files\WSL.wsl.2.1.5.0.x64.msidoes nothing.Remove-AppxPackage -AllUsers MicrosoftCorporationII.WindowsSubsystemForLinux_2.1.5.0_x64__8wekyb3d8bbwedeletesD:\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_2.1.5.0_x64__8wekyb3d8bbwe\, butC:\Program Files\WSLstill remains. WSL continues working correctly.All of these possible broken states are really confusing me, but I hope this helps.
I had the same issue, and nothing worked. However, running the following command fixed it:
That lines up with what I’ve observed, though I’d be reluctant to delete those directories without using the inbox commands such as
(add|remove)-appxpackage. I’ve ended up with sadness a few times when I do that.Untill we ship a fix I think you’ll want to stick to using this as a workaround:
Unfortunately yes, they take different code paths under the hood. Even if I explained it, it wouldn’t make sense to a rational human.
Thank-you for the logs, much appreciated. I assume you also have vanilla settings for this?