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

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.

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

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 72 (2 by maintainers)

Most upvoted comments

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 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, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging 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:

Closed similar issues:

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