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
    2023-03-06T23:26:23+00:00

    Since my previous post about this issue I've tried additional measures mentioned in this thread; none have worked. I've been racking my brain trying to find what's different, and why this Scheduled Task works on some setups and not others for no discernable reason. Finally noticed something interesting.

    Windows Version:

    21H2 -> Scheduled Task OK!

    22H2 -> Clean OS install -> Scheduled Task OK!

    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!

    It appears that something in the 21H2 -> 22H2 upgrade process causes existing profiles to have this trouble.

    Creating a NEW user profile and Scheduled Task to "run whether the user is logged on or not" works reliably!

    This is not a fix for what looks like a bug in the Windows upgrade process, but it does help narrow down the issue.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. 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
  3. Anonymous
    2022-10-14T19:10:52+00:00

    Was this answer helpful?

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