Hi, it makes no difference as 'run this profile when I login to Windows' is still relying on WTS to run the task - it creates a New Task within WTS to run on Login; this makes the task run in Unattended mode.
And as you are running V5, corrupted profiles will be deleted during an Unattended run without prior warning.
However, in V6 (V6.0.0.15 onwards), code have been added to the program so that corrupted profiles will NOT be automatically deleted during an Unattended run. During the next Attended run (aka, manual run), SyncBack will notify the user that the profile is corrupted and ask if he wants it deleted or not.
Also, if you upgrade to V6 now, you will be entitled to a free upgrade to V7 upon its eventual release.
http://www.2brightsparks.com/bb/viewtopic.php?f=15&t=10802&p=41877&hilit=enjoy+an+upgrade+to+V7+at+no+extra+charge#p41877
Ultimately, you will still need to figure out WHY and WHAT is causing the profiles to be corrupted in the first place, as upgrading to V6 or not does nothing to solve the original cause of profile corruption.
And as you are running V5, corrupted profiles will be deleted during an Unattended run without prior warning.
However, in V6 (V6.0.0.15 onwards), code have been added to the program so that corrupted profiles will NOT be automatically deleted during an Unattended run. During the next Attended run (aka, manual run), SyncBack will notify the user that the profile is corrupted and ask if he wants it deleted or not.
Also, if you upgrade to V6 now, you will be entitled to a free upgrade to V7 upon its eventual release.
http://www.2brightsparks.com/bb/viewtopic.php?f=15&t=10802&p=41877&hilit=enjoy+an+upgrade+to+V7+at+no+extra+charge#p41877
Ultimately, you will still need to figure out WHY and WHAT is causing the profiles to be corrupted in the first place, as upgrading to V6 or not does nothing to solve the original cause of profile corruption.