Hello everyone,
I have the same issue, there are updates?
Windows 11 22H2 upgrade breaks "Run whether user is logged on or not" scheduled tasks
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.
63 answers
Sort by: Newest
-
Anonymous
2022-11-13T06:23:34+00:00 -
Anonymous
2022-10-16T09:07:47+00:00 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.
-
Anonymous
2022-10-13T03:03:05+00:00 I have been trying the same for about a week now. I have tried recreating a new task, stop the existing instance if the task is already running, tried several programs: powershell, word, chrome, edge and just a plain cmd prompt, I even tried another account and nothing seems to be working. I've tried resetting my password for my microsoft account and a local account. This has been one of the worst updates I've encountered with authorization and authentication issues.
-
Anonymous
2022-10-11T18:34:23+00:00 I have exactly the same issue. Also with login with RDP connection to server. Saved password isn't working, but when I use the exact same password at the credential screen it works. Removing tasks and creating new ones doesn't work. Issue remains. Scheduled tasks aren't started because of credential issues.