Hi (remember me? Image may be NSFW.
Clik here to view.
)
I'm getting something similar in a Windows 7 VM with SE, too
1) Try it with just a log-off (not a full restart) then log back in. Does the background instance now persist?
2) Try it with the profiles set not to run On Login (temporarily) but SE itself still set to Start With Windows. Does the background instance now persist?
I think what's happening is that there's some confusion over return codes (to the Scheduler, possibly by the Scheduler). When I try to do both on startup (open SE and also run profiles) the Task that runs SE (and should stay open) is logging a return code of 0 (whereas there shouldn't be a return code unless/until you (or something else) close/s that open instance). I think that spurious return code is closing down the Task that should stay open, which closes SE (same as if you right-clicked the Task in Scheduler while Running, and selected End). Ending the Task closes the instance of SE/Pro...
Clik here to view.
)I'm getting something similar in a Windows 7 VM with SE, too
1) Try it with just a log-off (not a full restart) then log back in. Does the background instance now persist?
2) Try it with the profiles set not to run On Login (temporarily) but SE itself still set to Start With Windows. Does the background instance now persist?
I think what's happening is that there's some confusion over return codes (to the Scheduler, possibly by the Scheduler). When I try to do both on startup (open SE and also run profiles) the Task that runs SE (and should stay open) is logging a return code of 0 (whereas there shouldn't be a return code unless/until you (or something else) close/s that open instance). I think that spurious return code is closing down the Task that should stay open, which closes SE (same as if you right-clicked the Task in Scheduler while Running, and selected End). Ending the Task closes the instance of SE/Pro...
