WSL: The specified service does not exist as an installed service. Error code: Wsl/0x80070424 [process exited with code 4294967295 (0xffffffff)]
Windows Version
Microsoft Windows [Version 10.0.22621.2715]
WSL Version
2.0.9.0
Are you using WSL 1 or WSL 2?
- WSL 2
- WSL 1
Kernel Version
No response
Distro Version
No response
Other Software
No response
Repro Steps
WSL is now unable to launch following a Sindows update. Attempted to diagnose this issue by following the comments in #10755 (Disable hyper-v, enable virtual machine, reinstall WSL) but still doesn’t work.
C:\Users\omart>wsl.exe
Expected Behavior
WSL to launch
Actual Behavior
Errored out with this:
The specified service does not exist as an installed service.
Error code: Wsl/0x80070424
Diagnostic Logs
No response
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 19
Ok. I finally fixed WSL. I haven’t re-imported my files, but what I had to do was a complete re-installation of WSL. These were the steps I took:
wsl -land make sure it runs without the “service does not exist” errorand now it works. I also tried using #10764 as previously mentioned, but I wasn’t able to find that registry entry so skipped the steps. (Also note that I’m too afraid to update to 2.0.9 in-case anything bricks 😬) Additionally, I haven’t imported my
ext4.vhxdfile yet, but will soon. Thanks @bousch 😃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:
You can give me feedback by thumbs upping or thumbs downing this comment.
I also had this exact situation where every wsl command showed the help text. I think I then executed “wsl --update --inbox” as Administrator in a cmd.exe Command prompt. It would not work from Powershell as Administrator. Or it was the other way around. Sorry about that, I have tried so many combinations that I can’t remember exactly. Also check some of the other issue threads, some issues of the last couple of days are related/similar. For instance https://github.com/microsoft/WSL/issues/10782 and https://github.com/microsoft/WSL/issues/10767. I was able to fix it on both my laptops with slightly different steps.
On Sat, 18 Nov 2023, 18:25 Omar Tsai, @.***> wrote:
I now have WSL working also on my Windows Home laptop. I did uninstall wsl and re-installed from MSI but this resulted in the same error as before. I did notice that there were two entries in “Apps & Features”; one of 459 MB which says 2.0.9.0 and a smaller one (8 KB or 8MB) without version but with advanced options. I deleted this one. If I remember correctly the wsl command worked after this. I did run “wsl --update --inbox” and used “wsl --install -d Distroname” to reinstall the distro’s I had before. Then I ran “wsl --shutdown” and replaced the .vhxd files in %localappdata% with my backups. Now wsl seems to run fine. The WSL entries in my “Apps & Features” list are:
