One one machine (Win7), I can use GIT commands just fine, and the credential manager appears to do its thing properly. I can do GIT pull, push, etc to a BitBucket respository. It just works, and all that login stuff is handled automatically under the hood.
However, on a Win10 laptop, something strange happens. Doing "git pull origin master", for example, causes a Atlassian login popup. No matter what I enter, this always fails, but then the GIT command succeeds anyway. The same thing happens if I simply dismiss the login popup window without entering anything. GIT writes the nastygram "Logon failed, use ctrl+c to cancel basic credential prompt.", but then proceeds to perform the requested operation properly.
Since the operation is performed, GIT must be using the credential manager successfully to authenticate under the hood. On this machine, there is just this extra step of having to manually dismiss the login popup window to do GIT operations that access BitBucket respositories. That's annoying by itself, but really gets in the way of scripted operations. Again, this doesn't happen on other machines. I have copied the credential files between the machines, but that didn't change anything. It seems it's not a GIT credential problem, but something else getting in there somehow before the credential manager runs.
How do I fix this?