August 30, 2026 Free File Sync, v 13.2, 64 bit, tried to delete a folder from the originating drive, it failed to do so, and then moved the folder into a new folder that Free File Sync created without my direction.
https://photos.app.goo.gl/GL8rGVT1D8TQ7QQN9
This is the view of the originating G drive from which Free File sync attempted the deletion without being directed to do so:
https://photos.app.goo.gl/V9kTiFCUCGrwfE9R6
I ran Agent Ransack, which found the newly created folder. It was a frightening experience.
FFS moved a folder from the originating drive and deleted from target drive
- Posts: 3
- Joined: 31 Aug 2026
-
- Posts: 2995
- Joined: 22 Aug 2012
> ... tried to delete a folder from the originating drive ...
You run three Mirror syncs, with left-side location G:\Cases II\Duarte v. AHA being the source for all three.
So, your G-drive is your originating (=source) drive, not your E-, C-, respectively F-drive.
Your Mirror sync will remove/delete any files and folders that do not, or no longer, exist in G:\Cases II\Duarte v. AHA from your respective right-side locations.
The part of the log-file you show, does not seem to be in conflict with that.
You run three Mirror syncs, with left-side location G:\Cases II\Duarte v. AHA being the source for all three.
So, your G-drive is your originating (=source) drive, not your E-, C-, respectively F-drive.
Your Mirror sync will remove/delete any files and folders that do not, or no longer, exist in G:\Cases II\Duarte v. AHA from your respective right-side locations.
The part of the log-file you show, does not seem to be in conflict with that.
- Posts: 3
- Joined: 31 Aug 2026
Indeed, the "G" drive is the originator. The E,C, and F drives are not the originators. It may be that the G drive is failing and Free File Sync noticed it.
