-
Notifications
You must be signed in to change notification settings - Fork 821
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
Failed to update from 23.10 to 24.04 on WSL2, by 2024.6.13 #11694
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 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 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:
|
Having same issue. I tried reinstalling snapd. I do not use any snaps, so I ran |
An alternative to removing snapd is to enable systemd in the distribution, see https://learn.microsoft.com/en-us/windows/wsl/systemd |
remove snapd
but still do-release-upgrade fail and can't update anymore
some solution below don't work
|
install deb package version by force which wget from https://ubuntu.pkgs.org/24.04/ubuntu-main-amd64
|
|
Windows Version
10.0.22631.3737
WSL Version
0.0.0.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.10.16.3-microsoft-standard-WSL2
Distro Version
23.10
Other Software
N/A
Repro Steps
Step 1:
sudo do-release-upgrade
Step 2:
sudo systemctl restart snapd.service
Step 3:
sudo service snapd start
Step 4:
sudo service snapd.service start
Expected Behavior
I expect to see a successful update
Actual Behavior
Result of Step 1:
Result of step 2:
Result of step 3:
Result of step 4:
Diagnostic Logs
N/A
The text was updated successfully, but these errors were encountered: