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

Can not launch git bash of 0x800700c1 error #10270

Closed
Dragode opened this issue May 29, 2021 · 4 comments
Closed

Can not launch git bash of 0x800700c1 error #10270

Dragode opened this issue May 29, 2021 · 4 comments
Labels
Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@Dragode
Copy link

Dragode commented May 29, 2021

Windows Terminal version (or Windows build number)

1.8.210524004-release1.8

Other Software

git version 2.19.1.windows.1

Steps to reproduce

I used to launch git bash on windows-terminal successful.
After udpate windows-terminal version to 1.8.210524004-release1.8,it failed.
And I can use it in the cmd.
screenshot 2
This is the config:
{
"commandline": "D:\Program Files\scoop\apps\git\2.19.1.windows.1\bin\bash.exe",
"name": "git-bash",
"startingDirectory": null
}

Expected Behavior

No response

Actual Behavior

screenshot 1

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels May 29, 2021
@KalleOlaviNiemitalo
Copy link

KalleOlaviNiemitalo commented May 29, 2021

Is there a D:\Program file? According to #7195 (comment), that could cause error 0x800700c1. If so, you could perhaps delete the file or add quotation marks around the path:

{
    "commandline": "\"D:\\Program Files\\scoop\\apps\\git\\2.19.1.windows.1\\bin\\bash.exe\"",
    "name": "git-bash",
    "startingDirectory": null
}

(0x800700c1 is HRESULT_FROM_WIN32(ERROR_BAD_EXE_FORMAT), "%1 is not a valid Win32 application.")

@zadjii-msft zadjii-msft added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label May 31, 2021
@ghost ghost added the No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. label Jun 4, 2021
@ghost
Copy link

ghost commented Jun 4, 2021

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost ghost closed this as completed Jun 7, 2021
@casterle
Copy link

Is there a D:\Program file?

Thanks, from the future!

I don't know where it came from but removing that 'Program' file it fixed by 'Got Bash' problems.

@ghost ghost removed the No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. label Sep 28, 2022
@NotYoojun
Copy link

This worked!
I found a sus Program file on my D. Deleting this file fixed everything!

image

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

5 participants