Disabling Windows Compatability Telemetry

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

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

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.

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.

Unfortunately, this fix is unrelated to Compatibility Telemetry. That setting, though it has been renamed in Win 10, is one of the first services that I disable on a new install for customers. However, compattelrunner.exe still runs from time to time. We've noticed that it happens most often after a Windows update that requires a reboot. 

With our customers with SSDs , we get a few calls. However, our customers with HDDs hammer us with support calls whenever that thing kicks in. Some of the older computers become unusable for a significant amount of time, and you can only imagine the nasty responses we get from our customers.

Like many in this thread, we have also attempted to make this problem go away, only to find later, it still exists. We will find it eventually, hopefully.