search

microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.48k stars 822 forks source link

WSL2 system.vhd - The file or directory is corrupted and unreadable. #12129

Closed Cptwafflez closed 1 month ago

Cptwafflez commented 1 month ago

Windows Version

Version 10.0.22631.4169

WSL Version

2.3.24.0

Are you using WSL 1 or WSL 2?

Kernel Version

No response

Distro Version

Ubuntu-22.04

Other Software

No response

Repro Steps

Launching WSL via cmd, PowerShell, start menu all produce the same issue. Issue persists even with/without admin and after restarts/chkdsks.

Expected Behavior

WSL typically boots up in seconds, leading to a pleasant and expected experience

Actual Behavior

When attempting to launch from the methods above, I am stopped and given the error below:

Failed to attach disk 'C:\Program Files\WSL\system.vhd' to WSL2: The file or directory is corrupted and unreadable. Error code: Wsl/Service/CreateInstance/CreateVm/MountVhd/HCS/0x80070570

I have seen another related issue (#7991) but I did not delete any large amounts of data preceding this issue.

Diagnostic Logs

No response

github-actions[bot] commented 1 month ago

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](https://github.com/Microsoft/WSL/blob/master/diagnostics/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 script will output the path of the log file once done. If this is a networking issue, please use [collect-networking-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) 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!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

tharos47 commented 1 month ago

Hello, I had the same issue after updating wsl with wsl --update

Here is the fix that worked https://github.com/microsoft/WSL/issues/11069#issuecomment-2348414833

(you just need to extract the files from the msi of wsl 2.3.24.0)

Cptwafflez commented 1 month ago

Hello, I had the same issue after updating wsl with wsl --update

Here is the fix that worked #11069 (comment)

(you just need to extract the files from the msi of wsl 2.3.24.0)

Hey there @tharos47 - appreciate the help, this solution worked!