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 #7

Closed
leonardowolf opened this Issue Apr 7, 2016 · 26 comments

Comments

Projects
None yet
@leonardowolf

leonardowolf commented Apr 7, 2016

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

This comment has been minimized.

leonardowolf commented Apr 7, 2016

#4 (comment)

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

@J-Gonzalez

This comment has been minimized.

J-Gonzalez commented Apr 7, 2016

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.

image

@raeesbhatti

This comment has been minimized.

raeesbhatti commented Apr 7, 2016

Related to #2

@alorle

This comment has been minimized.

alorle commented Apr 7, 2016

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

This comment has been minimized.

leonardowolf commented Apr 7, 2016

Wow bro, TY all, worked fine here

@jbaribeault

This comment has been minimized.

jbaribeault commented Apr 7, 2016

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

@vidarw

This comment has been minimized.

vidarw commented Apr 12, 2016

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

@mabotn

This comment has been minimized.

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

@Artoria2e5

This comment has been minimized.

Artoria2e5 commented Apr 13, 2016

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

This comment has been minimized.

hbsis-lucianorodrigues commented Jun 15, 2016

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

This comment has been minimized.

Napo2k commented Nov 16, 2016

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

This comment has been minimized.

rudolphos commented Feb 13, 2017

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

This comment has been minimized.

Member

sunilmut commented Mar 2, 2017

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

@ReFruity

This comment has been minimized.

ReFruity commented Mar 11, 2017

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

@aseering

This comment has been minimized.

Contributor

aseering commented Mar 11, 2017

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

This comment has been minimized.

rudolphos commented Mar 12, 2017

@sunilmut

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

@ReFruity

This comment has been minimized.

ReFruity commented Mar 18, 2017

@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

This comment has been minimized.

tksunw commented Mar 20, 2017

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
@huangqingxin

This comment has been minimized.

huangqingxin commented Jul 5, 2017

I meet new problems , any others see this before

PS C:\WINDOWS\system32> Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
Enable-WindowsOptionalFeature : The parameter is incorrect.
At line:1 char:1

  • Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows- ...
  •   + CategoryInfo          : NotSpecified: (:) [Enable-WindowsOptionalFeature], PSArgumentException
      + FullyQualifiedErrorId : Microsoft.Dism.Commands.EnableWindowsOptionalFeatureCommand
    
    
@hsluoyz

This comment has been minimized.

Member

hsluoyz commented Jul 15, 2017

@huangqingxin I met the same issue:

image

@samfullman

This comment has been minimized.

samfullman commented Jul 28, 2017

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.
from J-Gonzales on April 7th above..
This helped me though ironically I checked the legacy mode and it worked.

@eltechnic0

This comment has been minimized.

eltechnic0 commented Sep 12, 2017

Still having this error when piping or redirecting the output. For instance: bash -c "ls -la" > out writes E r r o r : 0 x 8 0 0 7 0 0 5 7 to file out.
With no pipes or redir it works fine. Legacy mode is disabled.

@andy-5 andy-5 referenced this issue Feb 20, 2018

Closed

Error: 0x80070057 #13

@bardware

This comment has been minimized.

bardware commented Mar 26, 2018

I got this error today when I started kali. It has worked in the past.

C:\Users\bd>kali
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80070057
Error: 0x80070057 Falscher Parameter.

Legacy console is disabled.

image

@kyuuketsukikurai

This comment has been minimized.

kyuuketsukikurai commented Mar 27, 2018

Also getting this error when starting Kali. Any suggestions?

@DarthSpock

This comment has been minimized.

DarthSpock commented Mar 27, 2018

@tksunw

This comment has been minimized.

tksunw commented Mar 28, 2018

I have seen this error, 0x80070057, on two systems, and the only fix I ever found is a complete reinstall of Windows.

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