-
Notifications
You must be signed in to change notification settings - Fork 823
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_E_DISK_CORRUPTED #10996
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. 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. Thank you! Open similar issues:
Closed similar issues:
|
/logs |
Sorry it was an urgent case and my administrator had uninstall WSL via Settings\Apps & Features. WSL can be started now. |
if someone else encounters the same issue can follow the logs instructions above. |
Windows Version
Microsoft Windows [Version 10.0.19045.3803]
WSL Version
2.0.14.0
Are you using WSL 1 or WSL 2?
Kernel Version
Ubuntu 2
Distro Version
should be Ubuntu 22.04 (the last Ubuntu version aka jammy jellyfish that I installed)
I have this file:
...\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu_79rhkp1fndgsc\LocalState\ext4.vhdx
and also this folder:
...\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu20.04LTS_79rhkp1fndgsc
Other Software
Not applicable
Repro Steps
I had to change my AD domain recently and wsl was not available after that.
I then did a
wsl --install
followed bywsl --update
to 2.0.14.0.I think my previous version was 2.0.9.0.
And got the error below when I tried to launch wsl
Expected Behavior
Ideally, I can restart my WSL. Or at least be able to retrieve my files in WSL filesystem.
Actual Behavior
After AD domain change, am getting the below after
wsl --install
andwsl --update
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: