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

WSL will not launch after hibernation #9396

Closed
1 of 2 tasks
JustThat70 opened this issue Dec 24, 2022 · 3 comments
Closed
1 of 2 tasks

WSL will not launch after hibernation #9396

JustThat70 opened this issue Dec 24, 2022 · 3 comments

Comments

@JustThat70
Copy link

Version

Microsoft Windows [Version 10.0.19045.2364]

WSL Version

  • WSL 2
  • WSL 1

Kernel Version

5.10.102.1

Distro Version

No response

Other Software

No response

Repro Steps

I believe this may be related to #9387 and #9301

I initially updated wsl using wsl --upgrade but then ran into the SSH issue ( #9231) so I uninstalled WSL completely and reinstalled from the control panel plus the kernel upgrade.

After hibernation, wsl will refuse to launch at all. Even commands such as wsl --status will simply hang.

I cannot use the taskkill workaround as there is no wslservice to kill. Only a reboot clears the problem

Expected Behavior

wsl should work, even after hibernation

Actual Behavior

The attached logs were taken from Windows Terminal Version: 1.15.3465.0 when trying to launch a new tab set to launch wsl with the following command C:\WINDOWS\system32\wsl.exe -d fedora36

WslLogs-2022-12-23_01-09-46.zip

Diagnostic Logs

No response

@JustThat70
Copy link
Author

JustThat70 commented Dec 26, 2022

Additional information: I've discovered the LxssManager service gets stuck in "Stopping" status and cannot be killed without shutting down Windows. At least, that is what the warning says. However, I've found that this can be done without issue (at least a few times). This does allow wsl to work again

image

Please let me know if additional information or logging would be helpful

@OneBlue
Copy link
Collaborator

OneBlue commented Dec 27, 2022

/dupe #9301

@ghost
Copy link

ghost commented Dec 27, 2022

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!

This issue was closed.
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

2 participants