10

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.

enter image description here

(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:

enter image description here

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 8 '17 at 20:04
  • Some really smart folks seems to have found a solution to the problem. Check out the solution here. – Vinayak Dec 8 '17 at 20:15
  • In order to uninstall the WSL you have to use wsl-config – Ramhound Dec 8 '17 at 20:29
  • Is wsl.exe working? – Biswapriyo Dec 9 '17 at 8:02
  • @Biswa No, exact same behaviour for wsl.exe and ubuntu. Also when running PowerShwell or cmd as Administrator. – janpio Dec 9 '17 at 15:26
5

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

  1. Run windows + R
  2. type SystemPropertiesAdvanced
  3. click settings in performance group
  4. In advanced tab, click Change under Virtual Memory and deselect the automatically manage paging file size for all drives
  5. Select custom size and enter 800 for initial size, 1024 for maximum size.
  6. Apply changes and restart.
  • 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 :-| – kumar_harsh Apr 3 at 6:55

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.