Error: 0x80370109 The operation timed out because a response was not received from the virtual machine or container.

[Alisoltan82]

Windows Version

Windows 11 Home

WSL Version

Default Version: 2

Are you using WSL 1 or WSL 2?

• [X] WSL 2
• [ ] WSL 1

Kernel Version

2

Distro Version

ubuntu 2204.3.49.0

Other Software

Docker Desktop 4.34.2

Repro Steps

just A windows update

Expected Behavior

docker run

Actual Behavior

Diagnostic Logs

ensuring main distro is deployed: deploying "docker-desktop": importing WSL distro "The operation timed out because a response was not received from the virtual machine or container. \r\nError code: Wsl/Service/RegisterDistro/CreateVm/HCS_E_CONNECTION_TIMEOUT\r\n" output="docker-desktop": exit code: 4294967295: running WSL command wsl.exe C:\WINDOWS\System32\wsl.exe --import docker-desktop <HOME>\AppData\Local\Docker\wsl\main C:\Program Files\Docker\Docker\resources\wsl\wsl-bootstrap.tar --version 2: The operation timed out because a response was not received from the virtual machine or container. 
Error code: Wsl/Service/RegisterDistro/CreateVm/HCS_E_CONNECTION_TIMEOUT
: exit status 0xffffffff
checking if isocache exists: CreateFile \\wsl$\docker-desktop-data\isocache\: The network name cannot be found.```

cann't reinstall ubuntu as well

wsl --shutdown doesn't solve that
shutdown windows features virt machines and subsystem --nothing
reinstalling docker nothing
windows repair update nothing
bios system VM enabeled
whatever I try it gives no response.

anybody familier with such problem kindly provide your feedback or possible solutions

[github-actions[bot]]

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](https://github.com/Microsoft/WSL/blob/master/diagnostics/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](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) 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:

• WSL Not longer loading (#12093), similarity score: 0.77
• Can't run WSL2 and it returns Error code: Wsl/Service/CreateInstance/CreateVm/HCS_E_CONNECTION_TIMEOUT (#12094), similarity score: 0.75

Closed similar issues:

• WslRegisterDistribution failed with error: 0x80370110 and 0x8000ffff (#11145), similarity score: 0.77
• WSL2 failed to run, no response from virtual machine or container (#7351), similarity score: 0.76
• WSL start-up attempts fail (time-out / -1 / exited 4294967295 / 0x80370109) (#7428), similarity score: 0.76

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

[Alisoltan82]

Error: 0x80370109 The operation timed out because a response was not received from the virtual machine or container.

Press any key to continue...```

[m1adow]

Same here 🫠

[gilberto-BE]

I am having the same issue, it started after the latest windows update.

[efimovvlad]

I have the same issue. I tried everything to fix the problem. In the end, the problem was solved after the Windows update of 09/27/2024 was rolled out. But after that, a new problem appeared in Windows: "start menu isn't working"

[AlexLovser]

The same issue after latest Windows update.

But what really worked for me is 1) wsl.exe --set-default-version 1 2) wsl.exe --install -d Ubuntu 3) wsl.exe --set-default-version 2

It still doesn't work on Docker, but at least the wsl responds and work.

[Varun0o]

I am having the same issue

[Exisfar]

Hello everyone. I've found the reason of this issue. It is because the last update (KB5043145) of Windows breaks WSL2. I delete the update and restart then I am able to connect to WSL2.

KB5043145 breaks WSL2

[ShunyiYang]

Same question

[ShunyiYang]

The same issue after latest Windows update.

But what really worked for me is

1. wsl.exe --set-default-version 1
2. wsl.exe --install -d Ubuntu
3. wsl.exe --set-default-version 2

It still doesn't work on Docker, but at least the wsl responds and work.

That works to me! At least I could use wsl terminal in VScode. Thanks a lot!

[Varun0o]

Hello everyone. I've found the reason of this issue. It is because the last update (KB5043145) of Windows breaks WSL2. I delete the update and restart then I am able to connect to WSL2.

KB5043145 breaks WSL2

Hey Exisfar, Thanks to your solution, The WSL2 issue I had is fixed. Appreciate your help!

[daryllmoya]

Hello, need some urgent help, I cannot uninstall that update.

[Alisoltan82]

Hello everyone. I've found the reason of this issue. It is because the last update (KB5043145) of Windows breaks WSL2. I delete the update and restart then I am able to connect to WSL2.

KB5043145 breaks WSL2

work - great!

this is a brilliant solution to remove the exact update file , as per attched image 'KB5043145" and mentioned by @Exisfar

[AlexLovser]

Hello everyone. I've found the reason of this issue. It is because the last update (KB5043145) of Windows breaks WSL2. I delete the update and restart then I am able to connect to WSL2.

KB5043145 breaks WSL2

work - great!

this is a brilliant solution to remove the exact update file , as per attched image 'KB5043145" and mentioned by @Exisfar

Thank you bro, probably its the only one solution here.

[boskee]

Thank you for this. Uninstalling the update fixed the issue.

[PraveenRajPurak]

Thanks a lot sir. The latest update (KB5043145) had done something to wsl. I uninstalled the update and now it works well. I tried to re-install docker, wsl --shutdown, restarting system, manually install distro(which won't even run). But none of these worked. Only uninstalling the latest windows update worked.

[thamp59]

Uninstalling the update fixed the issue for me as well

[OneBlue]

Sharing the instructions I posted https://github.com/microsoft/WSL/issues/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 secure@microsoft.com )

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)