Hi, as explained briefly in my earlier post, this is due to how Windows Task Scheduler in Windows Vista or later runs Windows Sessions. When a scheduled task is run by WTS, it is launched in Session 0, which is invisible to the user. User sessions are usually in Session 1, 2, 3, etc. Due to this, there is no way for Session 0 to communicate with the user Session.
This is how Windows designed WTS and it's nothing to do with our program.
You can read this KB article on WTS for more info:
http://support.2brightsparks.com/knowledgebase/articles/211489-the-windows-task-scheduler
This is how Windows designed WTS and it's nothing to do with our program.
You can read this KB article on WTS for more info:
http://support.2brightsparks.com/knowledgebase/articles/211489-the-windows-task-scheduler