WSL --install fails with "Error: 0x80070424 The specified service does not exist as an installed service"

[markom80]

Windows Version

Microsoft Windows [Version 10.0.22631.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

Ubuntu

Other Software

No response

Repro Steps

Installing subsystem distro fails if i run wsl --install Ubuntu

Already tried following:
-Remove and reinstall Hyper-V and Subsystem

Expected Behavior

Actual Behavior

C:\Users\user>wsl --install ubuntu
Ubuntu on jo asennettu.
Käynnistetään Ubuntu...
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80070424
Error: 0x80070424 The specified service does not exist as an installed service.

Diagnostic Logs

WslLogs-2023-11-15_08-54-49.zip

[github-actions]

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:

• WSL --install fails with unknown error code (0x80240066) (#9385), similarity score: 0.84
• install WSL distribution with error code 0x80070001 (#6172), similarity score: 0.84

Closed similar issues:

• wsl --install fails with Error Code: 0x80245006 (#9480), similarity score: 0.86
• WSL2 Error: 0x80070420 An instance of the service is already running. (#8520), similarity score: 0.85
• WSL installing error with error code 0x80073701 (#3675), similarity score: 0.85
• wsl install failed with error 0x80240438 (#10226), similarity score: 0.84
• Error code: Wsl/Service/CreateInstance/0x80040326 when starting WSL Distro (#9867), similarity score: 0.84
• WSL Instal error 0x80080005 (#5700), similarity score: 0.84
• wsl install error for 0x80072eff, 0x80072ee7 (#8784), similarity score: 0.83
• Error code: Wsl/Service/CreateInstance/0x80040326 when starting WSL Distro (again) (#10232), similarity score: 0.83

You can give me feedback by thumbs upping or thumbs downing this comment.

[TheJCAB]

It's not just a problem installing WSL, the same error is happening when launching already-installed WSL after Windows Update. See #10755 (someone already closed it on account of workarounds, which might help here too, but the issue remains).

[markom80]

Re-Enabling Virtual Machine Platform solved my issue. #10760

[kiksy]

I've had this issue for a few days. None of the other fixes such as disabling and reenabled WSL services in Windows Features worked for me. I attempted to completly uninstall WSL and noticed I had 2 versions listed in the installed programs list. 1 version would uninstall fine, the other (which install date matched the day I started seeing this issue) would not unsintall with the message 'installation package could not be opened'. I used a 3rd party uninstall program to remove all registry entries and associated files. Rebooted, then installed the pre-release 2.0.11 : https://github.com/microsoft/WSL/releases/tag/2.0.11 . It now works and no data was lost as I didnt uninstall any distros.

[mariliamatosbiz]

Estou com esse erro

wsl --install ubuntu
O serviço especificado não existe como serviço instalado.
Error code: Wsl/CallMsi/0x80070424

Podem me ajudar?

[akartikus]

I had the same issue
Resolved with https://github.com/microsoft/WSL/releases/tag/2.0.11

[hakakou]

In my case, I needed to enable the following from Programs and Features -> Turn Windows Feature on or off:

• Virtual Machine Platform
• Windows Subsystem for Linux

[fgsoftware1]

go to Applications select windows linux subsystem app, advanced options, repair

[sansmoraxz]

go to Applications select windows linux subsystem app, advanced options, repair

Doesn't work in windows 10

[fgsoftware1]

go to Applications select windows linux subsystem app, advanced options, repair

Doesn't work in windows 10

i'm using windows 10 :)

[caminashell]

For me, the cause was Comodo Auto-Containment.

To explain . . .

I went through a process of deduction to find out what the cause was for my terminal not running as expected. I tried to stop/start the virtualization platform - negative. Tried netsh winsock reset - negative. I even went as far as checking my UEFI SVM setting, which was fine.

Then I thought back to what I had changed since I last ran the container. The only things I could think of were Malwarebytes, and Comodo Firewall (which comes with some fancy features).

I quit Malwarebytes - negative. I turned off all Comodo features - SUCCESS! Then narrowed it down to Auto-containment, so whilst it was off, I added the terminal process to an ignore rule, and now all is fine.

[CurtisDyer]

When I came across the issue, I was running an up-to-date Windows 11.

I already had the Hyper-V features enabled (reasons unrelated to WSL) and Windows Subsystem for Linux enabled. The fix for me was simple; I had to enable the Virtual Machine Platform Windows feature. No restart was required after enabling this feature. Lastly, I ran wsl --shutdown before trying to install a distro.

[brunoelly]

I had the same issue Resolved with https://github.com/microsoft/WSL/releases/tag/2.0.11

Finally it worked! Thanks for sharing!