WSL2 terminal won't start #5912
Comments
|
I have the same problem; after upgrading to 20211.1000 Wsl2 it stopped working properly; I tried a few steps to correct the problem. |
|
I have the same problem after upgrading to 20211.1000 Wsl2，but reinstall wsl not work for me |
|
After countless unsuccessful attempts to fix WSL2 under v20211.1000, there was no other way but to reinstall W10 from scratch.
|
|
Seems still not fix in 20215.1000 |
|
still not fix in 20215.1000 |
|
#5902 (comment) |
|
guys, I managed to fix it just by uninstalling WSL2 and installing again. Just follow common Microsoft guide: Run in PowerShell as admin: DISM /online /disable-feature /featurename:VirtualMachinePlatform /norestart Reboot, and again: dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart Reboot, and again: wsl --set-default-version 2 Note: you won't lose your Linux subsystem settings or files. This happened two times with me, both solved the same way, now it's apparently stable. And now I've just updated to build 20215, let's see how it goes... |
No, it's not give any result |
This did not work. |
|
This is a critical issue and affects my work from day to day. WSL is simply useless. Two critical things that should be addressed are followng: (1) WSL is not working, fix it. Until those issues are seriously fixed, I am running Linux natively for now. |
|
maybe I should use Ubuntu natively |
|
@xexpanderx @woodygithub can someone confirm that this update fixes the problem ? thx! |
|
insider 20221.1000 dont work |
|
Can confirm with 20221.1000, it is still not working. Same symptoms as before. |
|
20221.1000 is not working. Even |
|
@wadjeroudi what update |
|
Is fix for me in 20226 |
|
Yes, me to in 20226. Now, just the network issue, and WSL can finally be used. |
|
Unfortunately, it does not work again. I just did a restart of the computer. Back to square zero... Not sure if 20226 really did anything related to this problem. Again, WSL does not start, no errors, no warnings, nothing is printed out, it just does not start. |
|
Here is a demonstration: https://www.youtube.com/watch?v=YShMixfmrIM&feature=youtu.be |
|
WSL2 can be used in 20231 |
|
No, it does not work. |
|
Any solution for this issue yet ? I'm having the same problem, after multiple attempts to restart WSL 2 using :
none of the WSL 2 commands work, just hanging in the terminal, very annoying. |
|
Nope, it is amazing they do not prioritize this bug. |
|
This is a critical issue :
FYI : it worked for me for some time and I confirm it's a really cool feature, BUT this kind of issues makes it UNFORTUNATELY unusable, especially if one is working with Docker. |
|
Same issue here, the weird thing is that some terminals are still working, but new ones are not starting up and showing only the cursor. Even my docker containers are still running without problems which have been spun up when wsl2 was stil working properly |
For me this solution worked ... thanks! |
|
Hi! I just find a very weird solution. If you happen to have Virtualbox installed, that may in a very weird way contribute to WSL2 not starting. Simply uninstalling Virtualbox did it for me.... There seems to be more people fixing this problem by uninstalling Virtualbox: #5982 and #5845. This definitely is not a "solution", but since Microsoft does not give a crap about this problem, this is at least a workaround. |
|
just had this problem as well, resolved the issue by following the steps provided on @Gstar1525 comment |
|
Some updates came to Windows last night and broke me WSL2 in this way. Can't see file system, terminal won't load. This solution fixed it for now.
|
Thanksss, Run in PowerShell as admin: DISM /online /disable-feature /featurename:VirtualMachinePlatform /norestart Reboot, and again: dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart Worked for me. Thank you. |
|
If anyone else gets this, for some reason for me, running WSL just hangs as the others described, but if I type: |
|
Very annoying. Thought I had messed up my installation somehow until I stumbled upon this thread and realized it's a general issue. I have Docker 4.7.1 and I use WSL2 (wsl --set-default-version 2) with Ubuntu 20.04 (latest updates). Steps I follow to fix the issue:
Everything works for a couple of hours and then it hands again. This issue started happening about a month ago. Update: It turned out that WSL goes haywire when I have multiple VSCode instances open and I run load-tests on local constellations I have launched through docker-compose in WSL2. I increased the memory I allocate to WSL via .wslconfig to 12GB (up from 4GB) and the problems I described above disappeared at least for now |
|
|
it's still happened, why this issue were closed? |
|
July 2022, still not fixed. Had to reinstall whole subsystem... |
Over one year, still getting not fixed notifs from this issue. I switched to macOS eventually (not the only reason but very significant one). |
|
This is pissing me off, I cant do my work since wsl is not starting. I had this problem since 2020. When are you gonna fix this issue? |
|
For me this wasn't an issue with windows but a conflict with docker desktop. uninstalling docker desktop and reinstalling immediately fixed it. Haven't restarted yet to ensure the fix is permanent but I believe it may of had to do with incorrect installation procedures on my part. |
|
How can it be that this still is not fixed??????? I have windows11 21H2 (Build 22000.978) with wsl kernel 5.10.102.1. This happened to me today. Ubuntu22.04 distro just will not start again! |
|
Still affected too... I deinstalled, reinstalled, rebooted etc and now I can access it. But not after every reboots :( |
|
I found a solution to my specific problem, I don't know if it's the same as the others in this thread. My issue was that the terminal was stuck in the black screen with the cursor blinking. What I had is something that I've installed that edited my .bashrc file and put something that was blocking!
Go to the bottom of the file and check if there isn't anything strange, save the file and try again. |
|
@hwebb Great! It works for me! After I removing the NVM related startup scripts, WSL recovered. export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion" # This loads nvm bash_completion |
|
Those last two issues are not related with this problem I think, as WSL itself is not stuck in the "bash" case :) |
Actually it looks exactly like the OP, "WSL2 terminal won't start - just installed some pip packages and restart the PC. Now the terminal doesn't load. It keep blinking the cursor indefinitely." Which is exactly that, after installing a package, the cursor keeps blinking, so that means the terminal is loaded, he doesn't mention |
|
Well the rest of the thread converge on a WSL problem (see the OP post here #5912 (comment) ) which eventually leads to bug being closed without being fixed ( #5912 (comment) ) anyway this thread is lost, so you're right we might as well document anything that looks like it :) |
|
Just encountered this issue again. I think before running |
|
@hwebb - many thanks for your input here. This was the exact problem I had, too, and your fix worked perfectly. Much appreciated! |
|
Still a problem. |
Tried #5912 (comment) + #4084 (comment) |
|
Just for reference: I've had that problem several times when there were Windows Updates "pending". Just restarting the PC and applying the updates helped. |
Thank you very much, @hwebb ! This was exactly my problem. commented |
|
Run in PowerShell as admin: DISM /online /disable-feature /featurename:VirtualMachinePlatform /norestart Reboot, and worked for me. |
You save my day! Thanks! |
idk if this what fixed it but its fixed now i hope it doesnt break again because its a huge pain to re setup another wsl workespace and the git and ssh key and github now i am scared it will break on me the moment i need it so reliability is an issue here last time it broke i couldnt even acces my codebase and i didnt even push it to github i hope it doesnt break on me again |
This worked for me - issue was faulty Angular CLI installation that was trying to be loaded for autocompletion. |
This worked for me! thx! |
and others
After updating to build 20211, I worked for some minutes in Ubuntu 18.04 with WSL2. just installed some pip packages and restart the PC.
Now the terminal doesn't load. It keep blinking the cursor indefinitely.
The text was updated successfully, but these errors were encountered: