git-credential-winstore.exe missing

[wsw70]

Do you want to request a feature or report a bug?

Report a bug

What is the current behavior?

When pushing I get an error message about missing git-credential-winstore.exe:

"C:\Program Files\Git\bin\git.exe" push -u --recurse-submodules=check --progress "origin" refs/heads/master:refs/heads/master
Counting objects: 4, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 423 bytes | 0 bytes/s, done.
Total 4 (delta 3), reused 0 (delta 0)
"C:\Program Files (x86)\GitExtensions\GitCredentialWinStore\git-credential-winstore.exe" erase: C:\Program Files (x86)\GitExtensions\GitCredentialWinStore\git-credential-winstore.exe: No such file or directory
featal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
rror: RPC failed; HTTP 401 curl 22 The requested URL returned error: 401
Everything up-to-date

The Windows Credential pop-up does appears, enabling me to input my credentials, then I get the error above.

Which versions of GIT and which versions of Windows are affected by this issue? Did this work in previous versions of our tool?

This bug has been reported previously (for instance ferventcoder/chocolatey-packages#31) but still happens with fresh installs.

• My Git Extensions install is 2.49.03, "Complete" install package with all features enabled.
• I do not have any entries in my git config file (.git/config) which would point to the path referenced in the error log above.

[mortb]

I use gitextensions 2.49.03
I have a reference to git-credential-winstore.exe in the .gitconfig file which is placed in the "my documents" (%homedrive%homepath%) folder. I have no problems pushing, but we do not use http, we use ssh or git protocol

[RussKie]

does this relate to #3511?

afaik, git-credential-winstore.exe is needed for http

[increddibelly]

still here in 2.50.02. and I upgrade so few times that I forget the fix every time. C'mon guys...

[RussKie]

What do you expect us to do?

[increddibelly]

when you search for 'git credential winstore' it seems clear that gitextensions assumes defaults that aren't valid for many users. these issues date back to 2012 at least.
out of the top of my head, you could assume a safer default / verify the assumed value works BEFORE using it / add a check in the checklist?

[increddibelly]

actually, I've found it. again.
C:\users.gitconfig contains the following snippet:
helper = !\"C:\\Program Files (x86)\\GitExtensions\\GitCredentialWinStore\\git-credential-winstore.exe\"
but instead, this should be
helper = \"C:\\Program Files (x86)\\GitExtensions\\GitCredentialWinStore\\git-credential-winstore.exe\"

imho gitextensions should not write the ! to the config.

[vbjay]

! Means something. https://git-scm.com/docs/git-config. Search the page for !

…

On Thu, Nov 23, 2017, 4:03 AM Joost Boomkamp ***@***.***> wrote: actually, I've found it. again. C:\users.gitconfig contains the following snippet: helper = !\"C:\\Program Files (x86)\\GitExtensions\\GitCredentialWinStore\\git-credential-winstore.exe\" but instead, this should be helper = \"C:\\Program Files (x86)\\GitExtensions\\GitCredentialWinStore\\git-credential-winstore.exe\" — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#3732 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADdhsSJyxnndKG9ozZq_CsFh8xJ2f-yRks5s5TT0gaJpZM4NpL3-> .

[RussKie]

I think in this context, leading bang means "treat it as a shell command (executable)".... though I may be wrong

[RussKie]

I've searched the codebase and I can't find anything installs git-credential-winstore.exe or configures it.
I can only speculate that it is done by git for windows installation.

In #3511 there are suggested workarounds to replace it with wincred or manager.

[pmme]

The problem is not what GitExtensions 2.49 and later are doing, instead it's that earlier versions of GitExtensions created a setting (at a time when it was appropriate) and that setting now remains. In #3511 I wrote the command to remove the setting or change it to an alternative.

I have a suggestion: #4179