Microsoft Compatibility Telemetry Using High CPU

Question

Hi, whenever I startup, I notice that Microsoft Compatibility Telemetry uses about 50-80% of my CPU which stops after a minute or so. Is this normal or should I be concerned?

Answer 1

Hi Tqkend

I'm Juliet and I'll do my best to help you.

The Windows Compatibility Telemetry contains technical information about how the device and its associated software work. It sends data to Microsoft on a regular basis in order to improve the system and improve the user experience. To resolve your issue about its high CPU usage, you can disable this service in the Task Scheduler by following the steps below:

1. Click Start, type Task Scheduler, and then press Enter.
2. On the TaskScheduler window, go to this path: Task Scheduler Library\Microsoft\Windows\Application Experience.
3. On the Application Experience folder, look for Microsoft Compatibility Appraiser.
4. Right-click on it, select Disable, and then confirm to complete the process.

I hope it helps! Let me know the results.

Have a nice day ahead and Stay safe always :)

Source: https://answers.microsoft.com/en-us/windows/for...

Answer 2

Hey I found a fix, I just went to that file location of that "Telemetry"

In my case it was at : C:\Windows\SysWOW64

1. Renamed "CompatTelRunner.exe" -> "Something.exe"
2. Then Ended the task on taskmanager then it didn't start up.

Of course I am not sure if it will have any long term effects. Do it at your risk :)

Answer 3

my fix was just killing the task everytime my computer starts, it got annoying going to task manager just to kill the task everytime my pc turns on, so i automated it using a batch file, .bat (the command is: taskkill /f /im compattelrunner.exe), and i placed it to my desktop (so i can double click on it if it comes back) and copied it to my autostart programs folder so it wont turn on as my computer starts, i know im late here but this is my fix and even if the task isnt on, taskkill shouldnt do anything bad, and if it errors out and you cant read because the window dissapears, i recommend placing a pause or a timeout