You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Console opens only after restart, then stops #4047
opening console works only after reboot, you can open OpenSuse or Ubuntu console or type bash in cmd and all works fine, after some use if you close all windows with console you can't open again, say you open OpenSuse42.3 the window will show up but there is no prompt, if you type bash in cmd, the command will start execution and hang, no prompt will show up.
Seems to be distro unrelated as both ubuntu and opensuse are affected.
What's wrong / what should be happening instead:
Prompt never shows up, should show up after opening a console window or execution command in cmd/powershell
Reacted by harmangakhal, bigxd123, Alexej Kubarev, jgoeglein, Adrián Montesinos González, Shaun Luttin, the7threvival, Gabriel Dugny and Slava I. Maslennikov
LxssManager is running. It fails to stop/restart. Tried launching bash as admin and non-admin, no difference. I've been using it for months without issue. Suddenly started happening this week.
Thanks. This is an issue that I've been debugging for a while. In the meantime, to get back to a working state if you kill the svchost.exe that is running the LxssManager service. You can get this pid via the services tab of task manager. You can avoid this issue by leaving a window open, or launching something in the background like a detached tmux session.
ok, i will reboot i guess and then just keep a shell open. let me know if there is anything else you'd like me to try before rebooting and losing this broken state?
after restart i can start bash. but then if i close it, and try to open again it hangs again. once again can't kill the svchost process or take a dump of it, getting access denied.
ugh, now bash starts again after closing (not something i thought i'd complain about!) i collected traces, but guessing they aren't particularly helpful?
Found this thread while having the same issue. Ran 3 log traces as described. Adding additional logs in case they help.
Surface Pro 6. Version 10.0.18362 Build 18362
I first ran Ubuntu directly. After that, I attempted to run bash from Powershell with the same result (screenshots below). I waited roughly a minute for each attempt.
+1 cannot open nano or vim
Terminal appears to be fine first, but starting nano or vim results in a blanc black screen.
Need to then hit CTRL+X to get my prompt back, this also displays some zombie-nano content: the content of the file I was trying to open in nano + a grey "GNU nano 4.8" header - but at the bottom I am back at the command prompt.
reboot does not resolve the issue
WSL1 Ubuntu 18.04 LTS stopped working today after I installed Debian in another WSL1 distro using lxrunoffline. The other WSL distros (including Debian) continue to work.
Nothing helps so far:
Disabling/Enabling WSL Feature
Stopping lxssmanager and starting again
Renaming .bashrc in the Ubuntu WSL distro using powershell bash
changing the WSL distro start user back to root (id 0)
I have the feeling this distro is lost. It is only 1 month away from EOL for Ubuntu 18.04 LTS, so I may as well leave the ship to a new distro.
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.
Activity
bigxd123 commentedon Jun 24, 2019
same problem
dfeinzeig commentedon Jul 11, 2019
same problem. any updates? this is ridiculous. i use this to make a living.
benhillis commentedon Jul 11, 2019
What state is the LxssManager service in while this is happening?
dfeinzeig commentedon Jul 11, 2019
LxssManager is running. It fails to stop/restart. Tried launching bash as admin and non-admin, no difference. I've been using it for months without issue. Suddenly started happening this week.
benhillis commentedon Jul 11, 2019
If you "sc stop lxssmanager" from admin, does the service stop or does it get stuck in the "stopping" state?
dfeinzeig commentedon Jul 11, 2019
benhillis commentedon Jul 11, 2019
Thanks. This is an issue that I've been debugging for a while. In the meantime, to get back to a working state if you kill the svchost.exe that is running the LxssManager service. You can get this pid via the services tab of task manager. You can avoid this issue by leaving a window open, or launching something in the background like a detached tmux session.
dfeinzeig commentedon Jul 11, 2019
I get access denied message when trying to kill that svchost process
benhillis commentedon Jul 11, 2019
From task manager?
dfeinzeig commentedon Jul 11, 2019
yes, end task from task manager and also from taskkill on cmd as admin
benhillis commentedon Jul 11, 2019
Interesting... I can do that on my machine with no issues. My other workarounds will still work for you though as I diagnose this issue.
dfeinzeig commentedon Jul 11, 2019
ok, i will reboot i guess and then just keep a shell open. let me know if there is anything else you'd like me to try before rebooting and losing this broken state?
benhillis commentedon Jul 11, 2019
If possible, a dump of the service might be useful, but if you cant kill it it's unlikely you'll be able to collect a memory dump.
dfeinzeig commentedon Jul 11, 2019
nope, no luck also get access denied. next time it happens i can try again.
dfeinzeig commentedon Jul 11, 2019
after restart i can start bash. but then if i close it, and try to open again it hangs again. once again can't kill the svchost process or take a dump of it, getting access denied.
5 remaining items
dfeinzeig commentedon Jul 11, 2019
k, np, brb
dfeinzeig commentedon Jul 11, 2019
ugh, now bash starts again after closing (not something i thought i'd complain about!) i collected traces, but guessing they aren't particularly helpful?
benhillis commentedon Jul 11, 2019
Yeah I'd need a trace of the repro. In the past is it possible you waited about 5 minutes before attempting to re-launch?
dfeinzeig commentedon Jul 11, 2019
when i tried a few minutes ago i successfully launched it, tried
uptime, closed it, and then immediately tried to relaunch but it failedjgoeglein commentedon Jul 14, 2019
Found this thread while having the same issue. Ran 3 log traces as described. Adding additional logs in case they help.
Surface Pro 6. Version 10.0.18362 Build 18362
I first ran Ubuntu directly. After that, I attempted to run bash from Powershell with the same result (screenshots below). I waited roughly a minute for each attempt.
lxcoreLogs.zip
jgoeglein commentedon Sep 15, 2019
An update to try for anyone else coming along - I removed BitDefender antivirus and haven't had this issue since.
arsdever commentedon Oct 24, 2020
Any progress made on this scope? Still happens on my machine
MerzDaniel commentedon Mar 2, 2021
Also (or again) hangs with the most recent windows update KB4023057 . I have no HyperV installed. Clean restart fixed it
stemabo commentedon Nov 29, 2021
+1 cannot open nano or vim
Terminal appears to be fine first, but starting nano or vim results in a blanc black screen.
Need to then hit CTRL+X to get my prompt back, this also displays some zombie-nano content: the content of the file I was trying to open in nano + a grey "GNU nano 4.8" header - but at the bottom I am back at the command prompt.
reboot does not resolve the issue
lafloresb commentedon Jan 6, 2023
The best solution that always worked for me was to:
Sieboldianus commentedon Feb 9, 2023
WSL1 Ubuntu 18.04 LTS stopped working today after I installed Debian in another WSL1 distro using lxrunoffline. The other WSL distros (including Debian) continue to work.
Nothing helps so far:
lxssmanagerand starting again.bashrcin the Ubuntu WSL distro using powershell bash0)I have the feeling this distro is lost. It is only 1 month away from EOL for Ubuntu 18.04 LTS, so I may as well leave the ship to a new distro.
sanba-anass commentedon Jun 18, 2023
u saved my day !!!!!!!!! thank u so much
microsoft-github-policy-service commentedon Jun 20, 2024
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!