-
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
Cannot update WSL2 on Windows 10 (tried reinstalling) #12004
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! Open similar issues:
Closed similar issues:
|
I am sorry, but I am not sure why should I upload in public logs/data generated by the script |
Possible Issue SourceI am not sure at this point, but it's probably a bug where the latest installer, supposedly, tries to execute the installer of the current version expecting the file of the latter is already in directory Once again I tried executing Possible Workaround/SolutionThankfully it showed this error message, and I downloaded the file from GitHub repository Releases, copied it to
Et Voilà! ✨ |
Closing since the issue is resolved and doesn't have logs to diagnose the root cause. |
@OneBlue , thank you for the attention, but I am sorry, I believe it is a bug, and the issue must not be closed until a more clear clarification regarding this behavior. I stated the rationale behind absence of logs. Why does the installer of the latest version require an installer of the current/previous version is actually unclear. Is that an expected behavior of the installer in the first place? Besides, this is not a solution but a workaround, where I manually downloaded the file the installer implicitly required. |
Windows Version
Microsoft Windows [Version 10.0.19045.4780]
WSL Version
2.0.14.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.133.1-1
Distro Version
Ubuntu 22.04
Other Software
Docker Desktop v4.33.1
Repro Steps
Docker Desktop WSL update
Manual WSL update
wsl --update
.Update after reinstalling WSL
optionalfeatures
to/or open window "Turn Windows features on or off";Windows Subsystem for Linux
;1-4
but with the selection in stateEnabled
;wsl --version
;Expected Behavior
Both WSL and Docker Desktop updates successfully.
Actual Behavior
First of all, thank you very much for the marvelous project! 🪐✨
Docker Desktop executes
wsl --update
under the hood, and the latter fails for currently unknown reason.With the update fail, Docker Desktop will attempt to do the same over and over until only the user prohibits administrative permissions prompt, and that will end up with the following message:
When we try to update WSL manually, it looks like the following:
To clarify, seeing the
^C
orCtrl+C
- signalSIGINT
, there was no such command pressed. The terminal was not getting any interaction duringwsl --update
execution.It's probably worth to notice that WSL installation files are getting downloaded each time into
%TEMP%
directory:Each time it launches a new installation file and the installation logs shared in section
Diagnostic Logs
(wsl-install-logs.txt
) of this repository issue state various "error status codes", including16
,21
,22
,23
,1603
,1607
,1612
,1709
,1714
, and is there any more or less comprehensive/organized reference to see what these actually mean instead of digging deep into the source code of currently unknown projects involved?Diagnostic Logs
Contents of `%TEMP%\wsl-install-logs.txt`
The text was updated successfully, but these errors were encountered: