Install from .exe freezes, some commands won't run

[fredbutters]

• [x ] I was not able to find an open or closed issue matching what I'm seeing

There is a ticket (581) for the installer freezing, but I'm unsure if it's related to some of the commands not working

Setup

• Which version of Git for Windows are you using? Is it 32-bit or 64-bit?

$ git --version --build-options

git 2.15.0 and 2.14.2 (I tried both, same issue) 64-bit 
git version 2.14.2.windows.1
built from commit: 788debdfb6b794425a3b949dd1a0eb2425a72e96
sizeof-long: 4
machine: x86_64

• Which version of Windows are you running? Vista, 7, 8, 10? Is it 32-bit or 64-bit?

$ cmd.exe /c ver

Windows 10 (64 bit)
Microsoft Windows [Version 10.0.14393]

• What options did you set as part of the installation? Or did you choose the
  defaults?

# One of the following:
> type "C:\Program Files\Git\etc\install-options.txt"
> type "C:\Program Files (x86)\Git\etc\install-options.txt"
> type "%USERPROFILE%\AppData\Local\Programs\Git\etc\install-options.txt"
$ cat /etc/install-options.txt

Path Option: Cmd
SSH Option: OpenSSH
CURL Option: OpenSSL
CRLF Option: CRLFAlways
Bash Terminal Option: MinTTY
Performance Tweaks FSCache: Enabled
Use Credential Manager: Enabled
Enable Symlinks: Disabled

• Any other interesting things about your environment that might be related
  to the issue you're seeing?

None that I know of

Details

• Which terminal/shell are you running Git from? e.g Bash/CMD/PowerShell/other

CMD

• What commands did you run to trigger this issue? If you can provide a
  Minimal, Complete, and Verifiable example
  this will help us understand the issue.

These commands do not work. 
`git-push`
`git-stash`

These commands do work 
`git-status, branch, checkout, add, commit`

• What did you expect to occur after running these commands?

Just expected them to work

• What actually happened instead?

Hitting enter, the cursor just goes to the next line and sits there. I've waited up to 10 minutes without anything happening

• If the problem was occurring with a specific repository, can you provide the
  URL to that repository to help us with testing?

Local repo and react have the same symptoms (https://github.com/facebook/react.git)

[dscho]

Thank you for your report.

Sadly, these instructions do not repeat the issue here (and hence the V in MVCE is not fulfilled).

Could you try again after setting the environment variable GIT_TRACE=1, and possibly monitoring what is going on using Process Monitor?

[fredbutters]

I ran set GIT_TRACE=1 from a Windows admin cmd window then tried running git stash again with Process Monitor running with a filter for process name = git.exe. The output in the cmd window is below, but process monitor is showing around 1,800 lines - is there anything I should be looking for? Thanks

C:\Users\<username>\Source\Repos\>git stash
09:22:37.893518 git.c:572               trace: exec: 'git-stash'
09:22:37.897032 run-command.c:626       trace: run_command: 'git-stash'

[fredbutters]

If it helps, when I try to open git bash a window pops up with the title /usr/bin/bash --login -i but I'm not able to run any commands and there's not real cmd prompt. I can type text into the window but it almost acts like a text editor. I can type stuff and hit enter, which just moves the cursor to the next line and I can keep typing. That's all it does.

If I close the window it takes about 10 seconds before finally closing

[dscho]

process monitor is showing around 1,800 lines - is there anything I should be looking for?

You would be looking for suspicious activity during the time that git stash freezes. It may even be an antivirus taking too long...

[fredbutters]

I think I'm having the same issue as #815 . The resolution on #815 was to use 2.11.0 but I tried that version and had the same problems. So far I've tried 2.11.0, 2.14.1, 2.14.2 and 2.15.0. I don't have any anti-virus running and I've disabled Windows Defender (just in case)

After the install freezes I see two instances of bash.exe and one mkdir.exe that are "stuck." If I kill he bash exe's in Task Manager the installer finishes but git-bash still doesn't work and git stash still freezes.

On another install I killed the installer and tried to uninstall but got a warning that bash.exe and mkdir.exe are in use and I need to stop them before uninstalling.

I looked at the process mon log but I honestly have no idea what I'm seeing. I could paste the whole thing in here if someone is willing to check it out but it's usually over 1,100 lines

[fredbutters]

git pull isn't working either, I just noticed that. I think I pulled from within Visual Studio 2017. I enabled GIT_TRACE and it just freezes at this point.

C:\Users\<username>\Source\Repos\>git pull
16:31:18.347103 git.c:340               trace: built-in: git 'pull'
16:31:18.350600 run-command.c:626       trace: run_command: 'fetch' '--update-head-ok'
16:31:18.370820 git.c:340               trace: built-in: git 'fetch' '--update-head-ok'
16:31:18.377324 run-command.c:626       trace: run_command: 'remote-http' 'origin' 'http://tfs:8080/tfs/_git/branch'
16:31:18.395812 git.c:572               trace: exec: 'git-remote-http' 'origin' 'http://tfs:8080/tfs/_git/branch'
16:31:18.397312 run-command.c:626       trace: run_command: 'git-remote-http' 'origin' 'http://tfs:8080/tfs/_git/branch'
16:31:18.441021 run-command.c:626       trace: run_command: 'git credential-manager get'

[dscho]

It looks like your Bash freezes somewhere during startup (yes, Bash is used to launch credential-manager...).

Could you download the portable Git (which does not install into your Start Menu) and verify that the problem persists when you double-click git-bash.exe in the unpacked directory?

If it does, could you insert the line set -x somewhere early in the file etc\profile and then start git-bash.exe again? This should give us an idea where in the startup things get stuck.

[dori4n]

Microsoft Windows [Version 10.0.14393]

That's Windows 10 1607 (Anniversary Update), two major releases behind the current released stable version. Is there a particular reason, you are still running that and not 1703 (Creators Update) or the recently released 1709 (Fall Creators Update)? Did you run into problems upgrading? Are you installing updates at all?
Running dism /online /Cleanup-Image /RestoreHealth from an elevated command prompt may resolve the issue.

git-bash does also not work with DEP or ASLR enabled, causing similar behavior (see #1196), because the Windows binaries are built using MSYS2 or MinGW derivative build systems, which do not provide PE executables with relocatable base addresses. Normally, this would be as easy as passing the --dynamicbase command line option to MinGW when building, but that has been broken for years.

[dscho]

The Windows version, as well as the Address Space Layout Randomization, are unlikely to be the culprit: @fredbutters mentioned that Bash's startup process manages to execute all the way to a mkdir.exe. That means that the MSYS2 runtime is starting up, and mkdir.exe is not a program calling fork() (which would trigger the problem with ASLR reported elsewhere).

@fredbutters if you would not mind inserting that set -x, that will bring us farther along in finding out what is happening and how to fix it.

[AlphaZuluLima]

I am having what seems to be exactly the same problem that @fredbutters was having.

These are the settings I have:
set GIT_TRACE=1
set x added to etc\profile

This is the output that I see:

+ MSYS2_PATH=/usr/local/bin:/usr/bin:/bin
+ MANPATH=/usr/local/man:/usr/share/man:/usr/man:/share/man
+ INFOPATH=/usr/local/info:/usr/share/info:/usr/info:/share/info
+ case "${MSYS2_PATH_TYPE:-inherit}" in
+ ORIGINAL_PATH='/mingw64/bin:/usr/bin:/h/bin:/cmd:/c/Windows/system32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0:/c/Program Files/COMPANY/cfn-bootstrap:/c/Program Files (x86)/Quarantine:/c/Program Files/PuTTY:/cmd:/d/Users/USERNAME/AppData/Local/Microsoft/WindowsApps'
+ unset MINGW_MOUNT_POINT
+ source /etc/msystem
++ export MSYSTEM=MINGW64
++ MSYSTEM=MINGW64
++ unset MSYSTEM_PREFIX
++ unset MSYSTEM_CARCH
++ unset MSYSTEM_CHOST
++ unset MINGW_CHOST
++ unset MINGW_PREFIX
++ unset MINGW_PACKAGE_PREFIX
++ unset CONFIG_SITE
++ case "${MSYSTEM}" in
++ MSYSTEM_PREFIX=/mingw64
++ MSYSTEM_CARCH=x86_64
++ MSYSTEM_CHOST=x86_64-w64-mingw32
++ MINGW_CHOST=x86_64-w64-mingw32
++ MINGW_PREFIX=/mingw64
++ MINGW_PACKAGE_PREFIX=mingw-w64-x86_64
++ CONFIG_SITE=/mingw64/etc/config.site
++ export MSYSTEM_PREFIX MSYSTEM_CARCH MSYSTEM_CHOST MINGW_CHOST MINGW_PREFIX MINGW_PACKAGE_PREFIX CONFIG_SITE
+ case "${MSYSTEM}" in
+ MINGW_MOUNT_POINT=/mingw64
+ PATH='/mingw64/bin:/usr/local/bin:/usr/bin:/bin:/mingw64/bin:/usr/bin:/h/bin:/cmd:/c/Windows/system32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0:/c/Program Files/COMPANY/cfn-bootstrap:/c/Program Files (x86)/Quarantine:/c/Program Files/PuTTY:/cmd:/d/Users/USERNAME/AppData/Local/Microsoft/WindowsApps'
+ PKG_CONFIG_PATH=/mingw64/lib/pkgconfig:/mingw64/share/pkgconfig
+ ACLOCAL_PATH=/mingw64/share/aclocal:/usr/share/aclocal
+ MANPATH=/mingw64/share/man:/usr/local/man:/usr/share/man:/usr/man:/share/man
+ MAYBE_FIRST_START=false
+ SYSCONFDIR=/etc
+ ORIGINAL_TMP=/tmp
+ ORIGINAL_TEMP=/tmp
+ case "$TMP" in
+ case "$TEMP" in
+ test -d ''
+ test '!' -d /tmp
+ TMPDIR=/tmp
+ export TMPDIR
++ export LC_COLLATE=C
++ LC_COLLATE=C
++ echo /etc/post-install/01-devices.post /etc/post-install/03-mtab.post /etc/post-install/06-windows-files.post /etc/post-install/99-post-install-cleanup.post
+ for postinst in $(export LC_COLLATE=C; echo /etc/post-install/*.post)
+ '[' -e /etc/post-install/01-devices.post ']'
+ . /etc/post-install/01-devices.post
++ maybe_create_devs
++ local DEVDIR=/dev
++ '[' -e /dev -a '!' -d /dev ']'
++ mkdir -m 755 /dev

[AlphaZuluLima]

Nothing has changed in the /usr/bin/bash --login -i window in hours.

[dscho]

@AlphaZuluLima thanks for testing this. Does the directory C:\Program Files\Git\dev exist at that stage? What file system do you use on C:? Does it work if you edit C:\Program Files\Git\etc\post-install'01-devices.post (as administrator) and delete the -m 755 in mkdir -m 755 /dev?

[AlphaZuluLima]

Does the directory C:\Program Files\Git\dev exist at that stage?
No

What file system do you use on C:?
NTFS

Does it work if you edit C:\Program Files\Git\etc\post-install\01-devices.post (as administrator) and delete the -m 755 in mkdir -m 755 /dev?
No. I still hangs here:

++ maybe_create_devs
++ local DEVDIR=/dev
++ '[' -e /dev -a '!' -d /dev ']'
++ mkdir /dev

[dscho]

Hm. Sorry. I hoped this would shed some light into the issue.

Would you kindly try again while running ProcMon? I hope to find out what is happening there...