We have a repo on GitHub.com and I enabled git LFS on my Mac, rewrote the history with git lfs migrate and pushed the code. So far so good. After a few weeks we exceeded the Github's "Free" LFS quota (which is 1GB) and I tried to reverse the LFS support.
I did what is recommended to (git lfs uninstall, git lfs untrack, git lfs export...) and when I clone the repository on a MacOS or a Linux, everything works as expected.
When I clone on windows computers though, I get a warning saying that several file pointers are being used (so far so good) and several files show as "changed" randomly. If I clone the repo on the same computer into distinct folders, the number of files "changed" change randomly;
Also if I run git lfs ls-files a few files still show as tracked even them not being tracked over git lfs on Linux and MacOS.
Even creating a new repo and sending a single branch, those files still show running git lfs ls-files on Windows.
The behavior cloning on Windows based and Unix base system is completely distinct, which is quite unexpected.
