Microsoft Compatibility Telemetry, or CompatRelRunner.exe, is a service in Windows that sends performance data to Microsoft. This data can then be used by Microsoft to improve the users’ experience. However, users have reported facing high CPU usage issues with this service.
Why does this happen? Compatibility Telemetry Runner scans the files on your PC and checks whether they are compatible with your PC or not. This process might take some and also require a lot of processing. Though this is a service from Microsoft, it tracks your data, so it can be a privacy concern for the users.
To prevent Microsoft Compatibility Telemetry high CPU usage, you will have to disable the service. This will prevent the service from scanning files in the background. If you don’t know how to do so, then worry not. This article will guide you through it.
Fix Microsoft Compatibility Telemetry High CPU Usage
As we already discussed, you can fix high CPU usage from Microsoft Compatibility Telemetry high CPU usage by disabling this service. To do so, follow the steps given below –
1. Through Task Scheduler
The very first way to disable this service is by Task Scheduler. To do so, follow the steps given below-
- Press Windows key on your keyboard, search for Task Scheduler, and open it.
- Here, head to the following address-
Task Scheduler Library > Microsoft > Windows > Application Experience
- Right-click Microsoft Compatibility Appraiser and then click on Disable.
2. By Becoming the Owner of the Service
You can simply delete the file by taking its ownership. The steps for this have been discussed below-
- Press the Windows key, and search for CompatTelRunner. Right-click on it and then click on Open File Location.
- Now right-click on the file, and then click on Properties.
- Under the Security tab, click on the Advance button.
- Now under the Owner tab, click on the Change button.
- Here, click on the Find Now button.
- From the list of owners, select the account you are currently using and then click on OK.
- Next, click on Apply and then on OK.
- Again head to the properties of CompatTelRunner.
- Click on the Security tab and then click on the Advanced button.
- Now select your account from the list and then click on Edit to edit it.
- Click on the drop-down menu next to Type and select Allow.
- Now, under Basic Permissions, select Full Control.
- Now click on Apply and then on OK.
- Click on Yes and this will confirm your choice and you will be the owner of the file.
- Now you can delete the CompatTelRunner file.
3. Through Registry Editor
Another way to disable this service and fix Microsoft Compatibility Telemetry high CPU usage is through Registry Editor. To do so, follow the steps given below –
- Press Windows key on your keyboard, search for Registry Editor and open it.
- Visit the following path-
- On the left sidebar, right-click on DataCollection folder, click on New, and then on DWORD (32-bit value).
- Set the new DWORD as Allow Telemetry.
- Double-click on Allow Telemetry to edit it, change Data Value to 0, and click on OK.
- Now, restart your PC and the issue should be fixed.
4. Through Group Policy Editor
You can also disable the Microsoft Compatibility Telemetry service through the Group Policy Editor. However, this method only works for Windows Pro and Windows Enterprise users; if you have Windows Home, then you won’t be able to continue with this method. To do so, follow the steps given below-
- Open the Start Menu, search for Group Policy Editor and click on it from the search result.
- Navigate to the following path-
Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds
- Here, double-click on the Allow Telemetry option to edit it.
- Now, select the Disabled option; click on Apply and OK.
If you are facing Microsoft Compatibility Telemetry High CPU Usage, you can follow the steps given above to fix it. However, if you have disabled the CompatTelRunner.exe service but you are still facing performance lags, then you can check background processes which might also be causing this issue.