Subject: Bug - git fsck never ending on git-for-windows

From: Pascal Chambon <[email-masked]>
Date: Fri, 10 Apr 2026 09:20:20 +0200

What did you do before the bug happened? (Steps to reproduce your issue)

 > I launched "git fsck" (with various arguments)

What did you expect to happen? (Expected behavior)

 > A long run of fsck and then it's over

What happened instead? (Actual behavior)

 > A (seemingly) neverending run of fsck, exceeding the expected count 
of objects to check:
 > $ git fsck
 > Checking ref database: 100% (1/1), done.
 > Checking object directories: 100% (256/256), done.
 > Checking objects: 190% (54090/28351)        -->  (process still 
turning...)

What's different between what you expected and what actually happened?

 > Normal, finished fsck run, vs neverending checking of objects.

Anything else you want to add:

 > This is a quite old repository (from 2012) with quite heavy media 
files in it (70 GB total).
 > I've tried to "git gc --aggressive", it worked, and pack files are 
numerous and about the same size, but the fsck anomally remains.

[System Info]
git version:
git version 2.53.0.windows.2
cpu: x86_64
built from commit: e9edee0b34751bf4d7d1feda0e2535bff64d4e77
sizeof-long: 4
sizeof-size_t: 8
rust: disabled
feature: fsmonitor--daemon
gettext: enabled
libcurl: 8.18.0
OpenSSL: OpenSSL 3.5.5 27 Jan 2026
zlib: 1.3.1
SHA-1: SHA1_DC
SHA-256: SHA256_BLK
default-ref-format: files
default-hash: sha1
uname: Windows 10.0 26200 -> actually Windows 11 Professionnel 25H2
compiler info: gnuc: 15.2
libc info: no libc information available
$SHELL (typically, interactive shell): <unset>

[Enabled Hooks]
(none)