Hello to all.
I am new on this forum.
I want to back up my hardisk of 4 Tb and I have a big numbers of errors and think there is a real problem;
My first question is to know if the error is on the original disk or on my nbackup disk; I have reformated the backup (quick back up) with the same error.
I have 2 PC that I use with the same original hard disk and it is the same problem on botyh PC.
Second issue, I had problem with "long files names" due to someti_me multiple sub directories or other , I have set un the Win10 registry the information for windows to accept long files name.How to overcome the problem of "long Files Names" with FreeFileSync.
Thanks for your feedback and help
Patrick
WIN Long File Names
- Posts: 1
- Joined: 30 May 2025
- Posts: 323
- Joined: 13 Apr 2017
FreeFileSync has no problem handling Long file paths.
But please note the following in the FAQ:
Why does Windows Explorer show a different number of items?
When synchronizing with FreeFileSync and comparing the number of items of the source and target folders with Windows Explorer, consider the following possible explanations for a mismatch.
...
Long file paths: Unlike FreeFileSync, Windows Explorer is not able to handle file paths longer than 260 characters. Consequently, Explorer will not count files/folders with such long paths.
But please note the following in the FAQ:
Why does Windows Explorer show a different number of items?
When synchronizing with FreeFileSync and comparing the number of items of the source and target folders with Windows Explorer, consider the following possible explanations for a mismatch.
...
Long file paths: Unlike FreeFileSync, Windows Explorer is not able to handle file paths longer than 260 characters. Consequently, Explorer will not count files/folders with such long paths.
- Posts: 1222
- Joined: 8 May 2006
How about posting some of said file/path names where you're running into issues.
Perhaps, if name-part is 255 chars, ?, if an interim temp filename is ending up >255... or something like that? Could be a 255 char name-part - with no extension, & then a program wants to write 255+4 (like, 255.tmp), you're now at 259 chars which won't fly.
Perhaps, if name-part is 255 chars, ?, if an interim temp filename is ending up >255... or something like that? Could be a 255 char name-part - with no extension, & then a program wants to write 255+4 (like, 255.tmp), you're now at 259 chars which won't fly.
