$ 0 0 Yes, when using TaskScheduler 2.0 (Vista and later) the RunOnlyIfLoggedOn property will throw an exception. You must instead do as instructed and register the task using an InteractiveToken setting.