Skip to main content

Git for Windows 2.49.0 broke my Azure DevOps pushes

After a routine Visual Studio update silently upgraded Git for Windows to version 2.49.0, pushes to Azure DevOps started failing with a cryptic NTLM authentication error — even though our setup was supposed to use Kerberos. Here's what happened and how to fix it in 30 seconds.

The symptoms

You update Visual Studio (or Git for Windows directly), and suddenly any push to your Azure DevOps remote fails. The error mentions NTLM even though your network is configured for Kerberos. Typical signs:

  • Git push fails immediately after a Visual Studio or Git for Windows update
  • Error references NTLM authentication failure
  • Clones and fetches from the same remote may still work
  • The remote URL is an internal TFS/Azure DevOps server (e.g.https://tfs.yourcompany.com)

What changed

Git for Windows 2.49.0 (shipped as MinGit 2.49.0) changed how it negotiates authentication for HTTPS remotes. The new default behaviour causes Git to attempt NTLM where it previously fell through to Kerberos — breaking on-premises Azure DevOps and TFS servers that rely on Kerberos/Negotiate for authentication.

Root cause: The http.emptyAuth setting tells Git to send an initial request without credentials, which prompts the server to advertise its supported auth schemes. Without it, the new Git version skips that negotiation step and defaults straight to NTLM — which then fails.

The fix

Run this single command in any terminal (Git Bash, PowerShell, or Command Prompt). Replace the URL with the base URL of your TFS/Azure DevOps server:

git config --global http.https://tfs.yourcompany.com.emptyAuth true

This sets emptyAuth = true scoped only to your internal server URL, so Git sends an unauthenticated probe first. The server responds with the correct auth challenge (Kerberos/Negotiate), and the push succeeds as expected.

Why scope it to the URL? Using a URL-scoped config (http.https://…emptyAuth) rather than a global http.emptyAuth true keeps the change surgical — it won't affect authentication behaviour for GitHub, GitLab, or any other remotes.

Verifying the fix

After running the command, confirm it was written correctly:

git config --global --list | grep emptyAuth

You should see a line like:

http.https://tfs.yourcompany.com.emptyAuth=true

Then retry your push — it should go through immediately without prompting for credentials.

Alternative: roll back Git for Windows

If you need a temporary workaround while coordinating with your team, you can downgrade to Git for Windows 2.48.x from the official releases page. That said, the one-liner above is the cleaner long-term solution.

More information

Git for Windows/mingit 2.53.0(2) update causes Visual Studio git commands to fail with NTLM authentication error even though Kerberos should be used - Developer Community

Server advertises Kerberos, but GCM ignores it · Issue #2290 · git-ecosystem/git-credential-manager

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more