Repository navigation
Description
Windows Version
10.0.26200.7462
WSL Version
2.6.3.0
Are you using WSL 1 or WSL 2?
- WSL 2
- WSL 1
Kernel Version
6.6.87.2-1
Distro Version
Ubuntu 22.04.5 LTS
Other Software
Windows
Repro Steps
Get a forced update from Windows, which will restart your computer forcely.
Then try to run Ubuntu or VSCode connected to it... and get errors.
Now imagine if you lost all the work and setup and temporary files not sync with github.
Expected Behavior
Everything just works and using WSL feels safe to work with.
Actual Behavior
Fear of losing progress. System not working. Losing time to report bugs and blocked from work while not finding a solution.
Diagnostic Logs
Fehler beim Anfügen des Datenträgers "C:\Program Files\WSL\system.vhd" an WSL2: Das System kann die angegebene Datei nicht finden.
Fehlercode: Wsl/Service/CreateInstance/CreateVm/MountDisk/HCS/ERROR_FILE_NOT_FOUND
Microsoft Windows [Version 10.0.26200.7462]
PS C:\Users\henry> wsl.exe --version
WSL-Version: 2.6.3.0
Kernelversion: 6.6.87.2-1
WSLg-Version: 1.0.71
MSRDC-Version: 1.2.6353
Direct3D-Version: 1.611.1-81528511
DXCore-Version: 10.0.26100.1-240331-1435.ge-release
Windows-Version: 10.0.26200.7462
PS C:\Users\henry> lsb_release -r
[2025-12-20 10:13:17.667] NodeExecServer run: C:\WINDOWS\System32\wsl.exe -d Ubuntu-22.04 -e sh -c if [ -d ~/.vscode-server/bin/994fd12f8d3a5aa16f17d42c041e5809167e845a ]; then printf 'install-found '; fi; if [ -f /etc/alpine-release ]; then printf 'alpine-'; fi; uname -m;
[2025-12-20 10:13:18.705] Unable to detect if server is already installed: Error: Failed to probe if server is already installed: code: Failed to probe if server is already installed: code: 4294967295, , Fehler beim Anf�gen des Datentr�gers "C:\Program Files\WSL\system.vhd" an WSL2: Das System kann die angegebene Datei nicht finden.
[2025-12-20 10:13:18.705] Fehlercode: Wsl/Service/CreateInstance/CreateVm/MountDisk/HCS/ERROR_FILE_NOT_FOUND
[2025-12-20 10:13:18.705]
[2025-12-20 10:13:18.705] NodeExecServer run: C:\WINDOWS\System32\wsl.exe -d Ubuntu-22.04 sh -c '"$VSCODE_WSL_EXT_LOCATION/scripts/wslServer.sh" 994fd12f8d3a5aa16f17d42c041e5809167e845a stable code-server .vscode-server --host=127.0.0.1 --port=0 --connection-token=212470529-1317219931-825800281-1656135564 --use-host-proxy --without-browser-env-var --disable-websocket-compression --accept-server-license-terms --telemetry-level=all'
[2025-12-20 10:13:19.747] Fehler beim Anf�gen des Datentr�gers "C:\Program Files\WSL\system.vhd" an WSL2: Das System kann die angegebene Datei nicht finden.
[2025-12-20 10:13:19.747] Fehlercode: Wsl/Service/CreateInstance/CreateVm/MountDisk/HCS/ERROR_FILE_NOT_FOUND
[2025-12-20 10:13:19.747]
[2025-12-20 10:13:19.748] For help with startup problems, go to https://code.visualstudio.com/docs/remote/troubleshooting#_wsl-tips
Activity
github-actions commentedon Dec 20, 2025
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 in an administrative powershell prompt:
The script will output the path of the log file once done.
If this is a networking issue, please use collect-networking-logs.ps1, following the instructions in Collect WSL logs for networking issues
Once completed please upload the output files to this GitHub issue.
See Collect WSL logs (recommended method).
If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.
heberleh2 commentedon Dec 20, 2025
WslLogs-2025-12-20_11-35-53.zip
github-actions commentedon Dec 20, 2025
Diagnostic information
Ping-Hung commentedon Dec 21, 2025
Experiencing the same issue here, and here are my wsl logs
WslLogs-2025-12-20_19-54-14.zip
gorgsenegger commentedon Jan 1, 2026
Same for me, the
vhdfile is inC:\ProgramData\Microsoft\WSL, but the error message indicates that WSL seems to look in the wrong directory:Error message
gorgsenegger commentedon Jan 1, 2026
WslLogs-2025-12-20_19-54-14.zip
gorgsenegger commentedon Jan 3, 2026
Updating WSL from 2.6.2.0 to 2.6.3.0 solved the issue for me:
Running WSL works again.
trlef19 commentedon Feb 6, 2026
error remains
bstordrup commentedon Feb 25, 2026
Having the same issue.
shuaiyuanxx commentedon Mar 19, 2026
Thanks for the logs. The root cause across all reports is the same: system.vhd is missing from
C:\Program Files\WSL\after the2.6.2.0→2.6.3.0upgrade, either due to a Windows forced restart interrupting the MSI installation, or stale registry entries from an older WSL installation pointing to a path that no longer exists.Step 1: Re-deploy WSL
If it says no update is available, force a reinstall:
Step 2: If still broken, check for stale registry
reg query "HKLM\Software\Microsoft\Windows\CurrentVersion\Lxss" /v SystemDistroIf this returns a legacy path like
C:\ProgramData\Microsoft\WSL\system.vhd, delete it:reg delete "HKLM\Software\Microsoft\Windows\CurrentVersion\Lxss" /v SystemDistro /fThen run
wsl --shutdownandwsl --install --no-distributionagain.Step 3: Verify
dir "C:\Program Files\WSL\system.vhd"If the file exists, WSL should work normally.
H37IX commentedon Nov 21, 2026
Same symptom, now on 3.0.5.0 (upgraded from 2.7.3.0), with a recovered install timeline that points at the MSI upgrade/reboot path rather than stale registry. Adding it in case it helps narrow the root cause.
Environment: Windows 11 10.0.26300.9974, WSL 3.0.5.0 / kernel 6.18.58.1-1 / WSLg 1.0.79, 4 WSL2 distros, mirrored networking. Hyper-V enabled; the optional "Windows Subsystem for Linux" and "Virtual Machine Platform" features were both off (assuming not needed for WSL2 here, but still confuses me a bit. i thought it was needed and used to always install that as well. if not needed now, there should be better notice on what that add on feature for windows is intended for).
Symptom: after
wsl --update, every distro failed withFailed to attach disk 'C:\Program Files\WSL\system.vhd' ... ERROR_FILE_NOT_FOUND(Wsl/Service/CreateInstance/CreateVm/ERROR_FILE_NOT_FOUND).wsl --versionandwsl -l -vwork, so the install looks healthy until a VM starts.kernel,init,initrd.imgandartifacts.vhdundertools\were present.system.vhdwas absent, and a recursive search of C: found no copy.Timeline from the MsiInstaller log (local time, one day):
wsl.3.0.5.0.x64 (5).msi, whichwsl --updatehad downloaded to%TEMP%). Earlier--updateattempts on the previous day had left four more identical copies there. All five are byte-identical (SHA256231....AA), match the MSI cached inC:\Windows\Installer, and the Authenticode signature is valid. So the package is not corrupt.LastBootUpTime).system.vhdmissing, noPendingFileRenameOperationsleft, noSystemDistrovalue underHKLM\...\Lxss(so the stale-registry cause from the earlier comment doesn't apply here).Evidence the MSI is supposed to ship the file: the cached MSI's
Filetable listssystem.vhd(758,039,040 bytes, componentwsl, INSTALLDIR) in the embedded cabinets.Possible cause (inference, not proven): both the removal of the old product and the install of the new one reported "restart required", which suggests locked files.
system.vhdis attached to the running utility VM, so it is a good candidate. If the old product's removal queues a delete for reboot and the new install's replacement is also deferred, the delete could win and leave no file. Please check the ordering of the delete and replace operations forsystem.vhdin the major-upgrade sequence, and what the MSI does when it can't overwrite it. If it holds up, the fix would be to shut the VM down before upgrading, or to have the installer verify and re-lay the file after the reboot.Secondary problem: a leftover Store-package stub (
MicrosoftCorporationII.WindowsSubsystemForLinux_3.0.5.0_x64__8wekyb3d8bbwe, containing onlywsl.exeplus manifest) stays registered.winget install Microsoft.WSLthen fails with0x80073CFB("same identity as an already-installed package but the contents are different"), and removal fails with0x80073CF1. This blocks the reinstall route suggested earlier in this thread.Fix that worked (no data loss):
msiexec /fa {8ACC61B3-7BB9-4E69-9382-B0F4AA8F2677} /qnrestoredsystem.vhdfrom the cached MSI. Distro registrations and VHDXs were untouched, and all distros started afterwards.wsl --updateand winget could not do this.Suggestions:
wsl --updatecheck forsystem.vhdandtools\*after install and repair automatically.wsl.exeprint an actionable "installation incomplete, repair WSL" message whensystem.vhdis missing, instead of onlyERROR_FILE_NOT_FOUND.The MsiInstaller events above are from the Application log. I can add more detailed repair log if its is useful.
I thought for a moment I lost all my wsl installs, luckily i saw the vhdx avail still on my drives and was able to restore. Hopefully this can be fixed in the future updates so other user don't start over with a new install thinking they lost the old ones.