FreeFileSync Forum

Good concern to have, as FFS will absolutely copy corrupted data just as well as good data. If a monitored location can't be seen at all, RTS will never start a sync anyway, so no worry there. There is no concrete answer to your question, because as always, "it depends". Why would "no...

In Apple's infinite wisdom, First Aid only reports errors if it detected and couldn't fix an issue

Not a good idea. Way more complicated, if not impossible, and likely more confusing down the road.

Did you 'star' it?

Yep, use multiple folders on the thumb drive, use multiple folder pairs in a single FFS config, and set them to mirror

"- Access "My Computers" (as created by Google Backup and Sync) if starred"

viewtopic.php?t=9293#p33700

I have updated dozens of versions and have not lost any settings

If they only show up when syncing with the SFTP location, they must already exist in the other locations you are syncing to. You can use CMD to find and delete these files. There is no risk, if they are in use, you won't be able to delete them. It's not a FFS bug, 100% guaranteed

Ah the classic 'I've been staring at pixels too long to be competent" error
Been there oh so many times

Files with a Tilda at the beginning are temp files that didn't get deleted gracefully by the program using them. Your File Explorer isn't set to show these hidden files, but you can change it so you can see them. Just delete them though.

Seems like renaming those document packages is also changing stuff inside, no? If so, it is being modified and the mod time should probably change accordingly. On Windows, there is the option of copying over permissions, it's in the Tools->Options section, maybe give that a shot. It may require runn...

Sure is possible, just use the "post-sync" command option to have one sync config start another one and split the pairs into individual configurations

Oh yes, I see! The only option I see currently is to run a comparison, right-click the header above the list of files, and use the 'select time span' option from there. That is obviously not a good long-term solution, as you have to compare all files first. Actually, I am unsure if a date selection ...

There is a 'Time Span' setting in the filter section of the configuration options

Run as admin or change permissions to that location
Log files don't usually write there though, are you sure you want that?

After running a comparison, try right-clicking one of the files and excluding from the context menu. This can provide some insight on the correct syntax as that is likely the issue.

You can also put a shortcut that points directly to the ".ffs_real" configuration in the startup folder!

https://freefilesync.org/manual.php?topic=rts-as-service

Assuming the initial limitation for the 1st sync is to have all OneDrive files locally on the PC. What happens if you later select that sync'd OneDrive folder on the PC and choose the OneDrive option "Free Up Space" ? At the next sync will FFS detect that the freed up files files are now ...

Use Time Machine to back up your OS, it is simply the best option in existence.
FFS is not a system backup/restore tool and shouldn't be relied upon for such use

Of course, the permissions are there to prevent other users from accessing your data.
You can either run FFS from each account for backups or run FFS using sudo from a terminal.

While you may have same named files, what about time & size (your comparison method)? You can see time in W/E, but not in FFS. You can see size in FFS, but not in W/E (at least not to the byte level). Might something have changed the dates of particular files &/or might the file sizes have ...

The only difference I see is the capitalization of 'Mine' on one side. I'm sure it won't make a difference, but what happens if you change it so the folders match identically? Also, what happens if you only sync one of the files? You can click one of the photos and hit ENTER to sync just that one it...

File Explorer works fine?
Reboot computer?

Can't find any concrete info on what that directory is used for, so it probably has no need to be backed up. I would exclude it. It's definitely a system file location, and FFS isn't a good option for system backup/restore anyway

The timestamp on the original file is probably corrupt/broken and contains a date outside the range that FAT can support. This means copying the file to the FAT location will lose the timestamp and set it to the current date/time, which may result in FFS detecting it as out-of-sync with the source o...

If you are renaming/moving files, FFS can detect that and avoid duplicating the file on the destination. FFS isn't a duplicate finder though, so make sure you are renaming/moving the file(s), not copying them.

You should just use FFS from the get-go then, as it can detect files that are moved/renamed instead of creating duplicates