WSL Hangs on launch (dupe / re-open of #6980 with logs) #7096
Labels
failure-to-launch
failure to launch
Comments
|
From #6980 , logs are at https://aka.ms/AAczgdt |
jodavaho
changed the title
|
@jodavaho - I do not have access to that link. Can you attach logs directly? |
|
I have access to those logs. @jodavaho can you please enable the debug console and share its output ? Add this to .wslconfig: Then run wsl --shutdown and restart wsl. |
|
Happy to. Where do I put that file? |
ghost
removed
the
2 tasks
|
@OneBlue Requesting completed instructions. |
|
In |
|
OK, I captured a successful startup. I'll post a failed one next time it hangs. |
|
Here's a frozen / hanging startup log: |
|
What "Tasks" remain (above on toolbar?) |
It's because the template has a checkbox for the WSL version. It thinks it's a task list. |
|
Have you tried a full PC restart? Try to restart from the start menu, but hold shift when you press, "Restart." This fixed my problem. I figured it out by trying to run Ubuntu from the wsl --system command. It spat out this error: "The operation timed out because a response was not received from the virtual machine or container.", which led me here. Hopefully it helps! |
|
A restart temporarily solves the problem -- In that I can then access WSL -- but doesn't really "solve" the problem. Hangs return. |
|
I have moved my WSL distro(the vhdx file) to a new drive by exporting it, then importing it(like in this article.) And I have not experienced any more hangs. This is nothing short of a hack and I think that there is probably something weird happening in WSL. Hopefully this "fixes" it. |
|
In my case, whenever the WSL2 terminal hangs when returning from the sleep mode
It fixes the issues but looking for a permanent solution than this kind of patchwork. |
|
I do make it work using the above steps, but recently it hangs and doesn't re-start. |
|
My team is seeing this issue, personally I have seen it on Windows 11. My steps to resolve are:
NOTE 1: Attempting to stop the process in Powershell using NOTE 2: Attempting to stop the process in Services.msc has no effect NOTE 3: I abandoned using the built-in task manager, not sure if that will also kill the process or not. |
|
I am also having this issue as of recently - My question is do any of you have anything like beyond privilege management (Or a PAM Auth soloution of any kind?) My issues seem to have started after that. |
|
I'm having this issue frequently these days. It seems to have something to do with open file handles, as processes (typescript in particular) start behaving strangely, and just this time, deleting a file in wsl or in windows resulted in the file reappearing in windows moments later--but when trying to delete the reappeared file in wsl, it couldn't find it (despite ls listing it). Maybe drive issues or something but my ssd reports no issues. I'll try to get some logs next time this happens. 2022-06-05 No definite additional info yet, but I have ~12 zombie node processes that are unkillable and definitely preventing wsl restart. My issue is less the launch part than shutdown/relaunch, because of things stopping responding. Current windows version/updates--but I'll try to find a more apt issue to tack my comment on. |
|
This might be a duplicate of #8170. Can someone collect log and share repro instruction if this is still happening with the latest Windows updates ? |
2 tasks
|
I am still experiencing this issue. After sleep, LxssManager gets into a "stopping" state. This breaks WSL and docker. pdowson-rsc's workaround instructions work. |
|
The PAM Privlage magament stuff i has severly broke windows - It ended up getting re-installed by our local IT, and i never found a soloution sorry @remoford |
|
Thank you @remoford. Unfortunately I'm not seeing anything that jumps out. Next time this happens, can you please share a dump of the LxssManager process ? |
|
I also have the same problem. When it occurs, I tell the lxssmanager service to stop (which hangs), then find the PID and kill its process tree in task manager. I don't know if this will help, but the last time I was in this state, before stopping the service and killing the PID, I ran the Does this message give anyone insight into what might be going on? The full output of |
2 tasks
2 tasks
|
This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request. Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Windows Build Number
Microsoft Windows [Version 10.0.21390.2025]
WSL Version
Kernel Version
Kernel version: 5.10.16
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps
Launch wsl application, via the WSL for Linux
Expected Behavior
WSL launches
Actual Behavior
WSL freezes
Diagnostic Logs
https://aka.ms/AAczgdt starting up WSL ubuntu
The text was updated successfully, but these errors were encountered: