Same result with a new task created from scratch
(I'd like to share the task's definition XML here, but copy/paste will only get me garbage...)
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
Thanks for dealing with my issue.
As I said in my initial message, re-entering the credentials doesn't solve the issue; so this is not related to a password change (the password hasn't changed, BTW).
I'll try creating a new task from scratch with the "Run whether user is logged on or not" option and see what this gets me.
Hello sba923
Welcome to Microsoft Community.
Glad to be here assist you
According to your/windows11/accounts, profiles, and login categories, we know that your problem is "After updating to Windows 11 22H2, your task scheduler runs with Error Value: 2147943726". If my understanding is wrong, please correct me at any time.
Before finding the cause of the problem, could you please confirm some details:
Whether the password of the account executing this task been changed? The error value of 2147943726 is due to the latest change of the system user password configured when the task was created.
In addition, could you try deleting this task on one of the computers and then re-creating it to see if it can be successfully executed?
Please feel free to let me know if you got any further updates, thanks.
Best regards,
Chandy|Microsoft Community Support Specialist
* Beware of scammers posting fake support numbers here.