Re: "start with windows" runs but then exits

I didn't mean disable the profiles (completely), I meant to disable their Run On Logon status. This is why their Tasks didn't disappear from the Scheduler, and which is why their exit codes are 0xFFFFFF96 which means 'profile disabled'

But it's interesting that the open instance of Pro stays open if you do that anyway (disable entire profile) - the significant part being that nothing is sending an exit code of 0 any more (they're sending 0xFFFFFF96, aka -106).

Because I think something is detecting that 0 as the exit code of the wrong task (and thus closing your stay-open instance) - and once you have nothing sending a 0 ('Success, no error') exit code, the stay-open instance miraculously stays open. Which suggests to me the stay-open instance isn't sending a 0 wrongly, but that the Scheduler is receiving more than one 0 in swift succession, and is confusing which program instance sent them (especially as they have the same executable name, just different arguments)

Here's another test - create a Group called WhateverYouLike and add those three profiles to it. Then unset the When > OnLogon of the individual profiles, and set it for the Group instead. Then try again.