The plugin is regularly tested on Windows systems with git installed in a non-default location. One of my test machines has git installed on the D: drive. I believe another test machine has it installed in a different non-default location.
You may be able to diagnose why it can't find ssh.exe in your case by reviewing the steps the source code currently takes to find ssh.exe on Windows.
The steps used to attempt to locate the correct ssh.exe include:
- If the GIT_SSH environment variable exists and names a file which exists, use that name (allows user override)
- If %ProgramFiles%\git\bin\ssh.exe exists, use that name (32 bit windows default location)
- If %ProgramFiles(x86)%\git\bin\ssh.exe exists, use that name (64 bit windows default location)
- If the git program name provided by the user is an absolute path, and if an ssh.exe is in the same directory as that program, use ssh.exe in that directory
- If the git program is in the "cmd" directory instead of the "bin" directory, look in the "bin" directory adjacent to the "cmd" directory
Some possible places where that will go wrong include:
- git not in the PATH (can't find git program, thus can't find ssh near it)
- git.exe in a directory that is early on the path without an ssh.exe in the same directory
Based on the "D:\git-1.9.5\Git\cmd\git.exe" in the bug report (thanks for including it), I assume the last stage of the "find ssh.exe" process must be failing your environment.
Does the behavior improve if you use D:\git-1.9.5\Git\bin\git.exe as the git executable instead?