That's a new situation. Before version 13 I did not get that with the same conditions.
Cannot write modificaton time of: *.ffs_tmp
- Posts: 5
- Joined: 15 Sep 2023
I'm syncing to an exFAT USB drive and get that warning:
That's a new situation. Before version 13 I did not get that with the same conditions.
That's a new situation. Before version 13 I did not get that with the same conditions.
- Posts: 4934
- Joined: 11 Jun 2019
If you revert to the previous version of FFS, does it work? I doubt it, because it looks like a file you have has a modification date that exceeds the exFAT limits. Check the details on that file and confirm the date shown. Does it copy fine if you try a manual copy via File Explorer?
- Posts: 5
- Joined: 15 Sep 2023
Yes, you're right. I thought this is an issue with the temp files FFS creates, but turns out the file itself has that old timestamp. Which is quite peculiar - it's a Cryptomator vault file and I definitely don't have any files that old. On the other side, Cryptomator itself it having some strange behavior since the latest update...
The file copies when I do it manually but the timestamp changes to the current date and time. Haven't tried reverting to old FreeFileSync version. Yet, before today I never had issue syncing the same files over the same destinations. Now I think it could be more of Cryptomator's fault.
The file copies when I do it manually but the timestamp changes to the current date and time. Haven't tried reverting to old FreeFileSync version. Yet, before today I never had issue syncing the same files over the same destinations. Now I think it could be more of Cryptomator's fault.
- Posts: 4934
- Joined: 11 Jun 2019
Ah yeah
I think FFS preserves the timestamp, but I think Windows will 'fix' the timestamp by updating it
I think FFS preserves the timestamp, but I think Windows will 'fix' the timestamp by updating it
