Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: 0x80070057 when starting bash.exe #110

Closed
aeri23 opened this issue Apr 10, 2016 · 9 comments
Closed

Error: 0x80070057 when starting bash.exe #110

aeri23 opened this issue Apr 10, 2016 · 9 comments

Comments

@aeri23
Copy link

aeri23 commented Apr 10, 2016

I updated yesterday to 14316 and installed the "Windows Subsystem for Linux (Beta)" windows feature.

The first time through, it let me know it was downloading Ubuntu for Windows from Windows update.

Every subsequent time that I try to start bash i get this error:

C:>bash
Error: 0x80070057

Additionally the start menu shortcut would flicker a window and then disappear.

I attempted to remove the subsystem feature and then reinstall it to start fresh and clean. When I did this, my start menu shortcut disappeared...and from cmd.exe I get the same error when starting bash.exe.

[Edit] shortly after filing this issue, I came across
#7

which solved the problem for me, legacy mode was causing bash.exe to not run.

@mabotn
Copy link

mabotn commented Apr 12, 2016

Hi,
the solution is simple :)

  1. open CMD
  2. go to its properties
  3. disable legacy mode
  4. restart cmd
  5. run bash

enjoy :D

@bschwartz757
Copy link

This solved my issue as well, thanks!!

@kat0072
Copy link

kat0072 commented Apr 22, 2016

Worked for Me as well. Cheers

@ilan-schemoul
Copy link

legacy mode was already disabled. I still have the problem on the latest build

@walksoffaith
Copy link

I have the same issue. Legacy mode is disabled.

@dethoma
Copy link

dethoma commented Oct 25, 2016

@walksoffaith

Can you please collect a trace for us so we can investigate what's happening?

  1. Download the below two .txt files and rename them .cmd
  2. Run start_lxcore_trace.cmd from an admin command prompt
  3. Launch bash.exe
  4. Wait until you see the error.
  5. Run stop_lxcore_trace.cmd from an admin command prompt
  6. You should now see three .etl files in the directory you ran the script from.
  7. Email the logs to: InsiderSupport@microsoft.com. Include in the subject / message to forward to the WSL team. In the body of the email mention it is for russalex

https://github.com/Microsoft/BashOnWindows/files/288621/start_lxcore_trace.txt
https://github.com/Microsoft/BashOnWindows/files/288622/stop_lxcore_trace.txt

@benhillis
Copy link
Member

@walksoffaith I got your traces, looks like we're failing to delete some file in %localappdata%\lxss. Could you try to manually delete that directory and install again?

@uuf6429
Copy link

uuf6429 commented Nov 1, 2016

I've just had this problem as well, the solution for me was to clear the contents of C:\Users\<username>\AppData\Local\lxss\temp

@StalkAlex
Copy link

@uuf6429 solution was helpful, but before it worked I had to fix disk errors by chkdsk /f

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

10 participants