Disabling Windows Compatability Telemetry

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.

I will have to 100% agree with you, I just went through some steps to disable this service from running on my girlfriend's computer as it was causing the sounds to pop and crack because it causes the computer to become incapable of running a stream of data.

Microsoft you need to fix this or delete it!

"Now, none of them are running." 

Which makes them really annoying to try and stop permanently because they pop up and disappear like a whack the weasels game, you never know if you got rid of them or if they'll come again later.

That is true, it was a msvchost.exe that is shown in the image.

The CompatelRunner.exe was prior to that.  It completely locked up my computer for about ten minutes, and then I was able to see what was doing it.  After another 10 minutes, the CompatelRunner.exe relented and then the msvchost.exe took over.

Now, none of them are running.

If I'm not fundamentaly misunderstanding the resource monitor, what you are seeing is 42 pages of open file handles owned by a single proces, right? But that says msvchost.exe, not CompatTelRunner.exe. Was this disk io listed under Windows Compatibility Telemetry or some other name? Because the techniques in this thread are only for disabling Windows Compatibility Telemetry.