-
Notifications
You must be signed in to change notification settings - Fork 854
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
July 9th, 2024 update corrupted and destroyed my WSL instance #11776
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:
|
My WSL instance was corrupted even after I ran your command. |
/logs |
/logs |
I have since switched operating systems; no logs available. |
Closing since no logs are available. |
Windows Version
Microsoft Windows [Version 10.0.22631.3880]
WSL Version
WSL version: 2.1.5.0
Are you using WSL 1 or WSL 2?
Kernel Version
Kernel version: 5.15.146.1-2
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
Perform a windows update and restart your computer.
Expected Behavior
The expected behavior is the WSL and all of the files within it should service the update.
Actual Behavior
The WSL was corrupted and all of the information within it was destroyed.
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: