This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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?
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.
Broken features are one thing. Not acceptable, for sure.
But where data loss is at risk e.g. due to Windows 11 upgrade has broken File History - Microsoft Community, this is even worse. What would be the appropriate term?
Microsoft, are you listening?
Well, January 2023 is gone. Is the fix delivered as announced? Doesn't look like it.
I hope MS didn't fire the people who could've fixed this?
If your scheduled tasks do require access to network resources (and thus authentication with saved credentials), you're doomed as this is precisely what is broken.
Does your IT have a support contract with Microsoft? Maybe that would be an avenue worth pursuing...
sba923, we do not have a support contract with Microsoft. However, like the March 9 2021, update to windows 10 that caused so many of my workstations to blue screen when users would try to print, it's an issue that Microsoft should acknowledge and resolve. This windows 11 feature update 22H2 served no particular purpose as far as I can tell. For myself I've reformatted and reloaded several computers and installed windows 11 21H2, which does not seem to be affected by the task scheduler issue. I did the same with a couple of windows 10 boxes moving back to 21H2. But it was terribly time consuming. I've delayed feature updates for 365 days on those workstations. This allows task scheduler and my Robocopy scripts to work in my environment across network shares like before. However, I do not know if Microsoft intends to do anything about this issue. There are of course 3rd party tools that would accomplish what I am trying to achieve, but as a not-for-profit entity, this would cause needless expense.
Somewhere in the history of posts related to scheduled tasks failing to run scripts is reference to an executable named Elevate. Info found here How to start programs elevated from a batch file (winability.com) It was shared as a fix for the issue. It is easy to implement and worked for me. For me, the best I can remember, a feature update as far back as Windows 10 broke scheduled scripts that copied things to a UNC path and between UNC paths. some time later, a subsequent update apparently fixed the issue (can't say which because I ran the "Execute script.cmd" tasks for a good while and having free time one day, tried the old way and it worked.) has worked ever since through all feature updates to Windows 11.
