Failed to attach disk 'C:\Program Files\WSL\system.vhd' to WSL2: The system cannot find the file specified. about wsl HOT 12 OPEN

Solved by rolling back to 2.1.4.0

from wsl.

Solved by rolling back to 2.1.4.0

Can you please tell me how you roll back? Same issue here and I have been struggling the full day to solve this.

You can download 2.1.4.0 here, run the installer and it will do the job for you.

That hepled! Almost deleted my wsl. Thanks

from wsl.

Solved by rolling back to 2.1.4.0

Can you please tell me how you roll back? Same issue here and I have been struggling the full day to solve this.

You can download 2.1.4.0 here, run the installer and it will do the job for you.

from wsl.

There is no change in behavior between these two versions so I suspect there is some kind of latent issue with upgrade. Looks identical to #11069.

@OneBlue - can you take a look?

from wsl.

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:

• Failed to attach disk 'LocalState\ext4.vhdx' to WSL2: The system cannot find the file specified. (#10032), similarity score: 0.80

Closed similar issues:

• WSL2. Can no longer find 'C:\Program Files\WSL\system.vhd' (#11069), similarity score: 0.89
• WSL missing system.vhd (#11162), similarity score: 0.81
• WSL2 is failing to attach the wsl virtual disk and giving error code 4294967295 (#10390), similarity score: 0.79
• VHD mount issue with "WSL (2156) ERROR: UtilMount" (#11183), similarity score: 0.75

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

from wsl.

Solved by rolling back to 2.1.4.0

Can you please tell me how you roll back? Same issue here and I have been struggling the full day to solve this.

from wsl.

Thanks a lot @benhillis as I have no admin rights I really hope our IT Support is quick. @VladimirKaznacheiev I feel you, good that I do not have Admin rights :D

from wsl.

Solved by rolling back to 2.1.4.0

Can you please tell me how you roll back? Same issue here and I have been struggling the full day to solve this.

You can download 2.1.4.0 here, run the installer and it will do the job for you.

this is perfect.

tried everything from rolling back windows update to local security policy and regedit.
Thank you !

from wsl.

Solved by rolling back to 2.1.4.0

Good afternoon, unfortunately the reinstallation did not help me, do you know what else I can try?

Docker itself updates to the latest version of wsl, don’t know how to disable it?

from wsl.

No expert here. My docker desktop or WSL2 wouldn't start yesterday after working just hours before.
I got the same error message. I only had some 4-5 files in C:\Program Files\WSL, and system.vhd was not there.

As part of troubleshooting I did uninstall docker-desktop first. But I guess that was not needed.
I did install the 2.1.4 installer linked in this post. After that, I had lots of files in C:\Program Files\WSL, including system.vhd.
Then I re-installed docker-desktop. After that, I had WSL 2 working again.

# output after installing 2.1.4 install file and re-installing docker-desktop 
PS C:\ wsl --version
WSL version: 2.1.4.0
Kernel version: 5.15.146.1-2
WSLg version: 1.0.60
MSRDC version: 1.2.5105
Windows version: 10.0.19045.4046

Maybe using 2.1.5 installer would has worked just as well, I didn't test.
Might not have needed to re-install docker-desktop.

No idea what caused what seems like removing existing system.vhd and supporting files (if that happened). When WSL2 was not working anymore and I looked in C:\Program Files\WSL, I didn't have many files there, I just had like 4-5 files in that directory, plus some folders with log files and a few small size files.

I didn't install anything myself lately. I do have docker-desktop, but it doesn't auto-update for me. My IT dept said no rollouts was made recently.

So still no idea what caused this for me. I guess I'm happy it works now after this scare, and this post helped.

from wsl.

Thank you @joelhellman. Out of curiosity, do you have a .wslconfig ? If so can you share its contents ?

from wsl.

@OneBlue sure, here is my full unedited .wslconfig (it has been unchanged for about a year)

# Settings apply across all Linux distros running on WSL 2
[wsl2]
# guiApplications=false

# Limits VM memory
memory=12GB

from wsl.