Hi I'm an AI powered bot that finds similar issues based off the issue title.

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. Thank you!

Open similar issues:

• WSL 1.0.3 hangs forever (#9659), similarity score: 0.86

Closed similar issues:

• wsl.exe hangs on launching (#10710), similarity score: 0.88
• WSL 2 hangs on startup (#10296), similarity score: 0.86
• WSL2 freezes/timeout upon launch (cannot start) (#9942), similarity score: 0.85
• WSL2 hangs on launch (#5756), similarity score: 0.85

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

from wsl.

My wsl.exe --status is still hanging. I think this means I've experienced two separate issues here:

1. Log 1 is the system being slow to respond
2. Logs >= 2 is wsl stuck indefinitely.

And just to provide as much helpful information as I can, I'm going to create yet another WSL log right before I restart:
WslLogs-2024-01-23_17-04-47.zip

It might help to show the times in which I created these logs:

re: the bot's links

As far as I can tell those issues weren't exactly the same as mine. This one appears to have the most helpful information, mainly the second half of the comments: #4144 I use the word "appears" because I tried one and it didn't fix the problem:

I looked into my services.msc and saw that LxssManager was stuck in a "Stopping" state.

After I killed it, I opened a new wsltty terminal and it's hanging like before. I don't plan to stick around long enough to see if it eventually finishes; I'm going to restart my computer now.

from wsl.

I tried the other major suggestion from #4144

Managed to fix the issue by disabling all WSL related features, rebooting, then enabling them again and rebooting once more. Later I had to run wsl --set-default-version 2 again.

Disabled Hyper-V plus WSL -> reboot -> enable them again -> reboot solved my issue!

It did not fix the issue.

I ran sfc and dsim (sp?). The former found nothing. The latter found something and fixed it, but it did not fix the issue, even after restart.

from wsl.

Okay I decided to wsl --export and reinstall everything with these steps: https://gist.github.com/4wk-/889b26043f519259ab60386ca13ba91b

Everything was working fine with my new install. Then, I these last two steps, then the permanent hanging issue immediately came back:

1.

I modified my /etc/wsl.conf to change the user back to what it was (See https://learn.microsoft.com/en-us/windows/wsl/basic-commands#change-the-default-user-for-a-distribution )

2.

wsl --update.

It was this:

PS C:\Windows\system32> wsl --version
WSL version: 2.0.9.0
Kernel version: 5.15.133.1-1
WSLg version: 1.0.59
MSRDC version: 1.2.4677
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.3996

It became this:

PS C:\Windows\system32> wsl --version
WSL version: 2.0.14.0
Kernel version: 5.15.133.1-1
WSLg version: 1.0.59
MSRDC version: 1.2.4677
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.3996

Now I'm stuck at
PS C:\Windows\system32> wsl

WslLogs-2024-01-24_23-28-12.zip

It might be worth noting vmmem is running in the task manager again.

Without reinstalling WSL, I killed WSL in the task manager, unregistered my imported distro, reimported it, set the user to the original value. I'll report back if it happens yet again.

If it does happen again, next I'll try reinstalling WSL without running wsl --upgrade.

It seemed to be working all right until I noticed vmmem was using 1.5 gigs, so I ran wsl --shutdown. This command hung indefinitely. I don't know what's stopping it from completing because I don't see anything in my services.msc that are trying to stop and I don't see wsl mentioned in my task manager.

Guess I'll reinstall everything from scratch again.

from wsl.

okay I followed these steps again but skipped the wsl --upgrade step. I added one additional variable this time: I turned off the hyper-v feature and restarted and turned it back on again and restarted.

So far so good. Up to this point I could reproduce these problems in one tenth of the time and in one tenth of the attempts to trigger it. wsl --shutdown ran and completed instantly, too.

I'm willing to run wsl --upgrade to remove that last variable, but hopefully the log files have given enough information to troubleshoot.

from wsl.

/dumps

from wsl.

@OneBlue I've attached six log files throughout this thread. You can find them by searching for ".zip" in your browser. Let me know if they are missing information. Thanks

from wsl.

@OneBlue Hope you don't mind the second ping so soon. Let me know how else I can help, because I think I'm in a good position to do so!

from wsl.