Attempting to fetch or push if Pageant isn't already open results in freeze

Author: leximayfieldCreated May 7, 2023Updated Sep 19, 2026
Labelsup-for-grabsarea: ssh/putty

Environment

  • Git Extensions 4.0.2.16100
  • Build 25100ec1f7c8da8f798613da74826038af81a50e
  • Git 2.38.1.windows.1
  • Microsoft Windows NT 10.0.22621.0
  • .NET 6.0.16
  • DPI 168dpi (175% scaling)
  • Microsoft.WindowsDesktop.App Versions
    Microsoft.WindowsDesktop.App 3.1.24 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
    Microsoft.WindowsDesktop.App 5.0.12 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
    Microsoft.WindowsDesktop.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
    Microsoft.WindowsDesktop.App 6.0.14 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
    Microsoft.WindowsDesktop.App 6.0.16 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
    Microsoft.WindowsDesktop.App 7.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Issue description

When I attempt to do a git repository operation involving a remote such as fetch or push and Pagent isn't already running, Git Extensions freezes upon me putting in my SSH key password.

I am using PuTTY 0.76. If Pagent is already running, I do not get a freeze-up, no matter if my key has already been loaded with a password or not.

Steps to reproduce

  1. Ensure that Git Extensions is configured to use PuTTY and Pagent, with a passworded SSH key.
  2. Open Git Extensions with a SSH remote.
  3. Pull.

Did this work in previous version of GitExtensions?

It has been broken since at least the last major version (3.x), so for years.

Diagnostics

No response

Source: gitextensions/gitextensions