More than once, it crashed (reboot) at exact file number 538035.
Anyone experiencing the same issue?
Thanks
FreeFileSync stuck and crash my MacOS at `scanning files FreeFileSync 538035`
- Posts: 2
- Joined: 11 Feb 2026
- Posts: 4908
- Joined: 11 Jun 2019
- Posts: 2
- Joined: 11 Feb 2026
Thanks for your advice, for some reason, my FreeFileSync got stuck at exact #538035 file every time, it just got stuck there and going forever.
- Posts: 4908
- Joined: 11 Jun 2019
Your response didn't include any additional info, so I am only guessing here lol
Could be a corrupted file or failing storage drive. If that file has some of its data stored on a corrupted sector of a disk, the disk never fulfills the read request, FFS gets stuck forever. Does FFS display what file it is scanning at that time? If so, can you try to open it or copy it manually somewhere else to test? You could also try to sync subfolder pairs one-at-a-time to see if it's a memory/quantity issue or possibly nail down which path is causing the trouble.
Could be a corrupted file or failing storage drive. If that file has some of its data stored on a corrupted sector of a disk, the disk never fulfills the read request, FFS gets stuck forever. Does FFS display what file it is scanning at that time? If so, can you try to open it or copy it manually somewhere else to test? You could also try to sync subfolder pairs one-at-a-time to see if it's a memory/quantity issue or possibly nail down which path is causing the trouble.
