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 No comments

63 answers

Sort by: Oldest
  1. Anonymous
    2022-10-10T08:58:19+00:00

    Hello sba923

    Welcome to Microsoft Community.

    Glad to be here assist you

    According to your/windows11/accounts, profiles, and login categories, we know that your problem is "After updating to Windows 11 22H2, your task scheduler runs with Error Value: 2147943726". If my understanding is wrong, please correct me at any time.

    Before finding the cause of the problem, could you please confirm some details:

    Whether the password of the account executing this task been changed? The error value of 2147943726 is due to the latest change of the system user password configured when the task was created.

    1. Try going to the properties of the task.
    2. Under the General tab, click Change User or Group
    3. Enter the user name in the "Enter the name of the object to be selected" field.
    4. This will require authentication and provide your credentials.

    In addition, could you try deleting this task on one of the computers and then re-creating it to see if it can be successfully executed?

    Please feel free to let me know if you got any further updates, thanks.

    Best regards,

    Chandy|Microsoft Community Support Specialist


    * Beware of scammers posting fake support numbers here.

    Was this answer helpful?

    0 comments No comments
  2. 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 No comments
  3. 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 No comments
  4. Anonymous
    2022-10-11T18:34:23+00:00

    I have exactly the same issue. Also with login with RDP connection to server. Saved password isn't working, but when I use the exact same password at the credential screen it works. Removing tasks and creating new ones doesn't work. Issue remains. Scheduled tasks aren't started because of credential issues.

    Was this answer helpful?

    0 comments No comments
  5. 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 No comments