Sounds like something on that PC is simulating a key-press on the Del key? With the profile in question selected (highlighted)...and Free has the focus (is topmost application on desktop)
It's not something we've ever (TBOMK) had reported before, in any version (and the main UI is the same across SE, Pro and Free so people have had plenty of time to spot it since 2008)
If I'm right, unselecting all profiles should stop it (click in the empty area below the bottom profile), as then the Del keypress should have no effect (it doesn't know 'which one', so does nothing)
There is a command-line option to (for example - where 'killthis' is a dummy profile I created)
"C:\Program Files (x86)\2BrightSparks\SyncBackFree\SyncBackFree.exe" -delete "killthis"
which will do exactly that, but definitely won't prompt you (it will just delete it silently, using another instance of Free to do so, which closes afterwards; I just tested to be sure)
If you have your backups Scheduled, note that you don't need Free running as a foreground application anyway (a Schedule will start/use/close another instance - like the above does - because the Task Scheduler is also a command-line trigger)
It's not something we've ever (TBOMK) had reported before, in any version (and the main UI is the same across SE, Pro and Free so people have had plenty of time to spot it since 2008)
If I'm right, unselecting all profiles should stop it (click in the empty area below the bottom profile), as then the Del keypress should have no effect (it doesn't know 'which one', so does nothing)
There is a command-line option to (for example - where 'killthis' is a dummy profile I created)
"C:\Program Files (x86)\2BrightSparks\SyncBackFree\SyncBackFree.exe" -delete "killthis"
which will do exactly that, but definitely won't prompt you (it will just delete it silently, using another instance of Free to do so, which closes afterwards; I just tested to be sure)
If you have your backups Scheduled, note that you don't need Free running as a foreground application anyway (a Schedule will start/use/close another instance - like the above does - because the Task Scheduler is also a command-line trigger)