Can't start Git Bash

问题:

Having trouble starting Git Bash, not sure where in the stack my errors are occuring. Running Windows 10, Git Bash, ConEmu and Vagrant.

When I start Git Bash, either through ConEmu or the application directly, I receive the following message:

0 [main] bash 4696 fork: child 528 - died waiting for dll loading, errno 11
bash: fork: retry: No child processes
1263234 [main] bash 4696 fork: child 684 - died waiting for dll loading, errno 11
bash: fork: retry: No child processes
3519490 [main] bash 4696 fork: child 2020 - died waiting for dll loading, errno 11
bash: fork: retry: No child processes
7764494 [main] bash 4696 fork: child 7064 - died waiting for dll loading, errno 11
bash: fork: retry: No child processes

I don't know enough about Git Bash (or bash, for that matter) to figure out what's going on and all the answers I can find are about Cygwin.

回答1:

Same issue happened with COMODO Firewall since last update.

1. Adding Git folder to File Rating > File List as trusted file

2. Adding Git folder to Advanced protection > Milanescious > Shell code exclusion

3. Setting git-bash.exe as allowed application in Firewall > Application Rules (this one may be optional, but it won't hurt anyway)

Solved the issue on Windows 10.

Side note : Turning COMODO firewall off does not solve the issue, this is quite misleading... But adding exclusions rules does fix the problem.

Other side note: if you use Comodo Firewall, ou should consider uninstalling it... It has bugged and ruined my windows install... When i think of it in hindsight, he was the root cause of a lot of problem. I mean, how in the world a Firewall could silently block an application or infinite sandboxing it without even a notification. Plus the removall is a pain in the ass, uninstaller crash one time out of two...

回答2:

Turns out Comodo Antivirus was auto-sandboxing Git Bash. Adding Git Bash as an exception to the sandboxing rules solved my problem.

Hope this saves someone else an hour.

回答3:

The company I work for has BeyondTrust PowerBroker on corporate computers, and that turned out to be the source of the problem.

I solved it by adding a the key ExcludedProfilerApps to HKLM\SOFTWARE\Policies\BeyondTrust\PBDesktops with the value C:\Program Files\Git\*.

Here is a link to some discussion of the issue.

Git Bash complained about some permissions on startup, but I didn't notice any other issues.

Installing Git 2.7.0, as @rakehell have mentioned, also resolved the issue.

回答4:

I have solved this by adding an exclusion for the entire git directory in (c:\Program Files\Git\*):

Advanced Settings -> Advanced Protection -> Miscellaneous -> Detect shellcode injections

See this https://forums.comodo.com/news-announcements-feedback-cis/comodo-internet-security-v10016209-released-t118704.0.html;msg854022#msg854022

回答5:

I had this problem on Win 7 and installed 5 versions of Git working backwards from the latest as well as run every solution I could find by Googling. However, the only thing that worked was this version: 2.7.0

The subsequent updates, 2.7.0.1 and 2.7.0.2, did not work.

HTH

回答6:

It is definitely a BeyondTrust /firewall issue.

Here is what happened on my Windows 7 laptop:

• Git (via msi installer) was installed in the local programs directory : C:\Users\myusername\AppData\Local\Programs\Git
• But the regedit shows a different value here -> HKLM ->SOFTWARE\Policies\BeyondTrust\PBDesktops shows the value C:\Program Files\Git*

Solution :

• Copy the Git folder from C:\Users\myusername\AppData\Local\Programs\ and paste it to C:\Program Files