The Task Scheduler history shows that Defrag has run at completely random times during day, but I’ve set it to run only weekly (or monthly)! What’s going on?
You won’t see this random behavior if the machine is idle and on long enough at the originally scheduled defrag time. On the other hand, if you use the computer most of the time when it’s on, you might notice that the ScheduledDefrag task started and stopped again over a few days in an attempt to make a full run. The ScheduledDefrag task may have run during lunch, during a meeting, on the weekend, or (on your home computer) during a run of television shows you watch. The ScheduledDefrag task runs only when Task Scheduler detects that the computer is idle, typically when there is no user input. Moving the mouse or pressing a key will render your computer “not idle.” Other run-on-idle tasks may get priority over ScheduledDefrag and therefore the task will wait to start. If Disk Defragmenter doesn’t finish a run between one run of “idle” and “not idle,” Task Manager will wait for the next idle condition, wait for any tasks ahead of the ScheduledDefrag in the Task Scheduler queue, and then
Related Questions
- In trial version when macros run using scheduler it shows registration window that I have to manually click. Does this registration window show up in purchased version?
- Can I run Mil Shield from command line, from Task Scheduler or from a batch script?
- Can I run Advanced Task Scheduler hidden so user has no access to it?
