You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Failed to attach disk 'C:\Program Files\WSL\system.vhd' to WSL2: The system cannot find the file specified. #11288
Failed to attach disk 'C:\Program Files\WSL\system.vhd' to WSL2: The system cannot find the file specified.
Diagnostic Logs
No response
Reacted by Nikolai Pulkkinen, JenniferHem, fujikawa-rootip, Rustam, ostecke, dperez83, John Lyu, archive-20260622, Călin Diaconu, Chris Ebert and 7 more
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!
Thanks a lot Ben Hillis (@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
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.
Very happy with the suggestion of installing 2.1.4 since that instantly brought my WSL back to life, many many thanks.
Very unhappy with this critical bug in a patch version being around for more than two months without being addressed. Most people using WSL will be developers or students that rely on WSL working properly. These situations make me want to buy a Macbook.
Reacted by JenniferHem, Mahdi Baghdadi, John Lyu, zhao, Mateusz Majka, Campbell Brown, bobojobo, jira-zz, Ethan Reish, Slavko Fodor and 1 more
Neither installing 2.1.4 nor 2.1.5 fixed the problem for me (was using the msix installer). I just copied the files from its old location C:\ProgramData\Microsoft\WSL to the new location C:\Program Files\WSL with elevated rights, and it was working again. I made sure, that this procedure did not overwrite existing files (some of them were already there).
Same here. Update policy of my company suddenly restarted my PC without any warning, after that WSL stopped working.
I don't know what version I had before, but the 2.4.12 was not working, and installing the previous one, 2.4.11 fixed the problem.
Same here. Update policy of my company suddenly restarted my PC without any warning, after that WSL stopped working. I don't know what version I had before, but the 2.4.12 was not working, and installing the previous one, 2.4.11 fixed the problem.
The same thing happened to me this morning. Swapping to 2.4.11 fixed it here as well.
Same here. Update policy of my company suddenly restarted my PC without any warning, after that WSL stopped working. I don't know what version I had before, but the 2.4.12 was not working, and installing the previous one, 2.4.11 fixed the problem.
The same thing happened to me this morning. Swapping to 2.4.11 fixed it here as well.
Confirming that WSL was running when my computer auto-updated. Coming back up, this error occurred. Downgrading to 2.4.11 (from 2.4.12) fixed the issue.
I was also able to upgrade from 2.4.11 back to 2.4.12 and things are also still working and no data loss.
I upgraded from WSL 2.4.13 to WSL 2.5.7 in Windows 11, by "wsl --update"
but encountered the issue: "Failed to attach disk 'C:\Program Files\WSL\system.vhd' to WSL2"
Fix Method:
Download wsl.2.5.7.0.x64.msi from github
Shift + Right-click the MSI file
Select "Repair (P)"
After the repair completes, 'C:\Program Files\WSL\system.vhd' will be available.
Reacted by yuswaldi-klink, Joey, Alvar San Martin, Alex O'Donnell, Eric L. Frederich, Sam, Adrián Martín, Max Chaban, dbieber-rfideas, Kresna Satya and 18 more
Reacted by Alvar San Martin, Ilya Kraev, Shuan Chen, dbieber-rfideas, Kresna Satya, Maksim Cherkasov, Calum Lind, Shawn Peng, Dave Shoup, Anthony Douglas and 4 more
I upgraded from WSL 2.4.13 to WSL 2.5.7 in Windows 11, by "wls --update" but encountered the issue: "Failed to attach disk 'C:\Program Files\WSL\system.vhd' to WSL2"
Fix Method:
Download wsl.2.5.7.0.x64.msi from github
Shift + Right-click the MSI file
Select "Repair (P)"
After the repair completes, 'C:\Program Files\WSL\system.vhd' will be available.
I upgraded from WSL 2.4.13 to WSL 2.5.7 in Windows 11, by "wsl --update" but encountered the issue: "Failed to attach disk 'C:\Program Files\WSL\system.vhd' to WSL2"
Fix Method:
1. Download wsl.2.5.7.0.x64.msi from github
2. Shift + Right-click the MSI file
3. Select "Repair (P)"
After the repair completes, 'C:\Program Files\WSL\system.vhd' will be available.
Thank you so much! It works!
Reacted by Calum Lind, daviderni-pofi, Paul Lee and Václav Dohnal
I upgraded from WSL 2.4.13 to WSL 2.5.7 in Windows 11, by "wsl --update" but encountered the issue: "Failed to attach disk 'C:\Program Files\WSL\system.vhd' to WSL2"
Fix Method:
1. Download wsl.2.5.7.0.x64.msi from github
2. Shift + Right-click the MSI file
3. Select "Repair (P)"
After the repair completes, 'C:\Program Files\WSL\system.vhd' will be available.
Same issue after upgrading to 2.5.10.0, repair did the trick.
Comentaré mi caso:
Parece que al hacer wsl --update
Mi distro dejó de responder, usualmente me conecto con wsl -d Ubuntu pero en este caso me salía este mensaje
Failed to attach disk 'C:\Program Files\WSL\system.vhd' to WSL2: El sistema no puede encontrar el archivo especificado.
De alguna forma llegué a alguna página de microsoft para validar que aún estaba mi archivo que en teoría es el disco duro virtual en
C:\Users\LENOVO\AppData\Local\Packages
en esa carpeta encontré mi distro CanonicalGroupLimited.Ubuntu_45sdfxhfac3 y en esa carpeta debí asegurarme que aun sigue mi distro LocalState/ext4.vhdx por si acaso me hice una copia de seguridad de toda la carpeta CanonicalGroupLimited.Ubuntu_45sdfxhfac3
Diria que lo que me solucionó fue:
wsl --shutdown
wsl --uninstall
wsl --install
Recuerdo que tenía 2 distros, una que instalé que tenía el nombre a secas "Ubuntu" y la otra que no sé de dónde salió, creo que con la primera instalación apareció. Después de esos pasos al ejecutar wsl --list aparecía solo el distro que instalé y tenía todo mis archivos del trabajo :'v. Vi por ahí vi comentarios de hacer cosas raras :'v creí que los perdería pero ya estoy bien, ya tengo mis archivos recuperados. Esperen... acabo de levantar el docker desktop y el otro distro era docker-desktop. Entonces no perdí nada.
Wilder Trujillo (@wilder00) thanks a lot after uninstalling i removed CanonicalGroupLimited* folders from %AppData%\Local\Packages and make clean install and all worked fine.
I don't know what was broken. I think new windows 10 updates at the morning
I had the same problem after upgrading to 2.6.1 (via wsl --update). The PC suddenly restarted, and after booting up, WSL wouldn’t start (system cannot find that vhd file). I downloaded the latest installer (MSI), right-clicked on it, selected Repair, and now everything seems fine.
Reacted by Illich Rada, Allan Leal, Nikita, wzhiana, Luciano Paciornick, Lir Locker, Tobi, jordanjimenez-wp and Magneto
Reacted by Allan Leal, Nikita, Lir Locker, Magneto, Hyeongji Kim and Cocioaba Cornel
I had the same problem after upgrading to 2.6.1 (via wsl --update). The PC suddenly restarted, and after booting up, WSL wouldn’t start (system cannot find that vhd file). I downloaded the latest installer (MSI), right-clicked on it, selected Repair, and now everything seems fine.
This is the correct solution, I already face the same error when microsoft store automatically uptated the WSL to the 2.6.1 Version.
Thank you.
Reacted by bdemarne, Magneto, Hyeongji Kim, Rashif Ray Rahman and Ala' Alnajjar
Activity
github-actions commentedon Mar 12, 2024
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:
onmywaytoheaven commentedon Mar 12, 2024
Solved by rolling back to 2.1.4.0
JenniferHem commentedon Mar 12, 2024
Can you please tell me how you roll back? Same issue here and I have been struggling the full day to solve this.
onmywaytoheaven commentedon Mar 12, 2024
You can download 2.1.4.0 here, run the installer and it will do the job for you.
benhillis commentedon Mar 12, 2024
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.
Blue (@OneBlue) - can you take a look?
VolodymyrKaznacheiev commentedon Mar 12, 2024
That hepled! Almost deleted my wsl. Thanks
JenniferHem commentedon Mar 13, 2024
Thanks a lot Ben Hillis (@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
aclerc-blachere commentedon Mar 13, 2024
this is perfect.
tried everything from rolling back windows update to local security policy and regedit.
Thank you !
Romakip commentedon Mar 16, 2024
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?
joelhellman commentedon Mar 19, 2024
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.
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.
OneBlue commentedon Mar 19, 2024
Thank you Joel Hellman (@joelhellman). Out of curiosity, do you have a .wslconfig ? If so can you share its contents ?
joelhellman commentedon Mar 24, 2024
Blue (@OneBlue) sure, here is my full unedited .wslconfig (it has been unchanged for about a year)
ostecke commentedon May 29, 2024
Very happy with the suggestion of installing 2.1.4 since that instantly brought my WSL back to life, many many thanks.
Very unhappy with this critical bug in a patch version being around for more than two months without being addressed. Most people using WSL will be developers or students that rely on WSL working properly. These situations make me want to buy a Macbook.
mx-bernhard commentedon Jun 4, 2024
Neither installing
2.1.4nor2.1.5fixed the problem for me (was using the msix installer). I just copied the files from its old location C:\ProgramData\Microsoft\WSL to the new location C:\Program Files\WSL with elevated rights, and it was working again. I made sure, that this procedure did not overwrite existing files (some of them were already there).7 remaining items
kamichal commentedon Mar 12, 2025
Same here. Update policy of my company suddenly restarted my PC without any warning, after that WSL stopped working.
I don't know what version I had before, but the
2.4.12was not working, and installing the previous one,2.4.11fixed the problem.bpratt-uncomn commentedon Mar 13, 2025
The same thing happened to me this morning. Swapping to
2.4.11fixed it here as well.plabbett commentedon Mar 14, 2025
Confirming that WSL was running when my computer auto-updated. Coming back up, this error occurred. Downgrading to 2.4.11 (from 2.4.12) fixed the issue.
I was also able to upgrade from
2.4.11back to2.4.12and things are also still working and no data loss.jbrathwa commentedon Mar 27, 2025
I encountered a similar issue with version
2.4.13, and I was able to resolve it by downgrading to version2.4.11.mathisgauthey commentedon Mar 27, 2025
Same thing here. I will try to downgrade.
EDIT : Downgrading to WSL
2.4.11is a solution. It prevented me from starting my IntelliJ... Glad I found this post !dosif commentedon Apr 2, 2025
Same issue here. Worked by downgrading from
2.4.13to2.4.11AND performing a reboot of the machine.syuuha commentedon May 28, 2025
I upgraded from WSL 2.4.13 to WSL 2.5.7 in Windows 11, by "wsl --update"
but encountered the issue: "Failed to attach disk 'C:\Program Files\WSL\system.vhd' to WSL2"
Fix Method:
After the repair completes, 'C:\Program Files\WSL\system.vhd' will be available.
joey-bolts commentedon May 28, 2025
This also fixed it for me.
kresnasatya commentedon Jun 11, 2025
Thank you so much! It works!
totoguy commentedon Aug 25, 2025
Same issue after upgrading to 2.5.10.0, repair did the trick.
wilder00 commentedon Sep 6, 2025
Comentaré mi caso:
Parece que al hacer
wsl --updateMi distro dejó de responder, usualmente me conecto con
wsl -d Ubuntupero en este caso me salía este mensajeFailed to attach disk 'C:\Program Files\WSL\system.vhd' to WSL2: El sistema no puede encontrar el archivo especificado.De alguna forma llegué a alguna página de microsoft para validar que aún estaba mi archivo que en teoría es el disco duro virtual en
en esa carpeta encontré mi distro
CanonicalGroupLimited.Ubuntu_45sdfxhfac3y en esa carpeta debí asegurarme que aun sigue mi distroLocalState/ext4.vhdxpor si acaso me hice una copia de seguridad de toda la carpetaCanonicalGroupLimited.Ubuntu_45sdfxhfac3Diria que lo que me solucionó fue:
Recuerdo que tenía 2 distros, una que instalé que tenía el nombre a secas "Ubuntu" y la otra que no sé de dónde salió, creo que con la primera instalación apareció. Después de esos pasos al ejecutar
wsl --listaparecía solo el distro que instalé y tenía todo mis archivos del trabajo :'v. Vi por ahí vi comentarios de hacer cosas raras :'v creí que los perdería pero ya estoy bien, ya tengo mis archivos recuperados. Esperen... acabo de levantar el docker desktop y el otro distro eradocker-desktop. Entonces no perdí nada.darkdiesel commentedon Sep 12, 2025
Wilder Trujillo (@wilder00) thanks a lot after uninstalling i removed CanonicalGroupLimited* folders from %AppData%\Local\Packages and make clean install and all worked fine.
I don't know what was broken. I think new windows 10 updates at the morning
illagrenan commentedon Sep 12, 2025
I had the same problem after upgrading to
2.6.1(viawsl --update). The PC suddenly restarted, and after booting up, WSL wouldn’t start (system cannot find that vhd file). I downloaded the latest installer (MSI), right-clicked on it, selected Repair, and now everything seems fine.illich570 commentedon Sep 13, 2025
This is the correct solution, I already face the same error when microsoft store automatically uptated the WSL to the
2.6.1Version.Thank you.