Task Scheduler may write Event ID 414 entries mentioning "Task Scheduler service found a misconfiguration in the NT TASK\task name" in the System Event log. This happens if the program or script which the task was configured to launch, is missing.
For example, here is a 414 event from the System log, showing the task name as well as the file name that’s configured to run. In this case it’s the Restore Point Creator task causing the problem.
Log Name: System Source: Microsoft-Windows-TaskScheduler Date: Event ID: 414 Task Category: Task Misconfiguration Level: Warning Keywords: User: SYSTEM Computer: W10Insider Description: Task Scheduler service found a misconfiguration in the NT TASK\Restore Point Creator definition. Additional Data: Error Value: C:\Program Files\RP Creator\rpcreator.exe.
This task was originally added by a 3rd party program but the program no longer exists in the system. The file "C:\Program Files\RP Creator\rpcreator.exe" (nor the folder path) was present, which caused Scheduler to log it (Event ID 414) every time the task ran. The obsolete task can be deleted using Task Scheduler.
Delete the Invalid Task Using Task Scheduler
Click Start, type scheduler. Click Task Scheduler in search results. In the Task Scheduler library, right-click the task named "Restore Point Creator" (as mentioned in the log), and choose Delete.
Close Task Scheduler. That should do it!
Note: The task location would be mentioned in the event log in every case. For instance, if the description says “NT TASK\Apple\AppleTask definition”, then you’ll need to expand the Task Scheduler Library, select the branch named Apple and delete the task named AppleTask.
One small request: If you liked this post, please share this?
One "tiny" share from you would seriously help a lot with the growth of this blog. Some great suggestions:- Pin it!
- Share it to your favorite blog + Facebook, Reddit
- Tweet it!
So does it auto recreate the task? In your example you’re telling people to delete the restore point creation task, what if they need to actually use system restore? I think a better method would be to find the cause of the error and correct it rather than delete the task.
Tim: The example given in the article refers to a 3rd party tool that creates restore points at startup. Deleting those invalid or obsolete tasks wouldn’t harm the system.
I’m sorry, I didn’t say any way to fix the task. Alot of times when this error is shown in your event log it’s because the actual scheduled task is set to “disabled” My recommendation would be to change the task from “disabled” to “enabled”.
I have to concur with Tim. This isn’t a resolution. To give an analogy, if your child caught a cold, would you kill them to resolve the issue?
@Steven: You both *miss* the point here. The task in question is NOT a built-in task, but added by a 3rd party program which no longer exists. Your analogy doesn’t apply here.