WSL Server execution failed Error code: Wsl/CallMsi/Install/0x80080005

[DefinetlyNotAI]

Windows Version

Microsoft Windows [Version 10.0.22631.4037]

WSL Version

FAILS: WITH SAME ERROR

Are you using WSL 1 or WSL 2?

• [ ] WSL 2
• [ ] WSL 1

Kernel Version

FAILS: WITH SAME ERROR

Distro Version

CANT ENTER

Other Software

The main WSL only

Repro Steps

I have once deleted wsl - A power outage occured in the middle of it deleting, and now its fully corrupted, neither installed or removed, doesnt show up in program and features.

Not sure how to reproduce, its only a rare occuronce so not a bug, BUT nothing works to fix it

Attempted to use dism and sfc, both returned no errors,

Expected Behavior

To at least operate or open,

Actual Behavior

Anything related to wsl just fails entirely and does not in the slightest work or operate, disabling and re-enabling the feature was tried, IT used to work but not anymore (so required window and bios settings are fine) All other applications are operational, only wsl fails, no matter how or where it keeps failing, Also when i view it through the file manager, it shows its a empty folder, when i right click it to select properties i get the error shown in the attached image.

Here is the cmd prompt when running any command related to wsl:

PS C:\Users\Hp> wsl
Server execution failed
Error code: Wsl/CallMsi/Install/0x80080005
PS C:\Users\Hp> wsl.exe --version
Server execution failed
Error code: Wsl/CallMsi/Install/0x80080005
PS C:\Users\Hp> wsl -l -v
Server execution failed
Error code: Wsl/CallMsi/Install/0x80080005
PS C:\Users\Hp> wsl.exe --status
Server execution failed
Error code: Wsl/CallMsi/Install/0x80080005

Diagnostic Logs

WslLogs-2024-08-20_13-37-56.zip

