-
Notifications
You must be signed in to change notification settings - Fork 854
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error after update to 2.0.9.0, even reinstall fails: Error code: Wsl/CallMsi/E_ABORT #10764
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! Closed similar issues:
You can give me feedback by thumbs upping or thumbs downing this comment. |
Same issue. Even more frustrating that I didn't request any update from microsoft. Everything was working fine until I rebooted my PC. |
Also having the same issue. Completed a windows update overnight and this morning had some other issues so decided to do a complete uninstall and reinstall of WSL and Ubuntu and now my WSL is stuck in this state. Any command such as |
For me it went from the message above to |
Same issue here. C:\Users\lam>wsl Even after unistalling and reinstalling it completely, I got stuck at the same state. |
Same issue here. |
Have the same problem, nothing I've tried so far has been able to fix this. Restarted my computer a couple hours ago and have since not been able to open wsl and continue working. Says I have version 2.0.9.0. Every time I try to use any wsl command, I get the same message for the past couple hours: "WSL is finishing an upgrade... Update failed (exit code: 1603). Error code: Wsl/CallMsi/E_ABORT". I literally cannot get any work done and I have an urgent deadline. :(((((( |
I thought I will attach my logs to the issue as there is no logs available for this one: WslLogs-2023-11-16_23-23-55.zip Also I've spotted that WslInstaller service can be manually started in task manager but the WslService doesn't react to start command I hope this gets resolved asap and will be given the highest priority as it blocks all of my job duties. |
I got it working on my side. The problem was resolved when I deleted the WslService from registry. What I did to fix WSL:
I didn't try with 2.0.9 nor any other version of WSL for now. I'm happy it works in the end. Hope it will fix the issue for you as well. |
Thank you . I fixed it |
For me, "WslService" didn't even exist. I've disabled WSL from "Turn Windows Features on or off", rebooted, enabled it, rebooted, installed WSL 2.0.8 > wsl worked. |
Thanks. The way @MikolajGolowski fixed it works for me too. |
I have done this procedure and that fixed the problem to me. However, I lost all my data, but that's probably because I have been going through lots of different procedures, like reinstalling and messing with Windows registries to try to solve it. That on my own, I know. But I have decided to go back and use Linux VMs instead of WSL. |
When I try to downgrade, I get this error: I have tried doing so as administrator using the command prompt terminal, but I still get the same error. There are no other users on my computer other than myself. |
This worked for me, I was not able to downgrade install 2.0.8.0, but 2.0.5.0 worked perfectly. This method even kept my locally saved changes I hadn't yet pushed. YOU SAVED MY WORK, THANK YOU!!!!! |
I also deleted Docker, Ubuntu, etc... Before you do the same save your virtualdisk, for ubuntu it's somewhere under AppData/Local/packages/cano... {company of ubuntu} .... and so on. ext4.vhdx. I tried to open it with the 'Bereitstellen' (provide, make available, something like this in english. this feature can also be used to create a virtual diskdrive from an *.img Diskimage-File), but that doesn't work. |
I'm having a similar problem; I've noticed that no matter what command I enter, it always returns wsl update failed. So I deleted the key file ext4.vhdx and then I found that the commands worked, but of course wsl is now faulty. So |
Then I ran the following command: |
I run WSL on a Windows 10 system and had the same issue! It worked for me to remove the app 'Windows Subsystem for Linux' from 'Settings > Apps' and install these updates from the Microsoft homepage. |
@Molenfeuer's solution worked for me also (Windows 10 Pro 22H2).
|
Same issue, can only run wsl with admin rights, everything else fails. Have to manually run it on admin. |
Thank you very much, I was thinking re-install my Windows 11, but this solution works for me. |
thanks! actually, my problem was solved already after i delete the WslService on regedit and restart it |
Encountered the same issue, and after trying various solutions without success, I finally found a workaround that works, assuming you have admin access:
|
THANK YOU!!!! It worked here!! |
After updating to the 2.0.11 pre-release, wsl started working again for me. |
Edit: Apparently because I'd enabled "Use TLS 1.3 (experimental)" in Internet Options.
|
This worked for me as well, But I lost my projects because I couldn't retrieve my old files |
After uninstalling wsl and deactivating wsl in windows features, it started working again for me. Settings > Apps > Optional features > More windows features
|
Thank you so much! I solved my issue by doing step 1 through 4! I really appreciate your help! |
Fixed in 2.0.11 |
Thanks a lot!!! |
How to disable WSL from "Turn Windows Features on or off"? |
Thanks! I wasn't able to see WslService in the registry but had a WslInstaller folder there. I didn't want to mess anything up so I tried this and it worked for me. I was able to run the |
It works for me! You really saved my life! |
same issue here WSL was never installed before and I am running windows 10.0.19045.3636. this issue is not fixed. |
IDK how you figured it out, but you are a f***in CHAD! Thanks and well done! Even the MS devs couldn't figure it out. Can confirm that the latest version works fine! |
Thank you. It really solved the problem for me |
you should try wsl --update --web-download and then wsl --install |
Same process worked for me, but I used version 2.0.11. I didn't lose any data. The Linux distro, in this case Ubuntu, worked like a charm again. |
Just adding my 2 cents here, had the same issue, but for me |
THANK YOU! Been headbutting all morning, you saved my day! |
It not works for me, I got the error by wsl --update, and I went into the regedit but found no WslService. 😥 In fact, the problem bg for me is, I want to reload my vhdx file with my old ubuntu system, so I create a reg of that file, and wsl detect it. But after I use wslconfig to transfer the default version to my vhdx file and run wsl, the system requests me to update wsl and says "core" needs to be updated, so I run wsl --update and got the error code, and with no wslservice. What should I do to load my system successfully? |
Windows restart fixed the issue. |
press
|
thank youuuuuuu @bence42 😭 |
Windows Version
Microsoft Windows [Version 10.0.19044.3693]
WSL Version
2.0.9.0
Are you using WSL 1 or WSL 2?
Kernel Version
No response
Distro Version
No response
Other Software
No response
Repro Steps
WSL didn't start today, The Microsoft Store told me that an update was installed.
I tried repair, reset and deinstal + Windows Restart + new Install
Expected Behavior
WSL starts and works as it did for month.
Actual Behavior
WSL does not start,
If I start the Powershell as Admin and use wsl --status it tells me that WSL is finishing an upgrade. After a short time (~half second) it fails with (Exitcode: 1603).
Error code: Wsl/CallMsi/E_ABORT
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: