I'm sick of the freezing/disk access I get every time I create a new trigger while Task Scheduler scrapes all the log events together, and the feature is useless to me. Is there any way to disable that particular trigger type for good?

Failing that, is there any way to make its performance tolerable?

  • What happens if you clear the event logs first?
    – DavidPostill
    Dec 1, 2014 at 7:35
  • @DavidPostill: I assume if I cleared every one of the event logs, performance would be much improved. Unfortunately, this requires more effort and substantially more time every time I want to add another trigger, which I only do once every month or so at most, and furthermore wipes out log history, so I don't think that's a particularly profitable approach. Dec 1, 2014 at 8:04
  • You can save the logs before you clear them. In any case are logs more than one month old really that useful? In the end it's your decision as it is a tradeoff between more work and waiting ...
    – DavidPostill
    Dec 1, 2014 at 8:11
  • @DavidPostill: It looks more like a tradeoff between waiting and more waiting + more work from here, but perhaps I'm wrong. Dec 1, 2014 at 8:15
  • How to clear all Windows event log categories fast shows how to clear all the event logs from the command line. You could modify the answer to archive them first before clearing. Uses wevutil
    – DavidPostill
    Dec 1, 2014 at 8:21


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.