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

Windows Version

Windows 11 Home

WSL Version

Default Version: 2

Are you using WSL 1 or WSL 2?

  • 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

Screenshot 2024-09-28 150934_2

Screenshot 2024-09-28 151440_2

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

About this issue

  • Original URL
  • State: open
  • Created 2 years ago
  • Reactions: 10
  • Comments: 18

Most upvoted comments

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

img

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.

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”

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

Same here 🫠

I am having the same issue

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

Press any key to continue...```

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 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:

Closed similar issues:

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

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

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

ef990bc53c0ee46fe645eb8773c4d72

work - great!

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

Screenshot 2024-09-29 141604_55

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

ef990bc53c0ee46fe645eb8773c4d72

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