Skip to content

WSL not working after windows update #13948

Open

Description

@heberleh2

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

  1. github-actions commented on Dec 20, 2025

    @github-actions
    Contributor

    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:

    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, 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'.

  2. heberleh2 commented on Dec 20, 2025

    @heberleh2
    Author
  3. github-actions commented on Dec 20, 2025

    @github-actions
    Contributor
    Diagnostic information
    Detected appx version: 2.6.3.0
    Detected user visible error: Wsl/Service/CreateInstance/CreateVm/MountDisk/HCS/ERROR_FILE_NOT_FOUND
    Detected user visible error: Wsl/Service/CreateInstance/CreateVm/MountDisk/HCS/ERROR_FILE_NOT_FOUND
    Detected user visible error: Wsl/Service/CreateInstance/CreateVm/MountDisk/HCS/ERROR_FILE_NOT_FOUND
    Detected user visible error: Wsl/Service/CreateInstance/CreateVm/MountDisk/HCS/ERROR_FILE_NOT_FOUND
    Detected user visible error: Wsl/Service/CreateInstance/CreateVm/MountDisk/HCS/ERROR_FILE_NOT_FOUND
    Found evidence of disk failing to attach. Error: 0xC0000034, Path: C:\Program Files\WSL\system.vhd
    Found evidence of disk failing to attach. Error: 0xC0000034, Path: C:\Program Files\WSL\system.vhd
    Found evidence of disk failing to attach. Error: 0xC0000034, Path: C:\Program Files\WSL\system.vhd
    Found evidence of disk failing to attach. Error: 0xC0000034, Path: C:\Program Files\WSL\system.vhd
    
  4. Ping-Hung commented on Dec 21, 2025

    @Ping-Hung

    Experiencing the same issue here, and here are my wsl logs

    WslLogs-2025-12-20_19-54-14.zip

  5. gorgsenegger commented on Jan 1, 2026

    @gorgsenegger

    Same for me, the vhd file is in C:\ProgramData\Microsoft\WSL, but the error message indicates that WSL seems to look in the wrong directory:

    Image

    Error message

    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
    
  6. gorgsenegger commented on Jan 1, 2026

    @gorgsenegger
  7. gorgsenegger commented on Jan 3, 2026

    @gorgsenegger

    Updating WSL from 2.6.2.0 to 2.6.3.0 solved the issue for me:

    C:\Users\bla>wsl --version
    WSL-Version: 2.6.2.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
    
    C:\Users\bla>wsl --update
    Es wird nach Updates gesucht.
    Windows-Subsystem für Linux wird auf Version 2.6.3 aktualisiert.
    
    C:\Users\bla>wsl --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
    

    Running WSL works again.

  8. trlef19 commented on Feb 6, 2026

    @trlef19

    error remains

  9. bstordrup commented on Feb 25, 2026

    @bstordrup

    Having the same issue.

    PS C:\Users\benny.tordrup> wsl --version
    WSL version: 2.6.3.0
    Kernel version: 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.7781
    
  10. shuaiyuanxx commented on Mar 19, 2026

    @shuaiyuanxx
    Contributor

    Thanks for the logs. The root cause across all reports is the same: system.vhd is missing from C:\Program Files\WSL\ after the 2.6.2.0→ 2.6.3.0 upgrade, 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

    wsl --shutdown
    wsl --update

    If it says no update is available, force a reinstall:

    wsl --install --no-distribution

    Step 2: If still broken, check for stale registry

    reg query "HKLM\Software\Microsoft\Windows\CurrentVersion\Lxss" /v SystemDistro

    If this returns a legacy path like C:\ProgramData\Microsoft\WSL\system.vhd, delete it:

    reg delete "HKLM\Software\Microsoft\Windows\CurrentVersion\Lxss" /v SystemDistro /f

    Then run wsl --shutdown and wsl --install --no-distribution again.

    Step 3: Verify

    dir "C:\Program Files\WSL\system.vhd"

    If the file exists, WSL should work normally.

  11. H37IX commented on Nov 21, 2026

    @H37IX

    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 with Failed to attach disk 'C:\Program Files\WSL\system.vhd' ... ERROR_FILE_NOT_FOUND (Wsl/Service/CreateInstance/CreateVm/ERROR_FILE_NOT_FOUND). wsl --version and wsl -l -v work, so the install looks healthy until a VM starts. kernel, init, initrd.img and artifacts.vhd under tools\ were present. system.vhd was absent, and a recursive search of C: found no copy.

    Timeline from the MsiInstaller log (local time, one day):

    • 06:12:28: MSI transaction begins (wsl.3.0.5.0.x64 (5).msi, which wsl --update had downloaded to %TEMP%). Earlier --update attempts on the previous day had left four more identical copies there. All five are byte-identical (SHA256 231....AA), match the MSI cached in C:\Windows\Installer, and the Authenticode signature is valid. So the package is not corrupt.
    • 06:14:35: event 1039, "The application tried to modify a protected Windows registry key \Software\Classes\Application".
    • 06:14:40: event 1038, "requires a system restart", for the old product, 2.7.3.0 (its removal side of the upgrade).
    • 06:15:06: event 11707, 3.0.5.0 "Installation completed successfully", then 1038/1029 again for 3.0.5.0: "Restart required ... The restart was deferred."
    • 06:15:57: the machine rebooted (LastBootUpTime).
    • After the reboot: system.vhd missing, no PendingFileRenameOperations left, no SystemDistro value under HKLM\...\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 File table lists system.vhd (758,039,040 bytes, component wsl, 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.vhd is 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 for system.vhd in 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 only wsl.exe plus manifest) stays registered. winget install Microsoft.WSL then fails with 0x80073CFB ("same identity as an already-installed package but the contents are different"), and removal fails with 0x80073CF1. This blocks the reinstall route suggested earlier in this thread.

    Fix that worked (no data loss): msiexec /fa {8ACC61B3-7BB9-4E69-9382-B0F4AA8F2677} /qn restored system.vhd from the cached MSI. Distro registrations and VHDXs were untouched, and all distros started afterwards. wsl --update and winget could not do this.

    Suggestions:

    1. Make wsl --update check for system.vhd and tools\* after install and repair automatically.
    2. Make wsl.exe print an actionable "installation incomplete, repair WSL" message when system.vhd is missing, instead of only ERROR_FILE_NOT_FOUND.
    3. Resolve the stub/identity collision so winget and the Store can reinstall cleanly.

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions