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-11-22T16:24:21+00:00

    My entire production team has the exact same issue after upgrade to 22H2 yesterday.

    Two days ago it was working fine (pre-update).

    @chandy what's the status of internal investigation and when can we expect fixes please?

    Looking forward to having this working again.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-11-23T01:00:54+00:00

    Dear everyone

    As it can be seen from the following statement, the next update should be available in December, see this image:

    November 8, 2022—KB5019980 (OS Build 22621.819) - Microsoft Support

    However, due to the holidays, it is expected to wait until January 2023, which is the latest progress of the investigation.

    Best Regards!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-12-21T16:52:59+00:00

    I am also having the issue with task scheduler. My robocopy scripts do not function in task scheduler since I updated to 22h2. I am not able to roll back since it's been 10 days. The robocopy scripts work fine if executed manually. They also work on workstations that have not been updated to 22h2. This is a critical screw up, I am reliant on scheduled tasks being able to run whether user is logged in or not. Hopefully this will be resolved very very soon.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-12-21T20:13:54+00:00

    I am having a similar issue. I've checked the user account, which the user domain admin, was never was changed anyway. I have deleted the task and set it up again. Running my scheduled Robocopy batch files have been working for years. Now on any workstations that have been updated 22H2, my scheduled tasks no longer function. Since the update to 22H2 I am receiving the error ERROR 5 (0x00000005) Getting File System Type of Source Access is denied when it executes the batch file. The task is being run under the Domain admin account and has never had any an issue until I updated to Windows 11 22H2. The batch files work fine when executed manually. On some workstations that have not been updated to 22H2, there is no problem, they are still working. I'd like to see this resolved fairly soon.

    Mike Kerwin

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2022-12-25T19:58:11+00:00

    @chandy we are still experiencing the same issue. At this point is there a way to get this escalated?

    Was this answer helpful?

    0 comments No comments