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: Most helpful
Most helpful Newest Oldest
  1. 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
  2. Anonymous
    2023-05-23T19:22:25+00:00

    I can confirm the same,. Just tested this:

    22H2 -> Upgrade from 21H2, user profile is present before upgrading to 22H2 -> TASK FAILED

    22H2 -> Upgrade from 21H2, new user profile created after upgrade and new task created -> Scheduled Task OK!

    Any update on the fix?

    Ivan

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2022-10-13T03:03:05+00:00

    I have been trying the same for about a week now. I have tried recreating a new task, stop the existing instance if the task is already running, tried several programs: powershell, word, chrome, edge and just a plain cmd prompt, I even tried another account and nothing seems to be working. I've tried resetting my password for my microsoft account and a local account. This has been one of the worst updates I've encountered with authorization and authentication issues.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2022-10-10T12:20:38+00:00

    Same result with a new task created from scratch

    (I'd like to share the task's definition XML here, but copy/paste will only get me garbage...)

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2022-10-10T11:31:58+00:00

    Thanks for dealing with my issue.

    As I said in my initial message, re-entering the credentials doesn't solve the issue; so this is not related to a password change (the password hasn't changed, BTW).

    I'll try creating a new task from scratch with the "Run whether user is logged on or not" option and see what this gets me.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments