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.

[hbsis-lucianorodrigues]

Disable legacy mode do not works to me. I'm executing bash from java:

String script = "/mnt/d/bla.sh"; // "d:\\bla.sh"; // "d:/bla.sh" /* None works! */
Process process = new ProcessBuilder("bash.exe", "-xe", script).start();

[Napo2k]

I am having this same issue when executing bash from a Jenkins job.

I have located this comment on another issue, I wonder if it's the reason for this?

Thanks for reporting the issue, yes this is expected. #2 has more details if you are interested:

"We have a known limitation where we only support the console for stdin and stdout. If either of those are not a console then we will fail"

I'm going to close this out as a duplicate so we can track the issue in that post.

Thank you!

[rudolphos]

Legacy mode disabled.

C:\WINDOWS\system32>bash
Error: 0x80070002

Bash just opens and closes when I run the exe. In cmd it shows that error, which is windows update error., what this has to do with win update ?...

[sunilmut]

@rudolphos - Thanks for your post. Can you please collect ETL traces using these steps and share the traces out?

Also, which windows build are you running. You can find that out using the windows ver command.

[tony-ist]

I get this error when using %%bash magic in Jupyter Notebook. Any idea how to fix this?

[aseering]

Hi @ReFruity -- could you be more specific about exactly what you're doing when you get this error? Are you using the Windows or the Linux version of Jupyter Notebook? What's an example of the exact magic that causes this error for you?

Also, per @sunilmut 's question above: Which Windows build are you running? You can find that out using the Windows ver command (at a Windows command prompt).

[rudolphos]

@sunilmut

My Win version: Microsoft Windows [Version 10.0.14393
etl files: lxcore_win_10.0.14393.zip

[tony-ist]

@aseering I am using Anaconda2-4.3.0.1 on Windows 10 with enabled bash support.

Any simple bash command, for example,

%%bash
ls

will cause this error.

[tksunw]

I am getting Error: 0x80070057 when I try to install the Linux bits, via running bash or running lxrun /install, as an admin user or a regular user.

I have read several of the other threads in this forum that mentioned this issue, and none of the solutions worked for me, so I'm starting a new thread.

Here is the terminal output:

PS C:\Users\tkennedy\WS_ETL> lxrun /install
-- Beta feature --
This will install Ubuntu on Windows, distributed by Canonical
and licensed under its terms available here:
https://aka.ms/uowterms

Type "y" to continue: y
Downloading from the Windows Store... 100%
Extracting filesystem, this will take a few minutes...
Error: 0x80070057

My Microsoft build is:
Microsoft Windows [Version 10.0.14393]

• Steps to reproduce:

• `lxrun /uninstall /full /y'
• lxrun /install /y

I have ETL files from the lxcore_trace scripts. WSL_ETL.zip

Ran a full chkdsk /R, followed by a reboot, just in case it was a disk issue.

Same error.

Disabled the WSL feature, by running:
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
And rebooting. After reboot, re-enabled the WSL feature, by running:
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
And rebooting again.

Same error:

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

Z:\>bash
-- Beta feature --
This will install Ubuntu on Windows, distributed by Canonical
and licensed under its terms available here:
https://aka.ms/uowterms

Type "y" to continue: y
Downloading from the Windows Store... 100%
Extracting filesystem, this will take a few minutes...
Error: 0x80070057

[XDo0]

• If you have used proxy, you will also encounter this error:

ubuntu2004 config --default-user Username
Error: 0x80070057

And also see the error when :

wsl or ubuntu2004
参考的对象类型不支持尝试的操作。（The attempted operation is not supported for the type of object referenced.）

• To solve:

netsh winsock reset and reboot