Skip to content

mingw: support Windows Server 2016 again #5700

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

dscho
Copy link
Member

@dscho dscho commented Jun 30, 2025

It was reported to the Git for Windows project that a simple git init fails on Windows Server 2016:

D:\Dev\test> git init
error: could not write config file D:/Dev/test/.git/config: Function not implemented
fatal: could not set 'core.repositoryformatversion' to '0'

According to https://endoflife.date/windows-server, Windows Server 2016 is officially supported for another one-and-a-half years as of time of writing, so this is not good.

The culprit is the mingw_rename() changes that try to use POSIX semantics when available, but fail to fall back properly on Windows Server 2016.

This fixes #5695.

It was reported to the Git for Windows project that a simple `git init`
fails on Windows Server 2016:

  D:\Dev\test> git init
  error: could not write config file D:/Dev/test/.git/config: Function not implemented
  fatal: could not set 'core.repositoryformatversion' to '0'

According to https://endoflife.date/windows-server, Windows Server 2016
is officially supported for another one-and-a-half years as of time of
writing, so this is not good.

The culprit is the `mingw_rename()` changes that try to use POSIX
semantics when available, but fail to fall back properly on Windows
Server 2016.

This fixes git-for-windows#5695.

Signed-off-by: Johannes Schindelin <[email protected]>
@dscho dscho added this to the Next release milestone Jun 30, 2025
@dscho dscho self-assigned this Jun 30, 2025
@dscho
Copy link
Member Author

dscho commented Jul 1, 2025

/git-artifacts

The tag-git workflow run was started

The git-artifacts-x86_64 workflow run was started.
The git-artifacts-i686 workflow run was started.
The git-artifacts-aarch64 workflow run was started.

Copy link

Validate the installer manually

The installer was built successfully;
Please download, install, and run through the pre-flight check-list.
@dscho ☝️

@dscho
Copy link
Member Author

dscho commented Jul 1, 2025

/release

The release-git workflow run was started

Copy link

@dscho, please Share on Bluesky and send the announcement email.

@gitforwindowshelper gitforwindowshelper bot merged commit c050b58 into git-for-windows:main Jul 1, 2025
83 checks passed
@dscho dscho deleted the support-windows-2016-again branch July 1, 2025 11:58
MarkEWaite added a commit to MarkEWaite/docker-lfs that referenced this pull request Jul 2, 2025
* Cloning: large repositories via SSH frequently hung with Git for
  Windows v2.50.0 git-for-windows/git#5688
  fixed in git-for-windows/msys2-runtime#103

* In: Git for Windows v2.50.0, operations using the POSIX emulation
  layer (cloning via SSH, generating the Bash prompt) cannot be
  interrupted by Ctrl+C, fixed in
  git-for-windows/msys2-runtime#104

* Git: for Windows v2.50.0 is unable to initialize Git repositories on
  Windows Server 2016
  git-for-windows/git#5695), fixed in
  git-for-windows/git#5700
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

git-cmd.exe | git-bash.exe seems unable to write anything to my disk.
1 participant