FreeFileSync Scheduled Task Runs but Copies Nothing
Quick answer
If Task Scheduler reports that a job ran but no files changed, confirm the batch configuration, Windows task identity, destination accessibility and FreeFileSync log before rerunning.
Test the exact batch configuration
Execute the saved batch job interactively and confirm the expected sample item appears in the destination.
Check the Windows task account
Review task credentials, start-in folder, mapped network shares and conditions that may prevent access.
Inspect logs and last run result
Review Task Scheduler history and FreeFileSync logging for warnings, skipped files or an unexpected empty comparison.
Validate independently
Open the expected destination file using File Explorer. Do not treat a zero exit code as proof of a correct backup plan.
Before you run the job
Use disposable test folders for the first pass. Keep an independent copy of important files, confirm drive identities, and run Compare before Synchronize. A preview is not a substitute for checking the actual destination afterwards.
Related FreeFileSync Windows guides
Source and review notes
This guide explains a focused Windows workflow. Consult the current FreeFileSync developer manual for precise behavior and edition-specific options. Review each planned file operation and test with non-critical files before relying on a procedure.