-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Installer doesn't request elevation, then it hangs during config near end of installation #1768
Comments
I have the same issue. The installer hangs and never completes. Windows 7 and Git 2.22. Using the log option produces this output and stops progressing (but a new "git" process pops into my task manager): 2019-07-22 14:14:06.800 Installation process succeeded. |
I don't even know how the installer can be started without requiring elevation. In my case, it always does. |
To any one interested in a workaround read #2158 (comment) It worked for me. =) |
Pull request #2358, specifically commit 5a95abc, seems to have resolved the root cause of this issue—that an installation step tried unsuccessfully to modify Also, I found that to reproduce this issue, the directory
(The message is similar with Although the installer for version 2.26.0 similarly does not prompt me for elevated privileges, I'm closing this issue because its root cause appears resolved. |
I was not able to find an open or closed issue matching what I'm seeing
Commenters to issue Git installer hangs on non-Windows drive #815 after Dec 2017 report the installer hanging, but the causes aren't clear.
Issue Install from .exe freezes, some commands won't run #1374 reports a frozen installer and broken commands; based on a few tests, my commands appear functional.
In issue Git for Windows Installer hangs #1763, the installer hangs at
mkdir
, whereas in my case it hangs atgit config
. The log omits the early line specifying whether the installer ran with administrative privileges.Setup
Which version of Git for Windows are you using? Is it 32-bit or 64-bit?
Which version of Windows are you running? Vista, 7, 8, 10? Is it 32-bit or 64-bit?
Windows 10 64-bit.
What options did you set as part of the installation? Or did you choose the
defaults?
Any other interesting things about your environment that might be related
to the issue you're seeing?
None known.
Details
When I ran the installer (
Git-2.18.0-64-bit.exe
) from my non-privileged user account, it did not prompt for elevated privileges but proceeded into the wizard. I accepted its proposed installation path under myAppData
directory. Once the installer's progress bar filled, the installer remained in that state for several minutes. With Process Explorer, I saw that a subprocess with the following command line was running within theC:\ProgramData\Git
directory:After I killed that process, the installer continued and then exited after I clicked the "Finish" button on the final pane.
I expected, if that installer is intended only for system (not user) installations, that it would prompt for elevated privileges. If it may be used for user installations, I expect it not to try to modify a system configuration file at
C:\ProgramData\Git\config
.When I explicitly ran the installer as administrator, it completed without hanging and modified the system configuration file.
Cause of hanging
It appears that the cause of the installer hanging is
git config
waiting on input. When I used the Command Prompt to run the command line above in the correct directory,git config
asked to retry (because it lacked privileges to modify the config file) and waited for a response:That left a new file
C:\ProgramData\Git\config.lock
. When I ran the above command thereafter,git config
instead printed an error message and terminated immediately:That suggests that a second run of the installer would appear to succeed, although it would have failed to alter the system configuration file.
Installer log
When I ran the installer with
/log=<file>
(and with no lingeringconfig.lock
file), the installer hung after writing the "Installation process succeeded" line and continued after I killed thegit config
subprocess. The tail of the log is as follows:The text was updated successfully, but these errors were encountered: