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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2022-12-29T13:37:03+00:00

    I use Robocopy to run the batch file to access network shares. I need scheduled tasks to run like it did prior the the 22H2 update. Executing locally only is not what I need.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-12-29T07:53:48+00:00

    Hello everyone,

    Santa fixed the issue. This morning I simply tried to check the option "Do not store password. The task will only have access to local computer resource".

    Finally the task succeded running as my admin account.

    Hope this will help!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-12-27T16:25:28+00:00

    Hello. What is the status of task scheduler not working correctly after updating to 22H2? I am reliant on being able to enter the domain administrator account username and password whether logged in or not and running Robocopy batch files to copy user files for backup. I've run these batch files for years without any issues. Since updating multiple workstations that run these batch files, the scheduled task does not function. These batch files work fine when executed manually. On other workstations that I have not allowed to update to 22H2, there is not a problem with task scheduler executing the batch files and working properly. Deleting and recreating the scheduled task does not resolve the issue. These are run under the domain admin account. Nothing has changed on these workstations except the feature update. It is the 22H2 update that is causing the failure of the scheduled task for the batch files. I am not able to uninstall this 22H2 update because it has been more than 10 days. I either want to be able to uninstall 22H2 or get a patch sent out to install and resolve.

    Was this answer helpful?

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