WSL suddenly stopped working error code - Error: 0x80090006 Invalid Signature.

[MISSEY]

WslLogs-2023-09-19_17-19-04.zip

Windows Version

Microsoft Windows [Version 10.0.25201.1000]

WSL Version

WSL version: 1.2.5.0 Kernel version: 5.15.90.1 WSLg version: 1.0.51 MSRDC version: 1.2.3770 Direct3D version: 1.608.2-61064218 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.25201.1000

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

Initially, wsl stopped working. I tried a few available solutions, didn't help. So, then I try to reinstall the distro, still had same issue:

PS C:\Users\smishra> wsl --install -d Ubuntu-22.04
Ubuntu 22.04 LTS is already installed.
Launching Ubuntu 22.04 LTS...
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80090006
Error: 0x80090006 Invalid Signature.

Previously installed wsl distro Ubuntu-22.04 also had the

Invalid Signature. Error code: Wsl/Service/CreateInstance/CreateVm/0x80090006

Expected Behavior

Actual Behavior

WSL should start the distro

Diagnostic Logs

No response

[MISSEY]

[OneBlue]

/logs

[microsoft-github-policy-service]

Hello! Could you please provide more logs to help us better diagnose your issue?

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 scipt will output the path of the log file once done.

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

Click here for more info on logging

Thank you!

[webme818]

Windows Version

Microsoft Windows [Version 10.0.25227.1010]

WSL Version

2.0.0.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.123.1-1

Hi, I am in almost the same situation.
I ran the logging, could you please check?

WslLogs-2023-09-19_11-01-56.zip

[webme818]

Windows Version

Microsoft Windows [Version 10.0.25951.1010]

I was fixed by Windows Update.

[MISSEY]

@OneBlue Here is the logs
WslLogs-2023-09-19_17-19-04.zip

[MISSEY]

@webme818 , I am not able to update, update window shows that, it is upto date.

[ghost]

Did you let /log collection run while running the install commands you were having problems with? I don't see anything in the logs.

[microsoft-github-policy-service]

Hello! Could you please provide more logs to help us better diagnose your issue?

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 scipt will output the path of the log file once done.

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

Click here for more info on logging

Thank you!

[MISSEY]

Hi @pmartincic, this time I ran the script collect-wsl-logs.ps1 in parallel with wsl install commands.

WslLogs-2023-09-20_10-26-57.zip

WslLogs-2023-09-20_11-07-03.zip

Thank you

[OneBlue]

Thank you @MISSEY. Looking at the logs I can see that the issue is that the hyper-V firmware signature has expired on your machine. Can you try to update to a more recent build and see if that solves the issue ?

[MISSEY]

@OneBlue, My windows version is Microsoft Windows [Version 10.0.25951.1010], and there is no more updates. On windows insder programme page I am seeing this error,

[MISSEY]

So, Unfortunately, I had to install new windows 11 to solve the issue

[mquangdev]

Hello! Could you please provide more logs to help us better diagnose your issue?

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 scipt will output the path of the log file once done.

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

Click here for more info on logging

Thank you!

Hello, i have the same problem and this is my logs file
WslLogs-2024-10-09_15-08-11.zip
Can you help me ?

[mahmoudgx]

Hi, I'm experiencing the same issue, and here is my log file. Could you assist me?

WslLogs-2024-12-19_14-57-58.zip