WSL Bash doesn't start

Question

I have been using Windows 10's Windows Subsystem for Linux bash (Ubuntu via Microsoft Store) in the last few weeks, no problem, awesome feature, couldn't be happier.

But today it suddenly stopped working. Typing bash just does nothing on the command line (cmd and PowerShell), as if it would be waiting for something. It doesn't crash or output an error message, but just keeps showing a blinking cursor.

(Cursor not visible on screenshot, it is a blinking _ on the next line after bash)

Task manager shows both command lines at 0% CPU with a "Microsoft Bash Launcher" process also at 0% CPU:

Any idea how to debug and fix this?

Update: After a few manual restarts and one "crash" (I think explorer.exe stopped, and didn't really come back after killing the process after a prompt) it now works again for now.
I had the problem a few weeks before (where I fixed it be reinstalling WSL), so I assume it will reappear sooner or later.

I would uninstall and reinstall `WSL Ubuntu`, I normally would suggest you reset it, but that requires a working instance. — Ramhound, Dec 08 '17 at 20:04
Some really smart folks seems to have found a solution to the problem. Check out the [solution here](https://github.com/Microsoft/WSL/issues/849#issuecomment-252053937). — Vinayak, Dec 08 '17 at 20:15
In order to uninstall the WSL you have to use [wsl-config](https://docs.microsoft.com/en-us/windows/wsl/wsl-config) — Ramhound, Dec 08 '17 at 20:29
@Biswa No, exact same behaviour for `wsl.exe` and `ubuntu`. Also when running PowerShwell or `cmd` as Administrator. — janpio, Dec 09 '17 at 15:26
@Ramhound Thanks for the link to `wsl-config`, but I want to avoid re-installation if possible. Get a working setup was not easy, and to be honest I have no idea how to recreate it. Will take better notes if I really find no other solution though. — janpio, Dec 09 '17 at 15:30
So did you attempt the pagefile solution. If you didn’t then you are out of options. — Ramhound, Dec 09 '17 at 15:53
"Unfortunately" (I am actually pretty happy about it for now...) after a few manual restarts and one "crash" it now works again for now. I had the problem a few weeks before (where I fixed it be reinstalling WSL), so I assume it will reappear sooner or later. — janpio, Dec 09 '17 at 18:16
Do you have [detailed logs](https://github.com/Microsoft/WSL/blob/master/CONTRIBUTING.md#8-detailed-logs) we can review? — Jaime, Aug 08 '18 at 21:31
Looks like a duplicate of https://stackoverflow.com/questions/44049070/bash-on-ubuntu-on-windows-not-starting — Eyal Roth, Oct 04 '18 at 17:53
@EyalRoth: Indeed ... although this seems the more appropriate site. — GreenMatt, Feb 12 '19 at 23:06

score 56 · Answer 1 · edited Dec 19 '20 at 16:45

56

Try to do a full reboot of Windows10, hold Shift, and click “Restart.”

Normal reboot/shutdown action in the start menu will not shutdown Windows 10 fully, for the “fast boot” mechanism saves memory from the last session. The other answer mentioned changing system settings which make Windows 10 doing a full reboot, it works, but unnecessary.

By holding the Shift key and click the “Restart” in the start menu, Windows 10 will go into advanced restart mode, choose “Shutdown” from the menu. Then start normally again.

edited Dec 19 '20 at 16:45

Giacomo1968

53,069
19
162
212

answered Jul 06 '19 at 14:11

BOYPT

671
5
4

4

Thank you for this! I didn't have to change any settings, and this worked for me. – Archenoth Sep 17 '19 at 20:33
1

Worked for me too. I wish they fix this though – Geoffrey Hug Oct 30 '19 at 01:09
1

I got into maintain mode and clicked the special shutdown button, but when I booted back up bash still wouldn't start. – Maximillian Laumeister Dec 18 '19 at 17:37
5

Sure, reboot every time it gets stuck. Classic windows xD – Danny Lo Mar 09 '20 at 22:43
1

It works, but the problem will happen again eventually – mathiasfk Apr 06 '20 at 11:53
3

Thank You! It worked! Posted this issue on GH: https://github.com/microsoft/WSL/issues/5503 – Karan Singh Jun 29 '20 at 07:17
Worked for me as well. – optimus_prime Dec 11 '20 at 13:19
Advance restart menu? – Smart Manoj Dec 18 '20 at 17:53
2

Nope. As it turns out, rebooting doesn't fix every problem :) – steve Feb 11 '21 at 14:11
This solution worked for me. – ironywrit Jul 19 '21 at 15:31

score 14 · Answer 2 · edited Mar 17 '19 at 18:45

14

As discussed on https://github.com/Microsoft/WSL/issues/849 by user imkimchi the steps for solving this issue are:

Run windows + R

type SystemPropertiesAdvanced

click settings in performance group

In advanced tab, click Change under Virtual Memory and deselect the automatically manage paging file size for all drives

Select custom size and enter 800 for initial size, 1024 for maximum size.

Apply changes and restart.

edited Mar 17 '19 at 18:45

SpookyGengar

103
2

answered Feb 14 '19 at 19:47

enharmonic

309
2
11

3

This is not a complete solution. I suspect changing the page file management itself causes WSL to start working again. Mine got stuck, and I got it working after reading this answer, but then after a month or so, it got stuck again. I reverted my virtual memory to "System Managed", and WSL started working again. I don't know what to make of it :-| – kumarharsh Apr 03 '19 at 06:55
1

When I went to this window I already had almost 32gb of RAM allocated... so I think this is not the solution. – Jim Oct 26 '20 at 13:48
When I restart my PC, my WSL instance usually starts working again without having to change this. ¯\\_(ツ)_/¯ – Qwerty Feb 23 '22 at 17:31

WSL Bash doesn't start

2 Answers2

Linked