Loading the commit history takes forever, but only on one computer

[Uwe Risse]

I have SourceTree installed on two computers, both with the identical content in terms of branches and settings. The history of my project goes back until 2005 with thousands of commits. On my older computer (Windows 10), everything is fast and smooth. On my four times faster computer (with Windows 11), however, the commit history stays at "Loading 120 commits to reach commit xyz" forever, when trying to reach older commits. Any idea where it comes from and how to fix this? Thanks!

[Rock]

This is usually caused by a local issue, not the repo itself. On Windows 11, SourceTree can hang on history loading due to antivirus scanning, corrupted cache, or a Git performance setting.

Try clearing SourceTree’s cache, disabling real-time antivirus scanning for the repo folder, and make sure both machines are using the same Git version in SourceTree settings. In many cases, switching SourceTree to use the bundled Git instead of a system Git also fixes slow history loading.