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

July 9th, 2024 update corrupted and destroyed my WSL instance #11776

Closed
1 of 2 tasks
aleph2c opened this issue Jul 12, 2024 · 7 comments
Closed
1 of 2 tasks

July 9th, 2024 update corrupted and destroyed my WSL instance #11776

aleph2c opened this issue Jul 12, 2024 · 7 comments

Comments

@aleph2c
Copy link

aleph2c commented Jul 12, 2024

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?

  • WSL 2
  • WSL 1

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

Copy link

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 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
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com 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.

@zuohl
Copy link

zuohl commented Jul 15, 2024

WslLogs-2024-07-15_21-27-27.zip
20240715213000

@aleph2c
Copy link
Author

aleph2c commented Jul 29, 2024

My WSL instance was corrupted even after I ran your command.

@OneBlue
Copy link
Collaborator

OneBlue commented Aug 20, 2024

/logs

@OneBlue
Copy link
Collaborator

OneBlue commented Aug 20, 2024

/logs

@aleph2c
Copy link
Author

aleph2c commented Aug 26, 2024

I have since switched operating systems; no logs available.

@OneBlue
Copy link
Collaborator

OneBlue commented Sep 5, 2024

Closing since no logs are available.

@OneBlue OneBlue closed this as completed Sep 5, 2024
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