-
Notifications
You must be signed in to change notification settings - Fork 822
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
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
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 View similar issuesPlease 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:
|
Diagnostic information
|
by the way, any one know how to stop this update process? use an old but stable version is fine for me. |
same error here |
#11697 |
you should give "full control" permision of the keys to the "SYSTEM" user, rather than the "administrator", your own user account, etc. |
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?
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
The text was updated successfully, but these errors were encountered: