Windows 10 scheduled tasks are not running
I have created couple of tasks under Task scheduler (Win 10):
Unfortunatelly, the tasks do not run autmatically as scheduled. Their "Next run time" is changed as expected (each 10 or 5 minutes), but "Last Run Time" remain the same and nothing is done. There is even no record in history (15:23 was manual run half an hour ago):
In case I run the tasks manually, they work well. Conditions tab is empty for all of them. Any idea, what could be wrong?
47 Answers
I have a laptop and the same problem occured to me.
I resolved the issue DISABLING the option "Start the task only if the computer is on AC power" on the "Conditions" tab and "Power" group.
My laptop was indeed AC powered, but must be some kind of bug in this detection.
2I have same issue here. And found one workaround which may help someone to solve this. If I set start date and time to be in future (near future, just 1 minute), task will be triggered and will repeat at specific interval.
Until user who start the task sign out! If it signout, task won't start. Off-course Security options is set to Run whether user is logged on or not.
3It appears that repeated tasks were broken by the Anniversary Update. Sad :/ There is no known work-around at this point other than to stop using the Task Scheduler and move to a third party solution.
More info here - there are a few workarounds suggested but none that are usable. One is to run the task under the SYSTEM account, but this is no good for anyone requiring a specific AD user.
I'm seeing the same thing on some servers running Server 2012 but it only seems to happen after the system is rebooted. The solution I've found is editing the trigger and changing the start time slightly. Once I've done that the task runs fine. Will have to see if the problem comes back after the next reboot.
1Please check your Trigger tab and open your trigger. I had a trigger end up with the enabled box unchecked despite never unchecking it. The main screen still showed enabled and ready for the task when this was unchecked and I had this exact behavior.
This may be helpful for others in the future, but I had a scheduled task that I was running as myself, but escalated, to create command line Volume Shadow Copies. I eventually reconfigured it to run as SYSTEM and then it started running again.
I had the same problem.
Running on Windows Server 2008.
Tried all the solutions proposed here, and from other forum. Nothing works.
The only thing that worked for me, was to convert the BAT to EXE.
Then it run perfect.
Somehow, I dont know if it was an update from Windows or what, but from one minute to another, Taskman started to have this issue, and this was the only thing that made it work again
Hope it helps
Regards!
