Wsl/Service/CreateInstance/CreateVm/HCS/ERROR_FILE_NOT_FOUND on 2.4.11.0

[viccie30]

Windows Version

Microsoft Windows [Version 10.0.22631.4890]

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

Any (Fedora Rawhide, Debian Bookworm, Podman machine)

Other Software

No response

Repro Steps

Try to run anything in WSL, whether interactive or not.

Expected Behavior

WSL working

Actual Behavior

> wsl
Het systeem kan het opgegeven bestand niet vinden.
Foutcode: Wsl/Service/CreateInstance/CreateVm/HCS/ERROR_FILE_NOT_FOUND

Diagnostic Logs

WslLogs-2025-02-18_10-37-00.zip

Extra

According to #12566 this error should be fixed in 2.4.11, but it is not for me. It only started appearing in 2.4.10.

[github-actions]

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:

• Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/ERROR_FILE_NOT_FOUND upon executing WSL (#9840), similarity score: 0.79
• WSL distro fails to start with "Error code: Wsl/Service/CreateInstance/CreateVm/HCS/ERROR_PATH_NOT_FOUND" (#11677), similarity score: 0.79
• WSL Error code: Wsl/Service/CreateInstance/CreateVm/HCS/ERROR_MOD_NOT_FOUND (#12242), similarity score: 0.78

Closed similar issues:

• wsl2 fail to startup with Wsl/Service/CreateInstance/CreateVm/HCS/ERROR_FILE_NOT_FOUND (#12566), similarity score: 0.83
• Error code: Wsl/Service/CreateInstance/CreateVm/HCS/0x8007000d (#12042), similarity score: 0.81

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

Diagnostic information

Detected appx version: 2.4.11.0
Detected user visible error: Wsl/Service/CreateInstance/CreateVm/HCS/ERROR_FILE_NOT_FOUND

[viccie30]

According to #12566 this error should be fixed in 2.4.11, but it is not for me. It only started appearing in 2.4.10.

Downgrading to 2.4.8 then upgrading back to 2.4.11 seems to have solved the problem again.