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 went ahead and set run task when user is logged in as the domain admin, highest privileges. Robocopy log reports error, you do not have Manage Auditing rights. This is the domain admin profile that has full access to the folders and files.
As I mentioned, script works fine when run manually copying everything with correct permissions.
If the script is executed manually
Assume "log on as batch job" is set in secpol, "start in" is a folder that the user can read/write, and the script works fine from a command prompt, but does the scheduled task with "Run whether user is logged on or not" run when kicked-off manually in the task scheduler?
If not, does the task run if setting trigger to "At Log On", then assign the user running the task, and set "Run only when this user is logged-on" and see if that kicks off when you log in? This does not solve your issue but may be interesting to know if that at least works.
You may also want to run your script on a physical machine outside of your existing set-up, just to be sure nothing crazy is going on with virtualization.
I went ahead and wiped a laptop, installed the latest version of windows 11 22H2 and set task manager to run my Robocopy script. Task fails access denied error and the task never stops running. This script is used to copy data across network shares using the domain admin profile.
If the script is executed manually, it runs fine and copies all the files correctly across network shares.
I have the same task and Robocopy script running on some windows 11 21H2 and windows 10 21H2 boxes. The task and script work fine. I believe it's some kind of security / permission issue in 22H2 that is breaking my process. So, I am still in limbo with this issue and 22H2.
Since my previous post about this issue I've tried additional measures mentioned in this thread; none have worked. I've been racking my brain trying to find what's different, and why this Scheduled Task works on some setups and not others for no discernable reason. Finally noticed something interesting.
Windows Version:
21H2 -> Scheduled Task OK!
22H2 -> Clean OS install -> Scheduled Task OK!
22H2 -> Upgrade from 21H2, user profile is present before upgrading to 22H2 -> TASK FAILED
22H2 -> Upgrade from 21H2, new user profile created after upgrade and new task created -> Scheduled Task OK!
It appears that something in the 21H2 -> 22H2 upgrade process causes existing profiles to have this trouble.
Creating a NEW user profile and Scheduled Task to "run whether the user is logged on or not" works reliably!
This is not a fix for what looks like a bug in the Windows upgrade process, but it does help narrow down the issue.
Update regarding Scheduled task. Disabling Credential Guard allowed the scheduled task to run One time successfully, after that, the task continues to run and will not start over again. I've checked if the running tasks does not stop force it to stop and stop the task if it runs longer than 2 hours. So, my attempt at fixing this issue has failed. My windows 10 21H2 and windows 11 21H2 boxes are working fine for Task Scheduler and my Robocopy Scripts. I've set those not to allow a feature update for 365 days in group policy. Not sure if Microsoft is going to attempt a fix regarding this.
