Error: 0x80070057

[leonardowolf]

I'm an early adopter and a think I comited some sort of mistake in the processo of instalation of bash on my Windows computer. I did just like the blog step by step says, but by some kind of sorcery, if i have to do some serious shit on my cmd (this is an old trouble) i need to open it as admin. I'v done the activation of Windows Subsystem for Linux and restarted my SO. But when I come back to install the bash by cmd I forgot to open it as admin. There was no trouble at all during the instalation but now when I try to open the bash, from the cmd (as adm or not), or even from the installed app I have this error by response:"Error: 0x80070057".

Any tips to fix this? and yes I alredy tryed to restart my computer fhaushfuashdf (sad this didn't worked)

[leonardowolf]

#4 (comment)

I tryed these, Re-installed all the bash from an adm prompt and i still got the same error

[J-Gonzalez]

I've noticed this error occurs if you have the command prompt in legacy mode. Make sure you disable legacy mode and try if that works.

[RaeesBhatti]

Related to #2

[alorle]

I had the same error when attempting to start bash in WSL. It has been fixed by disabling legacy mode in the console options.

[leonardowolf]

Wow bro, TY all, worked fine here

[jbaribeault]

I noticed this setting gets set the moment you try and change the colors too - be careful!

[vidarw]

Should this be closed?
Even if we have a proper workaround and identified the cause of the problem, it's still breaking bug!

[mabotn]

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

[Artoria2e5]

This happens with other terminal emulators like mintty too. I was trying to escape from conhost's crappy emulation (e.g. problem with inserting characters in the middle of a bash command), but neither sshd nor other emulators worked.

Perhaps I should get xterm.