-
Notifications
You must be signed in to change notification settings - Fork 838
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 2 Not starting #7831
Comments
/logs |
Hello! Could you please provide more logs to help us better diagnose your issue? You can find instructions on how to attach logs here, please make sure to post the link to the Feedback Hub item in this chat so we can see it. Thank you! |
I have logged it in the Feedback hub app |
Could you find time to look into my issue |
Thanks @Wizards-god. Can you please share the link to your feedback hub entry ? |
https://aka.ms/AAf6ee8 , Here is the link to my issue on Feedback Hub. |
Thanks @Wizards-god. Looking at the logs, I can see:
Based on that, it looks like your distribution VHD is corrupted. Can you share the content of |
I did not know how to export individual keys, so just exported it and attached it here |
Ok, based on that I can see that the disk for ubuntu is in To recover its content the simplest I can think of would be to use
And then use fsck on the disk to try to recover its content (you can use Note that:
|
Thank you so much, I could recover all my files from the distro. Now it is working like before. |
Happy it worked ! Closing this. |
Version
Microsoft Windows [Version 10.0.22000.348]
WSL Version
Kernel Version
5.10.60.1
Distro Version
Ubuntu 20.04(maybe), Arch Linux
Other Software
PowerToys
Zoom
Cisco Webex
Cloudflare
Spotify
Windows Terminal
Glasswire
Repro Steps
Open Ubuntu.
Expected Behavior
Ubuntu to start normally, and I continue on my work.
Actual Behavior
It exits with this error.
The operation timed out because a response was not received from the virtual machine or container.
[process exited with code 4294967295]
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: