Microsoft Compatibility Telemetry Using High CPU

Anonymous
2022-10-13T10:50:28+00:00

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?

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2022-10-13T11:25:48+00:00

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...

Was this answer helpful?

900+ people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2023-02-22T15:43:11+00:00

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 :)

Was this answer helpful?

200+ people found this answer helpful.
0 comments

52 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2023-11-25T00:47:54+00:00

    Got it, thank you. I guess I was too harsh at MS. I still think it should be easier to disable this, tho.

    Definitely not too harsh. You shouldn't have to be a Microsoft Certified Systems Engineer in order to know how to resolve a problem in Windows!

    Taking ownership is not intuitive nor is it common knowledge. Your frustration is well founded!

    Was this answer helpful?

    40+ people found this answer helpful.
    0 comments
  2. Anonymous
    2023-12-23T08:18:28+00:00

    Thanks

    It worked for me

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2024-01-06T10:30:47+00:00

    hey Porper solution, Added to what Juliet said

    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.
    5. right click on Microsoft Compatibility Appraiser then click Properties
    6. Go to Triggers (on top next to General)
    7. choose trigger (there should be just one)

    Now you can either delete or edit it to once in a month/year/ or just never repeat it.

    I didn't delete it just edited it and set it to never repeat.

    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...

    Was this answer helpful?

    20+ people found this answer helpful.
    0 comments