I noticed that, while the "Status" of the task showed as "Disabled", there was still a trigger enabled run once and then repeat every day. It gave an error message that I didn't note exactly at the time, something like "could not connect to Task Scheduler", and the Properties dialog remained open. I have a similar issue. Mine was set by default to run at midnight, and then every day thereafter with random delay of up to 2 hours.
Today I had three instances running simultaneously after login from sleep. Go to Properties. On the Triggers tab reconfigure to run weekly on each Sunday at midnight with random delay of up to 2 hours , do not repeat task, stop task if it runs longer than 10 minutes manually type in.
On the Conditions tab tick "Start the task only if the computer is idle for 10 minutes", "Stop if the computer ceases to be idle", and "Restart if the idle state resumes". On the Settings tab untick "run task as soon as possible after a scheduled start is missed". I suspect this is one of the things that causes a high resource usage when I login after the computer was sleeping, because it immediately wants to 'catch up' on the task that was scheduled to run at midnight.
Set "Stop the task if it runs longer than" 30 minutes manually type in. I guess the task should stop when the shorter of the durations specified here and on the Conditions tab is exceeded. I already had "If the task is already running, Need to extend Support for Windows 8. I have my laptop with pre-installed Window 8? Can I Recover the same original window? Skip to main content. Find threads, tags, and users Dear Community, We have a system in our company whose user keeps complaining that its as slow.
Compatibility: Microsoft Windows Read Review. Try the FREE scan option to search for stability, security and hardware-related issues. To fix identified problems and receive hardware-related recommendations, you have to purchase the license key for the full software version. One of the easiest ways to solve Telemetry Runner problem is to disable it without deleting it.
Follow the given steps to stop CompatTelRunner. The following method requires having the Administrator privileges on the computer. The given method describes how to delete only the Compatibility Telemetry Runner file, not the entire KB update. Removing the whole update can mess up the schedule of Windows updates, so we do not recommend doing so.
Some users have expressed complaints online about compattelrunner. We hope that you managed to fix the high CPU issue and your computer works smoothly now. This post was first published on Jul 31st, , and updated since then.
He is the chief editor of the website who controls the quality of content published. The man also loves reading cybersecurity news, testing new software and sharing his insights on them. Norbert says that following his passion for information technology was one of the best decisions he has ever made. Any help? Hi Norbert, Thanks for the information. Never knew about the Task Scheduler access via run command. Saw a lot of speculations in other blogs… Here the Description from MS themselves is absolutely clear.
Thanks again! All running smoothly now… Thanks Norbert. Works amazing, I was having problems with this program running while I was playing assetto corsa on higher graphics levels.
Having the program running while playing assetto corsa actually pushed my computer up to percent cpu usage, I was really confused with it since assetto never uses any more then 30 to 40 percent at the absolute most. Your email address will not be published. Disable CompatTelRunner. Delete CompatTelRunner. Disable Telemetry via Registry Editor Method 6. Look for other issues causing slow Windows performance.
Method 1. Disable Windows Personal Data Sharing The easiest way to disable Microsoft Compatibility Telemetry and other data sharing services that transmit information from your device to Microsoft is to use a good security software. Run a quick scan or deep scan and then check your recommendations.
