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.
Best Answer
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.