Repository navigation
Git network operations failing after update to Git for Windows v2.50.1 from v2.49.1.1 #5838
Description
Existing issues matching what you're seeing
- I was not able to find an open or closed issue matching what I'm seeing
Git for Windows version
MinGit 2.50.1Windows version
Windows 11
Windows CPU architecture
x86_64 (64-bit)
Additional Windows version information
Options set during installation
This was reported in MinGit, so no installation happened.Other interesting things
This is happening on VS IDE 17.14.13 and up, which use MinGit 2.50.1. Seems related to this curl/libcurl issue issue. The output from Git's error and the one described in the issue match and it looks like Git for Windows is using one of the affected versions (8.13, 8.14. 8.15). Looks like the fix shipped with 8.16.
This was originally reported in a Visual Studio Developer Community Feedback Ticket.
Terminal/shell
CMD
Commands that trigger the issue
Git network operations on remote branches. Example below from `push`.Expected behaviour
Network operations succeed.
Actual behaviour
Network operations fail with messages like in the following example from push:
Error encountered while pushing to the remote repository: Git failed with a fatal error.
unable to access ‘removed devops link for privacy reasons’: schannel: failed to read data from server: SEC_E_CONTEXT_EXPIRED (0x80090317) - The context has expired and can no longer be used.
Failed to push to the remote repository. See the Output window for more details.
Repository
No response
Activity
dscho commentedon Sep 25, 2025
We already integrated cURL v8.16, all this would need is a new Git for Windows version. See also the discussion at #5787 (comment)
dscho commentedon Sep 26, 2025
My current plan is to release Git for Windows v2.51.0(2) this coming Monday, with the fixed cURL version.
dscho commentedon Sep 26, 2025
Here is a snapshot installer/Portable Git/MinGit of this revision: https://github.com/git-for-windows/git-for-windows-automation/actions/runs/18030062242, maybe you can confirm the fix?
aatala commentedon Sep 29, 2025
Confirmed with a customer that the new MinGit version fixes the issue.
dscho commentedon Sep 29, 2025
Thank you for circling back!