Tjyylli

What is the definition of "Natural Selection"?

Excess Zinc in garden soil

Rejected in 4th interview round citing insufficient years of experience

Touchscreen-controlled dentist office snowman collector game

Can infringement of a trademark be pursued for using a company's name in a sentence?

How do anti-virus programs start at Windows boot?

Why do Australian milk farmers need to protest supermarkets' milk price?

Prove that the total distance is minimised (when travelling across the longest path)

What is the blue range indicating on this manifold pressure gauge?

Best approach to update all entries in a list that is paginated?

Word for a person who has no opinion about whether god exists

Is "history" a male-biased word ("his+story")?

Does Linux have system calls to access all the features of the file systems it supports?

Can you reject a postdoc offer after the PI has paid a large sum for flights/accommodation for your visit?

Question about partial fractions with irreducible quadratic factors

Time dilation for a moving electronic clock

"One can do his homework in the library"

Is it ok to include an epilogue dedicated to colleagues who passed away in the end of the manuscript?

Confusion with the nameplate of an induction motor

Deleting missing values from a dataset

What happens with multiple copies of Humility and Glorious Anthem on the battlefield?

dabei is pointing to what preposition or fact "Ich war gerade dabei die Tür abzuschliessen. Da hast du angerufen."

Humans have energy, but not water. What happens?

How to deal with a cynical class?

WSL Bash doesn't start

Bash on Windows / Windows Subsytem for Linux (WSL) not installing correctly / hangsBash doesn't work after Windows 10 updateWin10 WSL - No Ubuntu bootstrap when typing bashPc restarts randomly without bsod or memory dumpHow to understand or “debug” hanging / not starting `bash` from WSL?How to access Linux files in WSL (windows 10 fall creators update)?WSL ffmpeg BSoD KERNEL_SECURITY_CHECK_FAILURE when killing from PythonIn Ubuntu Bash WSL in Windows 10, how can I have my redis-server service start?WSL process causing DPC_WATCHDOG_VIOLATIONHow to remotely terminate bash shell processes but ensure history is saved?

7

2

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.

windows-10 bash windows-subsystem-for-linux windows-10-v1709

share|improve this question

edited Dec 9 '17 at 18:15

janpio

asked Dec 8 '17 at 19:44

janpiojanpio

2702620

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  

  
  
  
  

 | 
show 6 more comments

7

2

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.

windows-10 bash windows-subsystem-for-linux windows-10-v1709

share|improve this question

edited Dec 9 '17 at 18:15

janpio

asked Dec 8 '17 at 19:44

janpiojanpio

2702620

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  

  
  
  
  

 | 
show 6 more comments

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.

windows-10 bash windows-subsystem-for-linux windows-10-v1709

share|improve this question

edited Dec 9 '17 at 18:15

janpio

asked Dec 8 '17 at 19:44

janpiojanpio

2702620

share|improve this question

edited Dec 9 '17 at 18:15

janpio

asked Dec 8 '17 at 19:44

janpiojanpio

2702620

share|improve this question

edited Dec 9 '17 at 18:15

janpio

asked Dec 8 '17 at 19:44

janpiojanpio

2702620

asked Dec 8 '17 at 19:44

janpiojanpio

2702620

asked Dec 8 '17 at 19:44

janpiojanpio

2702620

2 Answers
2

active

oldest

votes

2

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, 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.

share|improve this answer

answered Feb 14 at 19:47

enharmonicenharmonic

336

add a comment | 

0

Here's what got it working for me:

1. Open CMD Prompt or PowerShell
   


2. Type bash and press enter.


3. When nothing happens, type ctrl+c.


4. Upon performing Step 3, you initialize your bash session, starting in your ~ (e.g. %user%) directory.

Hopefully this helps someone out there.

share|improve this answer

answered 20 mins ago

DaveyJakeDaveyJake

1114

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1275505%2fwsl-bash-doesnt-start%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

2

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, 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.

share|improve this answer

answered Feb 14 at 19:47

enharmonicenharmonic

336

add a comment | 

2

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, 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.

share|improve this answer

answered Feb 14 at 19:47

enharmonicenharmonic

336

add a comment | 

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, 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.

share|improve this answer

answered Feb 14 at 19:47

enharmonicenharmonic

336

share|improve this answer

answered Feb 14 at 19:47

enharmonicenharmonic

336

answered Feb 14 at 19:47

enharmonicenharmonic

336

answered Feb 14 at 19:47

enharmonicenharmonic

336

0

Here's what got it working for me:

1. Open CMD Prompt or PowerShell
   


2. Type bash and press enter.


3. When nothing happens, type ctrl+c.


4. Upon performing Step 3, you initialize your bash session, starting in your ~ (e.g. %user%) directory.

Hopefully this helps someone out there.

share|improve this answer

answered 20 mins ago

DaveyJakeDaveyJake

1114

add a comment | 

0

Here's what got it working for me:

1. Open CMD Prompt or PowerShell
   


2. Type bash and press enter.


3. When nothing happens, type ctrl+c.


4. Upon performing Step 3, you initialize your bash session, starting in your ~ (e.g. %user%) directory.

Hopefully this helps someone out there.

share|improve this answer

answered 20 mins ago

DaveyJakeDaveyJake

1114

add a comment | 

Here's what got it working for me:

1. Open CMD Prompt or PowerShell
   


2. Type bash and press enter.


3. When nothing happens, type ctrl+c.


4. Upon performing Step 3, you initialize your bash session, starting in your ~ (e.g. %user%) directory.

Hopefully this helps someone out there.

share|improve this answer

answered 20 mins ago

DaveyJakeDaveyJake

1114

share|improve this answer

answered 20 mins ago

DaveyJakeDaveyJake

1114

answered 20 mins ago

DaveyJakeDaveyJake

1114

answered 20 mins ago

DaveyJakeDaveyJake

1114