WSL: [wsl2] Import failed with: The operation timed out because a response was not received from the virtual machine or container.
Please fill out the below information:
-
Your Windows build number: 19018
-
What you’re doing and what’s happening:
Sometimes (very rarely, but it happens) registering a distro withwsl --import <...> --version=2fails withThe operation timed out because a response was not received from the virtual machine or container.. After that, wsl seem totally unusable (wsl -l -vhangs). I can confirm that the machine on which I last saw the error has no file encryption/compression enabled. -
What’s wrong / what should be happening instead: wsl --import should work reliably, and errors should not put wsl in an unstable state.
-
For WSL launch issues, please [collect detailed logs]: The issue happened on a CI machine and it happens randomly and rarely, so I am unable to get detailed logs for that.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 6
- Comments: 27 (6 by maintainers)
This started happening to me after an upgrade to Windows 11.
I face the same issue as well after upgrading to windows 11.
@simonferquel - Thanks, I was able to confirm this is an issue we have fixed and are working on backporting to 19041.
i was working for git connection to wsl that i found this error too…ouuuuch… The operation timed out because a response was not received from the virtual machine or container and i cant use wsl --user root …i want only ubuntu desktop …why windoes dont let me for it by wsl…lool
What worked for me is - install wsl again in windows 11 by running this command in cmd/windows powershell : wsl install and verify the version of wsl using this command: wsl --list --online Restart docker desktop and voila, it worked 👍
Ok, let me ping @StefanScherer so that we find a way to enable at least a remote powershell to those machines and we’ll monitor those kind of errors, and try to get dumps if we see this happen in the coming days