[github-actions[bot]]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute [collect-wsl-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-wsl-logs.ps1) in an **administrative powershell prompt**: ``` Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1 Set-ExecutionPolicy Bypass -Scope Process -Force .\collect-wsl-logs.ps1 ``` The script will output the path of the log file once done. If this is a networking issue, please use [collect-networking-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

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!

Open similar issues:

• WSL installation fails with error "0x8007019e" plus "wsl -l -v" gives an error "Wsl/0x80080005" (#11898), similarity score: 0.75

Closed similar issues:

• Unable to get WSL Working (#11275), similarity score: 0.78
• Error 0x8007019e and Wsl/CallMsi/0x80070424 and Wsl/REGDB_E_CLASSNOTREG (#11683), similarity score: 0.76
• WSL not working anymore (#11757), similarity score: 0.74
• WSL stopped working now reinstall failing (#10760), similarity score: 0.74

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

[github-actions[bot]]

Diagnostic information

``` Detected appx version: 2.2.4.0 Detected user visible error: Wsl/CallMsi/Install/0x80080005 Detected user visible error: Wsl/CallMsi/Install/0x80080005 Detected user visible error: Wsl/CallMsi/Install/0x80080005 Detected user visible error: Wsl/CallMsi/Install/0x80080005 ```

[github-actions[bot]]

Diagnostic information

``` Issue was edited and new log file was found: https://github.com/user-attachments/files/16674428/WslLogs-2024-08-20_13-37-56.zip Detected appx version: 2.2.4.0 Detected user visible error: Wsl/CallMsi/Install/0x80080005 Detected user visible error: Wsl/CallMsi/Install/0x80080005 Detected user visible error: Wsl/CallMsi/Install/0x80080005 Detected user visible error: Wsl/CallMsi/Install/0x80080005 ```

[DefinetlyNotAI]

I have seen the similiar issues, they aren't helpful

[OneBlue]

Thank you @DefinetlyNotAI. Looking at logs, it looks like your installation is corrupted. Can you try to download and install the latest MSI and see if that solves the issue ?

[DefinetlyNotAI]

i knew it was corrupted, ill try the msi

[DefinetlyNotAI]

I installed the MSI Now doing wsl or wsl --install takes forever and doesnt actually do anything, just hangs until ctrl-c is used

[OneBlue]

Interesting. Can you collect a dump when that happens ?

/dumps

[DefinetlyNotAI]

Ok, Here are the attached logs, BUT just putting it out there, the windows explorer still shows an error

WslLogs-2024-08-21_09-30-05.zip

[github-actions[bot]]

Diagnostic information

``` Detected appx version: 2.3.17.0 ```

[OneBlue]

@DefinetlyNotAI: Looking at the logs it still looks like you're on 2.2.4. Can you confirm that you installed the 2.3.17 MSI ?

[DefinetlyNotAI]

Yes i have, it said success, then autoclosed the msi installer

[OneBlue]

Can you capture logs of installing that MSI ? Something is definitely not right there.

msiexec /i /path/to/msi /L*V C:\wsllogs.txt 

[DefinetlyNotAI]

Sorry, rate response, i have deleted the msi, im reinstalling it

[DefinetlyNotAI]

Now the msi just crashes,

https://github.com/user-attachments/assets/dcfc62ff-0952-4ce0-b7be-0241bdd0d983

[OneBlue]

@DefinetlyNotAI: Hmm, msiexec is weird sometimes. What if copy the .msi in C:\ and try to call it with msiexec from there ?

[OneBlue]

If it fails again, please share the log, this should contain more information at least

[DefinetlyNotAI]

no log is found... it is in the video

[DefinetlyNotAI]

Wait.. now it opened UAC, then crashed

[OneBlue]

Ah, I think I know what's missing: Can you try the msiexec command line in an elevated command prompt ?

[DefinetlyNotAI]

Im doing this again: Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1 Set-ExecutionPolicy Bypass -Scope Process -Force .\collect-wsl-logs.ps1

[DefinetlyNotAI]

Wait, i do it again?

[DefinetlyNotAI]

ok

[OneBlue]

Yeah what we need is the installation log, since that's where the issue is coming from

[DefinetlyNotAI]

https://github.com/user-attachments/assets/19ad4188-ff48-421c-b254-ebea9fb7c0db

Sadly it still does nothing and just crashes no logs are also generated

[OneBlue]

This actually looks like the expected behavior. Can you do that and add the logs command line ? Also is the explorer still failing to open \wsl.localhost now ?

[DefinetlyNotAI]

WslLogs-2024-08-21_23-45-49.zip Is me doing logs again,

And yes explorer fails to open the wsl folder

No logs are generated from previous instructions

Thx for being patient with me

[github-actions[bot]]

No logs.etl found in the archive. Make sure that you ran collect-wsl-logs.ps1 as administrator and that the logs.etl file is in the archive.

Diagnostic information

``` Detected appx version: 2.3.17.0 No logs.etl found in archive. Error while parsing the logs. See action page for details ```

[DefinetlyNotAI]

And it shows that not etl file is found...?

[OneBlue]

Can you run:

msiexec /i <msi> /L*V C:\wsllogs.txt  

In an administrator cmd.exe ? Now the installer is starting so this must generate a C:\wsllogs.txt

[DefinetlyNotAI]

ok

[DefinetlyNotAI]

fyi, the msi given to me is version 2.3 something (its name)

[DefinetlyNotAI]

https://github.com/user-attachments/assets/ddb3af21-3a28-4fe7-bc31-3a3e29a1d728

[OneBlue]

This looks non a non-elevated powershell. Can you run this in an elevated cmd.exe ?

[DefinetlyNotAI]

ok

[DefinetlyNotAI]

BUT the log was generated

wsllogs.txt

[OneBlue]

Is this the correct path to the MSI ? Can you try to pass "C:\wsl.msi" instead, since this is where you copied it earlier ?

[DefinetlyNotAI]

I attached the logs In the txt file

( In my country its pretty late, so im might go offline for a while to sleep )

[OneBlue]

The installation didn't start because the path to the msi file was wrong. can you try to run this again with the right path ? (C:\wsl.msi according to the previous video)

[DefinetlyNotAI]

for some reason it didnt open the log, but i attached it

[DefinetlyNotAI]

The installation didn't start because the path to the msi file was wrong. can you try to run this again with the right path ? (C:\wsl.msi according to the previous video)

ok. ill try

[DefinetlyNotAI]

ur right: wsllogs.txt

[OneBlue]

Thank you @DefinetlyNotAI. Looking at the logs, it looks something is failing while uninstall the previous version, which breaks the installation.

If you go to installed programs, you should see multiple entries for WSL. Can you try to remove them all ?

[DefinetlyNotAI]

Hmm... From my programs this is a peculiar one:

Here is wsl in settings

Here is wsl in programs and files

Here is in Programs dir

Here is in x86 Programs dir

Root dir

Search in root dir (And many more their)

[DefinetlyNotAI]

@OneBlue Here

[DefinetlyNotAI]

??

[DefinetlyNotAI]

Um, please i need a fix... OH, holidays - sorry i forgot different holiday schedules exist - SO SORRY

[DefinetlyNotAI]

Umm?

[DefinetlyNotAI]

??? Should i open a new issue, getting ridiculous now

[chris-piekarski]

I struggled with this for weeks myself. It ended up being a bad intel I9 13th gen CPU chip. I swapped it out with a new 14th gen and all the WSL instability and never ending errors went away. I am currently sending the bad CPU back to intel as part of the over voltage oxidation issue.