FreeFileSync Forum

I have been playing around with this and I really like the idea of being able to go back in time and capture something done previously. I have tried both settings and prefer the timestamp on the file name as opposed to the timestamp on the folder.

I noticed something that could be an issue. When a ...

Undoing the "run under highest privileges" has me back to the original issue. See attachment.

The script runs fine when invoked as a foreground task, fails when invoked by the task scheduler. The entry in the scheduler was created to run under the user who created the entry. In the app the ...

I was just looking at the links above. I have my job set to run under highest privileges'. I'm gonna undo that and see what happens this evening.

This backup job is set to run a 02:00. The user is logged in but the screen is locked. If I run this manually everything is fine, no errors. When run out of the task scheduler this job fails with the unable to log in message. See attachment.

I have validated that the user id on the Windows machine ...

I'll watch this the next time I do a backup and 1) make sure there is only 1 copy running and 2) check the setting mentioned in the other thread. Thanks for the pointer to the other conversation.
File I/O and timestamping can be a tough nut to crack.

I am running the donation version - 12.2 64 bit. My last few syncs the timestamp showing the completion of the sync has not updated.