Description
Setup
- Which version of Git for Windows are you using? Is it 32-bit or 64-bit?
$ git --version --build-options
git version 2.39.0.windows.1
cpu: x86_64
built from commit: de9501c66f93785f7eaf10d02ef08d231eb11688
sizeof-long: 4
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
- Which version of Windows are you running? Vista, 7, 8, 10? Is it 32-bit or 64-bit?
Windows 10 Professional 64-bit, 22H2
- What options did you set as part of the installation? Or did you choose the
defaults?
$ cat /etc/install-options.txt
Editor Option: nano
Custom Editor Path:
Default Branch Option: main
Path Option: Cmd
SSH Option: OpenSSH
Tortoise Option: false
CURL Option: OpenSSL
CRLF Option: LFOnly
Bash Terminal Option: MinTTY
Git Pull Behavior Option: Merge
Use Credential Manager: Enabled
Performance Tweaks FSCache: Enabled
Enable Symlinks: Disabled
Enable Pseudo Console Support: Disabled
Enable FSMonitor: Disabled
- Any other interesting things about your environment that might be related
to the issue you're seeing?
Details
- Which terminal/shell are you running Git from? e.g Bash/CMD/PowerShell/other
git-bash (but that's not relevant to the request)
- 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.
Running setup for upgrading an existing git-for-windows while ssh-agent is already running in the background.
- What did you expect to occur after running these commands?
Seamless upgrade with no or little user interaction.
- What actually happened instead?
The installer comes up with an error message telling that ssh-agent.exe is running in the background.
User have to open the task manager, go to the "Details" tab, find ssh-agent.exe and kill it in order to continue the upgrade process.
This is a bit tedious and unfriendly
I am suggesting that the installer either silently kill the running ssh-agent.exe, or at least offers to do it on behalf of the user when popping up the message.
As far as I remember, this behavior has been consistent since I am using Git-for-Windows for the last 3 years.
Thanks
Beside that, I LOVE git-for-windows and git-bash. I prefer using that than WSL2.
Thanks for the job.
- If the problem was occurring with a specific repository, can you provide the
URL to that repository to help us with testing?
not applicable