Have you noticed a process in Task Manager called Microsoft Compatibility Telemetry that is consuming most of the system resources? This process shows resource consumption by Microsoft’s telemetry service, which collects technical data about your device’s performance. Microsoft uses this data for future updates to fix technical issues.
But what causes it to consume so many resources that it makes your system sluggish? In this article, we explain why this process becomes resource hungry and what you can do to reduce its high CPU usage.
Why is the Microsoft compatibility telemetry process consuming a lot of CPU resources?
Many factors can cause the Microsoft Compatibility Telemetry process to consume too much CPU resources, including a serious problem with your operating system, an error with the Telemetry service, a delay in updating your operating system, or a corrupted system file affecting the service . But how to reduce resource consumption?
To fix the high CPU usage caused by the Microsoft Compatibility Telemetry process, you can update the service, run necessary file scans and change the process schedule in the Task Scheduler app. Likewise, you can replace the corrupted process file, change diagnostic and feedback settings, and disable the telemetry service as a last resort if all else fails.
Below we have explained how you can apply these fixes to limit the CPU usage of this process.
But first, some preliminary checks…
First, perform the following pre-checks:
- Close the applications that are currently running, especially those that are freezing, crashing, or behaving strangely.
- To rule out temporary problems, restart your device.
- Install all available Windows updates to rule out that an outdated system is causing the problem. Our guide to managing Windows updates has instructions on how to do this.
- Run a malware scan to ensure that Windows Telemetry is not being overloaded by a malware infection. We have a guide on how to remove malware with Microsoft Defender Offline Scan if you need help.
- Run an SFC and DISM scan. The SFC scan scans your system files and replaces corrupted files with a cached copy. However, if that doesn’t work, you can also try DISM scan. Be sure to check out How to Repair Corrupted Files Using Windows’ Built-in Tools for more information on how to perform these scans.
If the above checks don’t work, start applying the remaining fixes.
1. Update the Connected User Experiences and Telemetry Service
Update the Connected User Experiences and Telemetry service in the Windows Services app to rule out temporary issues with the Windows telemetry process. This can help solve the primary problem with the service and reduce the load it causes. Follow these steps to restart this service:
- open that Services App by typing “Services” in Windows search.
- Find them Connected user experiences and telemetry Service.
- Right-click the service and click Start anew.
2. Change the diagnostic and feedback settings
By preventing Windows from sending optional diagnostic data to Microsoft, you can reduce the load on the Microsoft compatibility telemetry process. You can also opt out of other personalized recommendations from Microsoft to minimize resource consumption. Follow these steps to change these settings:
- Right click on the window beginning button and go to settings.
- Go to privacy and security Tab.
- Under Windows permissionsopen this diagnosis and feedback the settings.
- To limit Microsoft to collecting only necessary diagnostic data, turn off the switch next to Send optional diagnostic data.
- In the same way, expand the Tailored experiences menu and disable the switch.
You can also delete the previous diagnostic data that Microsoft has already collected about your device, which can significantly reduce the number of resources used by Microsoft Compatibility Telemetry. Expand that Delete diagnostic data menu and press Extinguish.
Also, by deleting the diagnostic data, you miss out on tailored updates and security fixes that Microsoft generally provides to make your operating system more secure and efficient. So you should only resort to it if all else fails.
3. Manage the runtime of the telemetry process in the task scheduler app
By default, the Task Scheduler app schedules the telemetry process to run at a specific time every day for an indefinite duration. By customizing the task’s trigger settings, you can limit the resource consumption by this process during the active hours of the day when you are at your computer.
Here’s what you need to do:
- Open Task Scheduler app by typing “Task Scheduler” in Windows search.
- Navigate to Task Scheduler Library > Microsoft > Windows > application experience in the left sidebar.
- Double-click the Microsoft Compatibility Checker Task.
- Navigate to Triggers tab and double-click the enabled trigger.
- Reschedule the task to run when your device is idle during the day.
- Check the box for Stop the task if it runs longer than and choose your preferred time until you can allow the process to drain your resources.
- Then click OK.
- After that go to the settings tab and uncheck the box for Run the task as soon as possible after a scheduled start is missed.
The above changes should allow you to limit the telemetry process from running and not tax your system resources when you work. If this does not produce the desired result, replace the ComparTelRunner.exe file.
4. Manually replace the CompatTelRunner.exe file
The CompatTelRunner.exe file runs the telemetry process. Therefore, when it gets corrupted, you may experience high CPU usage. Running the SFC scan, which automatically repairs corrupted system files, usually eliminates this possibility. You can replace the file manually if it continues to burden your resources.
The easiest way to do this is to copy a file from another system where telemetry is working fine. Here’s what you need to do:
- Search for “Command prompt” In Windows Search, right-click the app and click Execute as administrator.
- Enter the following command in the command prompt app:
takeown /f C:\Windows\System32\CompatTelRunner.exe
- Press Enter.
The steps above give you ownership of the file. Then replace the CompatTelRunner.exe file on your device with a healthy copy from another computer. If this fix doesn’t work either, consider disabling telemetry as a last resort.
5. Disable telemetry in Windows
If the Microsoft compatibility telemetry process is still taxing your resources, consider disabling telemetry yourself. Since disabling telemetry can severely degrade your system’s performance and negatively impact user experience, this should only be considered as a last resort.
Windows offers several ways to disable telemetry; Use Registry Editor and Group Policy Editor, disable the task in Task Scheduler or disable the service. If you want to go down this route, check out our guide on methods to disable Windows Telemetry.
Free your system resources from telemetry
The telemetry process can seriously slow down our system if it consumes too many resources. Hopefully the process will consume fewer resources after applying the fixes detailed in the article. You may need to disable the service if none of the fixes work. Therefore, it is not one of those processes that you cannot end in Task Manager.