Windows 11 22H2 upgrade breaks "Run whether user is logged on or not" scheduled tasks

Anonymous
2022-10-09T09:00:28+00:00

I have a number of scheduled tasks with the "Run whether user is logged on or not" option set, with the default setting of storing the password for the account.

Everything was running fine, until the 22H2 update.

Now such tasks won't start, yielding

"Task Scheduler failed to start "xxx" task for user "yyy". Additional Data: Error Value: 2147943726.

Re-entering the password for the (local) user account does not help.

If I check the "Do not store password" option the task can start, but this prevents the task from accessing network resources.

Repro'ed on two machines, so doesn't feel like a configuration issue.

Any clue?

Windows for home | Windows 11 | Accounts, profiles, and login

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

63 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2022-10-14T19:10:52+00:00

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-10-16T09:07:47+00:00

    Hi sba923

    Thank you for your feedback and sorry for my late response.

    This problem is under investigation, and we are actively submitting it to the internal team. If there are new results, I will post back again.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-11-13T06:23:34+00:00

    Hello everyone,
    I have the same issue, there are updates?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2022-11-13T09:31:46+00:00

    Having the same problem, I've overridden by changing the task to use group "administrators" instead of my own account (even I am, of course, administrator).

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  5. Anonymous
    2022-11-17T20:05:11+00:00

    Hi sba923

    Thank you for your feedback and sorry for my late response.

    This problem is under investigation, and we are actively submitting it to the internal team. If there are new results, I will post back again.

    Any luck with the internal team? This is starting to trickle into production environments.

    Was this answer helpful?

    0 comments