| Event Id | 328 |
| Source | Microsoft-Windows-TaskScheduler |
| Description | Task Scheduler stopped the "%2" instance of task "%1" because the computer is no longer idle. |
| Event Information | According to Microsoft : Cause :This event is logged when Task Scheduler stopped the instance of task. Resolution : Fix task configuration settings The task was stopped due to a configured setting. Possible causes include: 1.The task ran for longer than the maximum configured run time. 2.The task was configured to stop when the computer switched to battery power. 3.The task was configured to stop when the computer is no longer idle. 4.The task was configured to stop when a new instance of the task is triggered. This behavior might be as expected. However, if the behavior was unexpected you can reconfigure the task configuration settings. To update the task settings and conditions: 1.Click the Start button and type Task Scheduler in the Start Search box. 2.Select the Task Scheduler program to startTask Scheduler. 3.Select the task to configure by locating the task in the task folder hierarchy. Right-click the task, and select Properties. 4.On the Settings and Conditions tabs, update the task settings and conditions. 5.Click OK. Verify: To verify that the execution of a task has completed as expected: 1.Click theStart button and typeTask Scheduler in the Start Search box. 2.Select theTask Scheduler program to start Task Scheduler. 3.Select the task to run by locating the task in the task folder hierarchy. 4.On theActions menu clickRun. You can also clickRun in the Actions pane. 5.Click theHistory tab for the task to verify that it contains events indicating the task was registered successfully. Also, ensure that the task completed successfully or that the task timed out as expected. |
| Reference Links | Event ID 328 from Source Microsoft-Windows-TaskScheduler |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.