I keep getting popups for "Git Credential Manager for Windows" whenever SourceTree is running.
Pretty sure the credentials for all the repositories I have open are already in SourceTree as I can update, commit, etc without issue so I'm not sure why the popups keep appearing.
Is there something I can do to prevent them from appearing? A screenshot of what I'm seeing is below. I'm using Windows 10 x64 if that makes a difference.
This is the solution that finally worked for me:
(1) Installed Git Credential Manager for Windows.
(2) Opened the terminal by clicking the Terminal button in SourceTree.
(3) Issued the commands below:
The first command set the credential helper to use Git Credential Manager for Windows.
The second command was necessary for me because I use repositories that are on the same server/domain but each repository has different credentials.
This is SOOOOOO broken. Every 10 seconds I get a popup asking for a password. No reason. No indication of which account it's for, just a generic "provide a username and password". So I have no idea which repository it wants a password for or even what program is requesting it. No indication of whether the password fail or succeded, and after a while the box just reappears. Over top of stuff, in the middle of presentations, etc. This is effectively malware. This all started with the installation of SourceTree 2.0, so it's gotta be that.
The commands above seemed to help, but not right away. I thought I had got the spontaneous dialogs to go away, but they do sometimes re-appear.
The problem seemed to start for me when I added a new bitbucket account (academic) and wanted to use two accounts. I have had Source Tree 2.x for a long time and don't recall this headache. I agree the GUI is borked since we have no idea for which account or which operation the credintial manager is asking this information.
Tools > Options > Authentication seemed also to be helpful for me. I removed the Saved passwords that were stored and re-tried a push. That forced the GCM dialog, to which I supplied credentials for the repo that I was pushing to. The push was successful, and I saw also that a new entry in "Saved passwords" was created for that repo.
It seems weird, since I have OAuth for both accounts, and can browse my bitbucket.org repos (some of which are private) with no problem. Why doesn't push (or pull) use that same method to authenticate?
I have this problem too.
I install Visual Code 1.15.1 and SourceTree 2.1.10.
It always pops up a window too. I use Process Explorer v16.04 to inspect which process is asking me.
Open log `git config --global credential.writelog true`, and search `credential.log` in Everything Version 184.108.40.2067 (x86), but the content the log file is empty.
I recently updated Git and SourceTree (on Windows) and now I have the same problem with a pop up appearing every 10 minutes or so (even after I entered my password there) when SourceTree is open.
In my case it's the Microsoft account sign in.
I've tried what's suggested in the accepted answer but didn't help. Also tried various other terminal commands I found googling this problem also to no avail yet.
Would appreciate help to fix this, thanks.
Sorry to rant, but I'm not able to work with this annoying pop up getting in my way again and again.
Went back to SourceTree 1.x until this is properly fixed.
EDIT (20 June 2018): Recent changes to Bitbucket authentication has also meant that you must use your email (NOT your username) when logging in. Currently, logging in with your username is still accepted but seems to cause several issues ranging from this repeated login prompt issue to the "too many login attempts" error when pushing.
I've not seen the issue occur for non-Bitbucket accounts.
EDIT (29 Aug 2017): The embedded Git has now been updated, alongside the release of Sourcetree 220.127.116.11. After updating SourceTree, go to Tools > Options > Git and click "Update Embedded Git" to get the latest version (at least 2.14.1).
The majority of issues in Git Credential Manager for Windows have been fixed in recent versions. The latest version (1.12.0) released a couple days ago fixed the remaining issues I had with Bitbucket authentication.
The latest Git Credential Manager for Windows is included in the latest Git for Windows. Until Atlassian update their embedded version, you could install Git for Windows 2.14.0 and within SourceTree, click "Use System Git" in Options.
Kris's solution also works if you only want to update Git Credential Manager for Windows specifically, though does require config changes.
This is just a 'me too'. Updated to 18.104.22.168 and now I can't get rid of the Windows Credentials Manager popup, despite trying all the suggestions above.
This makes ot almost impossible to work.
Anyone know where I can get an older version of SourceTree until there is a fix for this?
last 1.x version (I think) is available here, also other older versions there.
Regarding a temporary 'fix' for this using 2.x version (on Windows), what I did when that annoying pop-up came up, was opening Task Manager, see what processes are running, could spot "Git credential manger.exe" (can't remember exact name), closed SourceTree and renamed that to something like "Git credential manger.old", (so it couldn't run anymore) which 'fixed' the popups for me.
I'm back to version 1.x anyway, as I like the layout with the bookmarks sidebar better.
Just to pop in here and bump this thread, it's been marked resolved, but it isn't. I have tried all of the "fixes" in this thread, and the only one that stops the annoying pop ups is going back to 1.9. Something happened recently, because I was just using this same repo on github last week without the issue. I noticed I was using the system git, so I updated that, tried the embedded git, etc. I stopped that service, rebooted a few times, yadayada.
I normally wouldn't bother commenting but I wanted to let the devs know this is not a fixed issue.
You might want to check whats being requested before the password prompt using wireshark or similar.
Also, SourceTree supports single sign-on, mening you can forever get rid of the need for passwords when using Bitbucket:
Lars, Kantega Single Sign-on
Thanks for the reply Lars. I'm not sure what's being requested but the pop-up only occurs when SourceTree is open and stop once SourceTree is closed so I'm pretty sure they are coming from SourceTree.
All I have open in SourceTree are three repositories (screenshot below). Each repository uses different credentials if that makes any difference.
That's right, Kris. Popups comes only when sourcetree has been started and when I start pull or push. In my sourcetree folder I have a git_extra folder with git-credential-manager.exe and git-credential-manager-st.exe. When I rename them, sourcetree throw an error. So where to stop to use this git-credential-manager.exe
Hi Lars, I'm using the SSO (OAuth) on both my accounts. When I want to clone a repo, I can browse all the repose for both accounts, so I know the OAuth tokens are good. Still, when I push, I'm asked to authenticate with the pop-up. Something seems broken, or am I supposed to indicate somewhere to use the OAuth tokens when pushing?
In my case, it was related to submodules including digest credentials in the URL string.
After trying all the suggested solutions, this is what ended up working for me:
Hops this helps someone else.
I was having this issue too, I tried several suggestions on this page to no avail. Turned out to be much simpler, I still had a reference in my SourceTree to an out-of-date repo which had finally been removed. Once I deleted that, the error went away.
Tried suggested solutions above from Kris, Christopher, Bo, Ryan and Francis, but the issue persists.
Have updated a helper tool to easily toggle the presence of git-credential-manager.exe (rename it, and rename back again when required) as a workaround.
Does anyone know if other GIT clients (GitKraken, SmartGit, Tower, GitUp) are experiencing the same behaviour?
I'll add something here that I think has solved it and others may have mentioned before. Probably the wiping all accounts clean might do the job, but If you're using SSH on some of your repos and HTTPS on others, you'll need to generate a private access key and use that as a password for the HTTPS ones. Also, keep in mind that subrepos may be set up this way, too.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Supported Platforms macOS Windows To make using Sourcetree as simple yet powerful as possible we embed (bundle) dependencies such as Git, Git LFS, and Mercurial. We strive to keep these...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG