Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HCS_E_CONNECTION_TIMEOUT after drivers update or BIOS virtualization disabled & enabled again #9560

Closed
1 of 2 tasks
HonzaKopecky opened this issue Jan 30, 2023 · 2 comments
Closed
1 of 2 tasks

Comments

@HonzaKopecky
Copy link

HonzaKopecky commented Jan 30, 2023

Version

Windows version: 10.0.22621.1105

WSL Version

  • WSL 2
  • WSL 1

Kernel Version

5.15.79.1

Distro Version

Ubuntu 18.04

Other Software

WSL version: 1.0.3.0
Kernel version: 5.15.79.1
WSLg version: 1.0.47
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.1105

Repro Steps

wsl.exe

Expected Behavior

Expecting the distro to startup just fine.

Actual Behavior

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

I tried to disable & enable the Virtual Machine Platform and Windows Hypervisor Platform several times without any success. I also tried installing another distro but the installation never finishes with the same error code. Also tried disabling & enabling virtualization in BIOS.

I also tried to mount the .vhdx drive in case it was corrupted but the mount command never finishes. Also, it doesn`t look like corruption of the drive since a fresh install fails too. I am also not aware of anything advanced I did inside of the distro since it worked flawlessly.

Some updates/driver updates were done since the distro worked okay. Unfortunately, I don't have a backup to go back to.

Diagnostic Logs

https://drive.google.com/file/d/18X-VQVoXZSp6Kv_0g7SFwG2zvg_MHtoK/view?usp=sharing

@ghost
Copy link

ghost commented Jan 31, 2023

Can you rerun log collection from before starting WSL?

@HonzaKopecky
Copy link
Author

Hello @pmartincic, I am sorry. I can no longer replicate the issue since I had all my work tools installed in the WSL, so I had to completely uninstall WSL, reinstall it again and create a new distro. Then I had to manually recover necessary data from the .vhdx virtual drive. It was hell of a few days. Anyway, let's close this now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant