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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2023-03-08T22:06:58+00:00

    Additional data as follow-up to previous post....

    In the task's history, after the task with stored password fails to launch the following two events are logged in TaskScheduler history:

    ID 110, Info, "Task triggered by user"

    ID 101, Error, "Launch Failure"

    Task Scheduler failed to start <task name> task for user <username>. 

Additional Data:  Error Value:  2147943726

    The following article about known issues with Credential Guard is dated 12/15/2022. About 3/4 down the page, the first item under "Previous known issues that have been fixed", a substantially similar issue is presented (task fails to run, same error value as shown above). The article claims that problem was fixed by a Windows 10 Cumulative Update in 2017, so perhaps this is an "old issue" that has returned...

    Windows Defender Credential Guard - Known issues | Microsoft Learn

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-03-08T23:09:41+00:00

    I'm not affected by this issue anymore (I created new accounts to get my task to fire on startup) so I can't verify if this helps, but here are a couple of other things to look into if you upgraded from 21H2 to 22H2 and have an affected account/machine:

    Instead of creating a new account, reset the password for the affected user and then see if the Scheduled Task is able to run.

    Also have a look at an article that discusses LSA Protection being enabled by default in Windows 11 22H2. It's not directly related to the issue with Scheduled Tasks, but the problem sure looks familiar:

    https://kb.vmware.com/s/article/90938?lang=en_US

    Starting with Windows 11 22H2 Microsoft changed the default setting for the LSA "RunAasPPL" to enable.

     

    This setting will require administrator UAC login for the installation, if the application installation context is "User" and the Admin Privileges selection is "YES".

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-03-08T23:42:29+00:00

    Been there, done that -- no help. Does seem related to Credential Guard (not LSA, since that was already running before 22H2), but it is something deeper than just the user's current key.

    I've found workarounds with less impact (to me) than deleting/recreating my profile. But I want it to WORK RIGHT! Be nice if there was some procedure to just fully "reset" whatever part of credential store / credential manager / credential guard is screwed up.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-03-16T16:46:09+00:00

    Thank you for this information. I am going to test this. As far as changing /copyall to DATSO. I made that change and my scripts seem to work without the need to be logged in. It's interesting that I've never had a problem with my .bat scripts using /copyall until the 22H2 update.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2023-04-26T19:16:48+00:00

    Having the same issue on an Windows 11 system that was just upgraded to 22H2. Same error value of 2147943726 for the job. Anybody find a way of resolving this yet?

    I see it has been months with no update from Microsoft...

    Was this answer helpful?

    0 comments