-
Notifications
You must be signed in to change notification settings - Fork 834
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
WSL2. Can no longer find 'C:\Program Files\WSL\system.vhd' #11069
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:
|
Same here after installed v2.1.1.0 |
me too.
|
I just reinstalled WSL2 in the end, after first copying the vhdx in my AppData to a safe location, just in case. |
mee too |
I reinstalled also and worked... |
This is unfortunately a known issue when upgrading from an older version. The way to solve this is to manually download and install the new version. You can find the latest MSI there: https://github.com/microsoft/WSL/releases/tag/2.1.1 |
I have to say though, that it worked fine for a couple of days after the upgrade. Then the vhd suddenly 'disappeared overnight'. Nevertheless, I will give this a go if it happens again. |
@OneBlue Thank you! Confirmed this fixed the issue for me. Saved me a bunch of time, because every other thread seemed to recognize unmounting and re-installing which would have took a ton of time for me to re-setup my workspaces. Same thing as @simonlaszcz, I updated wsl everything worked fine, next day I get this error. |
I was also using 2.0.14 and lost two days in a row the Ubuntu distro. Now I give a try with the latest version 2.1.1. Error message in wsl 2.0.14:
|
this helped, thanks. But absolutely confusing as an 'known issue' this is nowhere to be seen |
Thanks @OneBlue! Upgrading to v2.1.3 fixed this issue. |
You saved my file! Thank you! |
Same behavior here. Reinstalling wsl.2.1.5.0.x64.msi does not fix the issue ! I then went to look into the msi archive a extracted the systemd.vhd file as system.vhd. But this is really not a user friendly process :-( |
@jtognazzi: Can you share logs of the installation of 2.1.5.0 if that doesn't solve the issue ? You can collect them via msiexec /i /L*V C:\wsllogs.txt |
@OneBlue |
I couldn't initiate my old vhdx disk eventually, but I handled to move all my precious data to another subsystem by mounting the disk via https://learn.microsoft.com/en-us/windows/wsl/wsl2-mount-disk |
Exact same issue here. The proposed solution also worked - for extracting the system.vhd file from the msi installer I ran
The file is then at the following location
from there just copy it to |
I also have same error.
I copy from my colleague PC same file to my PC with same version, then it can launch. |
Perfect, it works for me! Actually, I extracted the systemd.vhd from latest msi archive and renamed it to system.vhd, and it works well. But I cannot extract this file directly to folder C://Program Files/WSL, it pops up a window indicating permission deny, so I extract it to other folder and then copy to C://Program Files/WSL. |
|
I have just now updated to wsl 2.2.4.0 and the issue still persists. After running the
|
Today it worked with exactly same problem with version 2.3.26.0 |
I do this with several adjustments for example I work with this version below then I search for the exact version in this Release page which is 2.3.26.0 It worked. Just find the missing |
Windows Version
10.0.22621.3007
WSL Version
2.0.14.0
Are you using WSL 1 or WSL 2?
Kernel Version
No response
Distro Version
Debian
Other Software
No response
Repro Steps
Try to open console
or
try wsl --export
Expected Behavior
For it to work
Actual Behavior
Failed to attach disk 'C:\Program Files\WSL\system.vhd' to WSL2: The system cannot find the file specified.
Error code: Wsl/Service/CreateInstance/CreateVm/MountVhd/HCS/ERROR_FILE_NOT_FOUND
[process exited with code 4294967295 (0xffffffff)]
You can now close this terminal with Ctrl+D, or press Enter to restart.
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: