Can't run WSL2 and it returns Error code: Wsl/Service/CreateInstance/CreateVm/HCS_E_CONNECTION_TIMEOUT

[Eleron8]

Windows Version

Microsoft Windows [Version 10.0.22631.4249]

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.153.1-2

Distro Version

Can't run any commands within WSL due to connection timeout error.
But I have only one distro and it's ubuntu. I'm pretty sure it's 20.04 or 22.04 version

Other Software

No response

Repro Steps

I just got some update for Windows 11 and after that my WSL2 stopped working.
I turned on Windows features like Hyper-V, Containers and Windows Subsystem for Linux to try to fix that issue, but it didn't help anyway.
Still getting Error code: Wsl/Service/CreateInstance/CreateVm/HCS_E_CONNECTION_TIMEOUT each time

Expected Behavior

I want to be able to run WSL2 without getting timeout error.

Actual Behavior

I run wsl.exe command or run Ubuntu terminal from Windows apps, I'm getting the same result

wsl.exe

The operation timed out because a response was not received from the virtual machine or container.
Error code: Wsl/Service/CreateInstance/CreateVm/HCS_E_CONNECTION_TIMEOUT

Diagnostic Logs

I executed collect-wsl-logs.ps1 script to collect logs. I hope it will be helpful.
WslLogs-2024-09-28_10-18-26.zip

[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!

Closed similar issues:

• After Cumulative Update (KB5023706) WSL Started to generate time out error (#9795), similarity score: 0.84
• Wsl/Service/CreateInstance/HCS_E_CONNECTION_TIMEOUT (#10571), similarity score: 0.82
• WSL2 doesn't start (/HCS_E_CONNECTION_TIMEOUT) after installing Docker desktop (#10546), similarity score: 0.77
• Error code: Wsl/Service/CreateInstance/CreateVm/HCS/ERROR_MOD_NOT_FOUND after Windows update (#11736), similarity score: 0.77
• HCS_E_CONNECTION_TIMEOUT after drivers update or BIOS virtualization disabled & enabled again (#9560), similarity score: 0.77

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

Diagnostic information

Detected appx version: 2.2.4.0
Detected user visible error: Wsl/Service/CreateInstance/CreateVm/HCS_E_CONNECTION_TIMEOUT

[gilberto-BE]

I am hiving the same issue, also in my case it started after the latest windows 11 update.

[Eleron8]

I am hiving the same issue, also in my case it started after the latest windows 11 update.

if you find any solution, let me know. Tried many things but couldn't get any result.

[pakalnis]

if you find any solution, let me know. Tried many things but couldn't get any result.

I uninstalled windows update and WSL started to work... but Start button causes critical error now.

[pjacekm]

Same here, uninstalling the update KB5043145 fixed the issue for me. See also here.

[mkotyushev]

Same issue the WSL2 is broken after some updates, uninstalling the KB5043145 update helps, thanks @pjacekm

[daryllmoya]

How did you manage to uninstall the KB5043145, I am so frustrated right now.

I already ran some checks for corrupted file but there was none
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

[Rajneesh2008]

facing the same issue

[pakalnis]

How did you manage to uninstall the KB5043145, I am so frustrated right now.

https://support.microsoft.com/en-us/windows/how-to-uninstall-a-windows-update-c77b8f9b-e4dc-4e9f-a803-fdec12e59fb0

[daryllmoya]

How did you manage to uninstall the KB5043145, I am so frustrated right now.

https://support.microsoft.com/en-us/windows/how-to-uninstall-a-windows-update-c77b8f9b-e4dc-4e9f-a803-fdec12e59fb0

I wouldn't be using the terminal for uninstalling it if I haven't tried that already. It will show uninstalled, but after restart, it will still show as installed.

[aerkwannasak]

Same here, uninstalling the update KB5043145 fixed the issue for me. See also here.

This work ! Thanks

[MatCast]

Same happening here. Rolling back the update seems to have fixed the issue.

[bssrdf]

Same here. Almost gave up on it until found this thread. What's going on?

[OneBlue]

Sharing the instructions I posted #12087. If you hit this issue, please:

• Reproduce the issue by calling into wsl.exe and waiting about 5 seconds
• While WSL is booting, open task manager, select "System", right click -> "Create live kernel memory dump file" -> "Change - -
• memory dump settings" -> select "Capture Hypervisor pages", "include nonessential pages", "Capture user pages"
• Then go back to "System" -> right click, "Create live kernel memory dump file" -> "full live kernel memory dump"
• Share that file with us (either via Google Drive, OneDrive, or send to [email protected]

For this to work, the dump must be captured while WSL is in that "hung" state (once the error is displayed, you need to start wsl.exe again)

[jackheuberger]

@OneBlue I was able to reproduce the issue -- I just sent an email

[OneBlue]

Thank you so much @jackheuberger: It hasn't been forwarded to us yet. Would you mind telling the recipient to forward it to the WSL team ?

[jackheuberger]

@OneBlue Will do. I'm also msft internal and can send it to you directly. Feel free to ping me on Teams