-
Notifications
You must be signed in to change notification settings - Fork 837
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
Comments
Hi,
enjoy :D |
This solved my issue as well, thanks!! |
Worked for Me as well. Cheers |
legacy mode was already disabled. I still have the problem on the latest build |
I have the same issue. Legacy mode is disabled. |
Can you please collect a trace for us so we can investigate what's happening?
https://github.com/Microsoft/BashOnWindows/files/288621/start_lxcore_trace.txt |
@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? |
I've just had this problem as well, the solution for me was to clear the contents of |
@uuf6429 solution was helpful, but before it worked I had to fix disk errors by chkdsk /f |
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.
The text was updated successfully, but these errors were encountered: