How are you running (triggering) the profile? Because it sounds like what you 'should' normally see (or 'not see') if run on a Schedule in Vista or later.
http://www.2brightsparks.com/resources/ ... 011.html#3
Note that we cannot control what type of session Windows decides to use for a Scheduled Task (sometimes PCs that have run such Scheduled profiles 'hidden' in session-0 for ages will, sometimes at random, decide to do so in a 2nd 'foreground' (Session-1) instance). Sounds like your Vista used to do the latter all the time, and only just started to run them in the normal hidden session-0 mode, maybe c/o a Windows Update)
There's nothing we can do to influence that, but there is a feature in the beta V7 that enables you to see/control what is happening with profiles running in other instances of the program (which a Schedule - or any other command-line trigger - will always use), if you want to try it.
http://www.2brightsparks.com/resources/ ... 011.html#3
Note that we cannot control what type of session Windows decides to use for a Scheduled Task (sometimes PCs that have run such Scheduled profiles 'hidden' in session-0 for ages will, sometimes at random, decide to do so in a 2nd 'foreground' (Session-1) instance). Sounds like your Vista used to do the latter all the time, and only just started to run them in the normal hidden session-0 mode, maybe c/o a Windows Update)
There's nothing we can do to influence that, but there is a feature in the beta V7 that enables you to see/control what is happening with profiles running in other instances of the program (which a Schedule - or any other command-line trigger - will always use), if you want to try it.