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(25.6, 47%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
WS2012, patched through 2023-01. Scheduled Tasks whose trigger is "Startup" are rarely firing at startup, effective sometime in the last several weeks. Either they all fire (but that's been very rare) or none fire. Affects custom Tasks and those built into Windows. SFC /SCANNOW couldn't find anything to fix. Got anything I can check to try to fix it?
![](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(67.2, 68%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELT%3C/text%3E%3C/svg%3E)
Hello
Thank you for your question and reaching out. I can understand you are having query\issues related to Task Scheduler.
It may be Bug that if the password cannot be verified when 'When the computer starts' has been selected.
Alternatively Please put the script or program shortcut in the startup folder for all users %allusersprofile%\Microsoft\Windows\Start Menu\Programs\Startup
Reference :
--If the reply is helpful, please Upvote and Accept as answer--
No. Not an auth problem. As per original post--
And what should have been in the original post--
I haven't checked to see if tasks with other trigger types run; I need to do that. A specific task that should run at startup has been my focus because it is important for managing the server.
Clearly, the Task Scheduler is broken for Startup tasks. Trying to avoid rebuilding this server, which only has a few months to live anyway before it's replaced with WS2022. Have considered writing a PowerShell command that uses Get-ScheduledTask, filtering on tasks with a Startup trigger, and run them. That could be run with a shortcut as you suggest or from HKLM...\Run. But if there's a way to fix Task Scheduler that isn't too draconian, that would be preferable.