Ok, I've got this fully correct now I think. In some cases in previous builds you could end up with both registry and Task Scheduler startup entries, which is obviously neither intended nor desired. This was rare, and only if you changed configurations. However, it could happen.
I fixed the Task Scheduler (elevated rights) detection so it properly detects if the GUI and Core Engines are set to start with elevated rights they now correctly identify whether they are set to start with the current user or all users.
I've described this before, but wanted to elaborate. I *may* backport this simple fix. We'll see.
It MAY take one run to 'clean things up', so the first run may look funny, or be inaccurate, but from then on everything will be ok. For new installs, everything will be fine of course.
This change coming in v4.09.30 beta.
Saturday, 12 March 2011
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment