3 ms·
How is Windows Task Scheduler broken?
by fetbaffe 6y ago
How is Windows Task Scheduler broken?
- amw 6y agoCan't bulk-kill processes, for one. Not searchable, for two.
- Someone1234 6y agoYou can bulk kill with e.g. Get-ScheduledTask -TaskPath "\UpdateTasks\" | Stop-ScheduledTask That also demonstrates search too, by the way.
- fetbaffe 6y agoHaven't used it in a long time, but looking at it now, the GUI is definitely clunky and those features are missing. Wasn't there another GUI during the Windows XP days?
- WorldMaker 6y agoThat MMC snap-in hasn't changed much in the NT era of Windows. You might be recalling 95-ME's even worse task scheduler?
- josteink 6y ago> How is Windows Task Scheduler broken? Fundamentally. Try to schedule a simple script to run once an hour, while the user is logged in. No other conditions. Nothing complex. Wait an hour and wait to see one window pop open running your script. Wait one work-day. Work on your machine. Observe 10+ executions of that script, in parallel, on the mark the script was scheduled to run once. Watch this get worse every day, until reboot. And then it slowly starts collapsing on itself again. Not even this simple use-case works. It’s just unbelievably broken.
- jpalomaki 6y agoDid you check "run task as soon as possible after scheduled start is missed"? And what about "If task is already running, then the following rule applies: Do not start a new instance".
- josteink 6y agoNot sure. Why should those be needed? It says run once and it literally launches 10+ within the same 100ms. That’s just broken.