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.
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.
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!
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.
Hi sba923
Thank you for your feedback and sorry for my late response.
This problem is under investigation, and we are actively submitting it to the internal team. If there are new results, I will post back again.
Any luck with the internal team? This is starting to trickle into production environments.
Hi sba923
Thank you for your feedback and sorry for my late response.
This problem is under investigation, and we are actively submitting it to the internal team. If there are new results, I will post back again.
