Hi, I think you may be too caught up in this detail regarding the second icon appearing in the notification area - that is simply because the Windows Task Scheduler triggering the Scheduled Task at the appointed date/time as you've set it and it is calling SyncBackPro to run the task under Session 0.
That is perfectly normal.
This is because the user sessions (that is, when you log into Windows Vista and/or later, it counts as a Session 1, 2, 3, etc), but automated scheduled task from WTS are always run in Session 0. These sessions are separate from one another and they do not interact with each other. Thus, the additional icon you see is due to WTS calling upon Pro to trigger the task, which is run in a different session, which will close by itself when it finishes.
For more information about Session 0, I suggest you read the following articles:
http://support.2brightsparks.com/knowledgebase/articles/211489-the-windows-task-scheduler
http://www.2brightsparks.com/resources/articles/understanding-sessions-in-windows.html
It doesn't matter if your profiles are in a Group or individual profiles, any profiles running under a Scheduled Task, Windows Task Scheduler will create a separate session of Pro to run the profiles. This additional icon is not created by us, it's by WTS.
Coming back to your original issue, that "Unknown Error" simply means there are two instances of the same profile that was bring run at the same time (Scheduled, etc), leading to both instances aborting each other out.
I suggest you review your profiles again and maybe check to see if there are schedules created within them that are configured to start at similar/same timings. If so, you may need to remove them.
That is perfectly normal.
This is because the user sessions (that is, when you log into Windows Vista and/or later, it counts as a Session 1, 2, 3, etc), but automated scheduled task from WTS are always run in Session 0. These sessions are separate from one another and they do not interact with each other. Thus, the additional icon you see is due to WTS calling upon Pro to trigger the task, which is run in a different session, which will close by itself when it finishes.
For more information about Session 0, I suggest you read the following articles:
http://support.2brightsparks.com/knowledgebase/articles/211489-the-windows-task-scheduler
http://www.2brightsparks.com/resources/articles/understanding-sessions-in-windows.html
It doesn't matter if your profiles are in a Group or individual profiles, any profiles running under a Scheduled Task, Windows Task Scheduler will create a separate session of Pro to run the profiles. This additional icon is not created by us, it's by WTS.
Coming back to your original issue, that "Unknown Error" simply means there are two instances of the same profile that was bring run at the same time (Scheduled, etc), leading to both instances aborting each other out.
I suggest you review your profiles again and maybe check to see if there are schedules created within them that are configured to start at similar/same timings. If so, you may need to remove them.