How to avoid having to push the Start button in RealTimeSync?

[Synchronizator]

So I have created a task in FreeFileSync, exported it to .ffs_batch file, imported that file to RealTimeSync, executed it by pressing Start - and it works: i.e. my backup folder got updated to the state in which the original is and keeps being updated

But now my question is: how do I start his monitoring and updating process automatically whenever my Windows 10 Enterprise 20H2 starts?

I do want to keep clicking that Start button - all I wanna see is an icon in the Tray notification to know if RealTimeSync is running and have 100% certainty that it is doing what it would be doing if I had opened its window and pressed that button myself

[xCSxXenon]

Save the RTS configuration and put it in your startup folder

%homepath%\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup

[Synchronizator]

So it is as simple as putting in

C:\Users\YOUR-USER-NAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup

a shortcut to a BAT file with content of e.g.

start "" "C:\Program Files\FreeFileSync\RealTimeSync.exe" "C:\MY SCRIPTS\FreeFileSync Jobs\test of automation.ffs_batch"


while also making sure that this LNK file leading to that batch file has its

Properties > Shortcut > Advanced Run as administrator

turned on to avoid blockades?

[xCSxXenon]

No, you use the .ffs_batch configuration to create a RTS configuration. The RTS configuration will be saved as a .ffs_real file

https://freefilesync.org/manual.php?topic=realtimesync

[Synchronizator]

So I have now

C:\Users\YOUR-USER-NAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\test of automation.ffs_real.lnk

and it does start RealTimeSync wit that job of mine. But despite turning on

[...]
Properties > Shortcut > Advanced Run as administrator
[...]

for it I get the

ERROR_ELEVATION_REQUIRED: The requested operation requires elevation. [AdjustTokenPrivileges(SeSecurityPrivilege)]

blockade info

[Synchronizator]

What has worked for me was going to

C:\Program Files\FreeFileSync\RealTimeSync.exe

and selecting

Properties > Compatibility > Settings > Run this program as an administrator

and then putting in the Start system folder an LNK leading to BAT which runs my FFS_REAL file

Because I can either do the above - or put in Start an LNK leading directly to FFS_REAL file, which does not work [i.e. the pogram does not start automatically after Windows boots up]. The same thing happens [i.e. RealTimeSync does not starts with Windows] if use such Registry hack

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]

"C:\\Program Files\\FreeFileSync\\RealTimeSync.exe"="RUNASADMIN"


which approach when utilized by me for every other program so far has no issue of running affected software through shortcut put in Start folder


So to sum up:

A] The help info at https://freefilesync.org/manual.php?topic=realtimesync should have a small summary at its beginning like:

1] Use FreeFileSync to create FFS_BATCH file with jobs

2] Import it to RealTimeSync

3] Export them to FFS_REAL file

4] Put shortcut to it in the StartUp folder

This way discussions like this one and that one viewtopic.php?t=1124 could be most likely avoided


B] Doing the above point A does not work for me

[Zenju]

https://freefilesync.org/faq.php#permissions-error

[Synchronizator]

[...]
B] Doing the above point A does not work for me

https://freefilesync.org/faq.php#permissions-error

Yes. When I deselect

Tools > Options > Copy locked files (requires administrator rights)
Tools > Options > Copy DACL, SACL, Owner, Group (requires administrator rights)

I can then relay on having just

C:\Users\YOUR-USER-NAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\test of automation.ffs_real.lnk

without a BAT intermediary executing it. But then RTS gets blocked when trying to update e.g.

C:\MY PORTABLES\Mp3tag\Mp3tagError.log

and thus after all I do need to use such BAT scripted workaround


So thank you both for you help, as I am now able to operate - but the last issue of this conundrum would be to have an explenation for why

[...]
RealTimeSync does not starts with Windows] if use such Registry hack

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]

"C:\\Program Files\\FreeFileSync\\RealTimeSync.exe"="RUNASADMIN"


which approach when utilized by me for every other program so far has no issue of running affected software through shortcut put in Start folder
[...]

which forces me to use less elegant solution

[...]
going to

C:\Program Files\FreeFileSync\RealTimeSync.exe

and selecting

Properties > Compatibility > Settings > Run this program as an administrator
[...]

[Synchronizator]

Long story short:

the optimal way to deal with the whole shebang is to use options

FreeFileSync > Tools > Options > Copy locked files (requires administrator rights)
FreeFileSync > Tools > Options > Copy DACL, SACL, Owner, Group (requires administrator rights)

then implement this REG hack

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]

"C:\\Program Files\\FreeFileSync\\FreeFileSync.exe"="RUNASADMIN"
"C:\\Program Files\\FreeFileSync\\RealTimeSync.exe"="RUNASADMIN"


then finally create an LNK with its Target set to

C:\Windows\System32\cmd.exe /c start "" "C:\Program Files\FreeFileSync\RealTimeSync.exe" "C:\q\FreeFileSync _ RealTimeSync - Jobs\TEST JOB.ffs_real"


and in the end put this LNK it in the

C:\Users\YOUR-USER-NAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\

system folder - without a need to having selected for it the

Properties > Advanced > Run as administrator

option


This way the elevated synchronization process will not skip up-front potentially multiple items in targeted paths, user does not have to deal with an intermediary launcher script and bypasses the UAC restrictions - which built-in Windows feature is the culprit that prevents anything requiring Administrator rights to be auto-launched directly from the StartUp folder, even if this operating system's security measure will be partially subdued when user selects

Control Panel > All Control Panel Items > User Accounts > Change User Account Control settings > Never notify

option. And so, this deals with the

[...]
issue of running affected software through shortcut put in Start folder
[...]

mystery


And at the very end the only thing that still will has to be dealt with are some mandatory Exclusions for Filter in FFS like e.g.

AppData\Local\Microsoft\WindowsApps\
AppData\Local\Temp\


and some individual ones like for example

AppData\Local\BraveSoftware\Brave-Browser\User Data\Default\Cache\Cache_Data\
AppData\Roaming\ASCOMP Software\BackUp Maker\logs\*.log~


if user happens to use such programs that use blocked files


But if my above explanation and solutions are wrong in any way - then do please correct me