Disabling Windows Compatability Telemetry

Anonymous
2015-09-23T22:34:38+00:00

Does anybody know how to stop the Windows Compatability Telemetry (CompatTelRunner.exe) from starting? It causes extremely high disk usage which results in large performance issues.

Windows for home | Previous Windows versions | 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 No comments

166 answers

Sort by: Newest
  1. Anonymous
    2017-01-23T02:05:29+00:00

    I don't have the DD17FA14 subkey in my registry. Is there any other key I should look under?

    Registry keys that are on their default value are sometimes simply not there. If it's missing just create it. I think a .reg file was provided in the article, you can just use that if you're worried about making the wrong key though.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-01-22T21:14:13+00:00

    I don't have the DD17FA14 subkey in my registry. Is there any other key I should look under?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-01-17T21:02:26+00:00

    Then make a .cmd with the following code and start it on bootup:

    @echo off

    :start

    taskkill /f /im CompatTelRunner.exe >nul 2>nul

    timeout 2 >nul

    goto start

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2017-01-17T20:25:58+00:00

    If it keeps coming back (and it does for all of us), you could schedule a test to run every 30 seconds or something and execute taskkill /f /im CompatTelRunner.exe. This would force kill the process if it's running, and it shouldn't impact performance even if you ran it once per second. Note that this will probably require administrator privileges. 

    In an ironic twist of fate, the task scheduler itself is quite broken too. The conditionals are messed up (for Network presence, for one), and many of my self-defined tasks don't run past a reboot. Besides, the lowest interval it can run at is 5 minutes, which is about 4:59 mins longer than I want CompatTelRunner to run unchecked.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2017-01-17T19:40:49+00:00

    If it keeps coming back (and it does for all of us), you could schedule a test to run every 30 seconds or something and execute taskkill /f /im CompatTelRunner.exe. This would force kill the process if it's running, and it shouldn't impact performance even if you ran it once per second. Note that this will probably require administrator privileges.

    Was this answer helpful?

    0 comments No comments