FreeFileSync and Ransomware: Safer Backup Workflow
Design a FreeFileSync workflow that reduces exposure to ransomware and preserves recoverable copies.
Quick answer
Synchronization alone is not ransomware protection because encrypted or deleted source files can also be synchronized.
What to check first
Keep at least one versioned, snapshot-based, or offline copy that is not continuously writable from the main Windows session.
Windows-specific factors
Investigate unexpected mass changes before running Mirror or Two Way synchronization.
Safer troubleshooting workflow
Limit backup destination write exposure where practical and use permissions appropriate to the workflow.
How to verify the result
Practice restoring files without overwriting originals so the recovery path is known before an incident.
Frequently asked questions
Should I change sync mode to fix this?
Not until the underlying cause is identified. First verify paths, permissions, comparison results, and logs.
Is a successful sync the same as a verified backup?
No. Important data should be checked at the destination and periodically restored to a separate location.
Related: all FreeFileSync Windows guides