wsl --install fails on freshly installed Windows 11 and wsl --update breaks WSL #11124
Comments
|
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! Open similar issues:
Closed similar issues:
|
|
Can you please collect WSL logs of this issue? /logs And also can you try installing the latest WSL release by downloading the msi from the 'releases' page: https://github.com/microsoft/WSL/releases and manually installing it? |
|
I collected as you asked logs during the various steps. I include short comments on the state of the system before each log. not installed: windows subsystem for linux, VirtualMachinePlatform, kernel after now wsl_update_x64 installed in addition subsequent wsl now works this logs were collected during update attempt (--update) which resulted in "catastrophic failure" (this is new) invocation of wsl --status after failed update attempt after Remove-AppxPackage -Package "MicrosoftCorporationII.WindowsSubsystemForLinux_2.0.14.0_x64__8wekyb3d8bbwe" rebooted and repeated wsl --update |
|
Not sure what is going on... As mentioned I back than had this problem on a freshly installed Windows 11 machine. To be more precise Windows 11 was actually reinstalled (reset this pc -> remove everything -> cloud). I also tried reinstalling from the recovery environment instead of the cloud download, but both resulted into the same problem. Installing WSL was not the only problem as I for instance I couldn't access Windows Defender from the Security Center. After finding no fix for the Windows Defender problem I downloaded the Microsoft Surface recover image which brought me back to Windows 10 and from there updated to Windows 11 followed by a final reset this PC and install from cloud step. Now I'm back where I was before in terms of Windows 11 version |
|
I am experiencing exact the same beahvior. I did a PC Reset via Cloud Install. After finishing Install I tried to configure wsl as mentioned above an came across the same error: Class not registered I tried the fast line by directly uninstalling the via
The interesting part here is that the system shows the "Updates are underway" Screen, and after an automatic reboot, the Updates (the freshly activated WSL components) are being rolled back leaving me with a broken WSL. Sidenote: I did another Clean-Install like above but with leaving WSL as is and instead activated Hyper-V Feature. After a reboot the same install and rollback behavior appears. My Device is a Surface Laptop Studio 2 (1.Gen). |
|
@aheinzel: Thank you for sharing all the logs. Based on the wsl --install logs it looks like the store is failing to download the WSL app. Can you try manually installing the latest MSI package and see if that solves your issue ? |
|
Just in case: On Windows 10, same issue, receipts from here did help: uininstall everything related to WSL (WSL, WSL Updates in Features And Apps) Reboot In admin PowerShell: Reboot wsl --update --inbox Reinstall RancherDesktop (my case) It finally works again. |
|
@OneBlue: Sorry I no longer have the machine available in this state. I know this is terrible timing, but that machine is my daily driver and I needed a working setup again. |
|
Maybe I can give some assistance. My System was left in the "Class not registered"-State. So I tried your approach by installing the msi-Package as provided. WSL now works for me: |
|
Ok thank you @aheinzel. I'll close this for now. Feel free to reopen if this happens again. |
|
I had the exact same issue as the author of this. As suggested by @OneBlue, I solved it by installing the MSI package of the WSL app published on GitHub, and everything is okay, but the lack of wsl commands remains. |
Windows Version
Microsoft Windows [Version 10.0.22631.3085]
WSL Version
not yet installed
Are you using WSL 1 or WSL 2?
Kernel Version
not yet installed
Distro Version
not yet installed
Other Software
I'm attempting to install WSL on a freshly installed copy of Windows 11. Please find details about the state of the OS below:
systeminfoGet-WindowsOptionalFeature -Online | Where {$_.State -eq "Enabled"} | Select FeatureNameGet-AppxPackage -AllUsers | Select Name, VersionNote: MicrosoftCorporationII.WindowsSubsystemForLinux was installed out of the box
Repro Steps
Attempt to use
wsl --installto install WSL or attempt to update an existing WSL installation withwsl --update.Expected Behavior
wsl --installshould enable WSL and install Ubuntu as linux environmentwsl --updateshould update the existing WSL installationActual Behavior
wsl --installerrors out with Error code: Wsl/CallMsi/REGDB_E_CLASSNOTREGwsl --updatebreaks the existing wsl installation causing all subsequent calls to wsl to error out with Error code: Wsl/CallMsi/REGDB_E_CLASSNOTREG and attempts to install a distribution result in WslRegisterDistribution failed with error: 0x8007019ePlease find more details below:
Attempts to install WSL
Error installing WSL from store (via
wsl --install)Attempt to install with
wsl --installerrors out (see above). Manually enabling Windows Subsystem for Linux optional component does not alter the outcome.Manual installation of kernel update package and VM feature
Following the instructions from Step 4 - Download the Linux kernel update package.
Installation is still not successful, but will work after removing the WSL windows store app.
Installation appears to be in principle successful, registration of VM fails as virtual machine platform has not been enabled yet.
Ubuntu appears to be up and running, it, however, fails to mount c: volume. After restarting wsl this error goes away.
At this point it appears wsl is working fine.
Updating to the latest version breaks WSL
Running
wsl --updateto update wsl to the latest version will break wsl.After updating wsl errors out again with Error code: Wsl/CallMsi/REGDB_E_CLASSNOTREG. After removing the WSL store app wsl will work again.
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: