Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wsl fail to start after auto-update #12127

Closed
1 of 2 tasks
shaobingchen opened this issue Oct 4, 2024 · 6 comments
Closed
1 of 2 tasks

wsl fail to start after auto-update #12127

shaobingchen opened this issue Oct 4, 2024 · 6 comments

Comments

@shaobingchen
Copy link

shaobingchen commented Oct 4, 2024

Windows Version

Microsoft Windows [Version 10.0.22631.4169]

WSL Version

can not be get by "wsl.exe --version" now

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

can not be get by "wsl.exe --status" now, it most likely to be the newest one at 10/4/2024, since it is triggered by auto-update.

Distro Version

Ubuntu 24

Other Software

No response

Repro Steps

run
wsl
at powershell, regardless of the parameters

Expected Behavior

it should enter the wsl

Actual Behavior

WSL is finishing an upgrade...
Could not write value to key \SOFTWARE\Classes\Directory\Background\shell\WSL\command. Verify that you have sufficient access to that key, or contact your support personnel.
Update failed (exit code: 1603).
Error code: Wsl/CallMsi/Install/ERROR_INSTALL_FAILURE

in fact, i have give "full control" permision of keys

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Drive\shell\WSL
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Directory\background\shell\WSL
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Directory\shell\WSL
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Directory\shell\WSL\command

to administrator and current user by using registry.exe, but it doesn't work.

Diagnostic Logs

WslLogs-2024-10-04_22-00-48.zip

No response

Copy link

github-actions bot commented Oct 4, 2024

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 [email protected] 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!

Closed similar issues:

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

Copy link

github-actions bot commented Oct 4, 2024

Diagnostic information
Issue was edited and new log file was found: https://github.com/user-attachments/files/17259642/WslLogs-2024-10-04_22-00-48.zip
.wslconfig found
Detected appx version: 2.3.24.0
Detected user visible error: Wsl/CallMsi/Install/ERROR_INSTALL_FAILURE

@shaobingchen
Copy link
Author

shaobingchen commented Oct 4, 2024

by the way, any one know how to stop this update process? use an old but stable version is fine for me.

@ubranch
Copy link

ubranch commented Oct 4, 2024

same error here

@shaobingchen
Copy link
Author

#11697
it works after restart

@yuan-yb
Copy link

yuan-yb commented Nov 21, 2024

you should give "full control" permision of the keys to the "SYSTEM" user, rather than the "administrator", your own user account, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants