Unable to disable Compatibility Telemetry in Windows 10

Methods Failed to disable Microsoft Compatibility Telemetry:

Method 1: Use O&O ShutUp10 _{Used latest version released on 7-Mar-'17}

Method 2 (CMD commands) _{mentioned here}:

sc delete DiagTrack
sc delete dmwappushservice
echo "" > C:\ProgramData\Microsoft\Diagnosis\ETLLogs\AutoLogger\AutoLogger-Diagtrack-Listener.etl
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\DataCollection" /v AllowTelemetry /t REG_DWORD /d 0 /f

Method 3 (Disable appraiser) _{mentioned here}: Disable the Microsoft Compatibility Appraiser task in Task Scheduler under \Microsoft\Windows\Application Experience.

Method 4 (Disable all tasks under \Microsoft\Windows\Application Experience) _{mentioned here} : Disabled all tasks (Microsoft Compatibility Appraiser, ProgramDataUpdater, StartupAppTask) under \Microsoft\Windows\Application Experience.

Microsoft Compatibility Telemetry is known for its high disk and CPU usage and suspicious anti-privacy activities.

I've used the previous methods to disable it but all of them failed to disable it, as it returns to run again.

Moreover, weird activity was detected via Process Monitor where Compatibility Telemetry is trying to write files to my antivirus location. Screenshot:

Solution 1:

I had similar problem in my laptop, the telemetry consumes all disk IOs after I install anything new or updates. Making it unusable for a few hours.

Here how I solved:

1. Make sure the telemetry is not running (you can stop it from the task manager)

2. Open your %windir%\system32\

3. Find the trouble maker CompatTelRunner.exe

4. Gain ownership on the file (Properties -> security tab -> advanced -> owner change, set yourself as owner)

5. Add permission to modify for the users (select "users" -> edit -> basic permissions-> check modify -> ok)

6. Click ok again

7. Rename the CompatTelRunner.exe to CompatTelRunner.exe.bak for example

The telemetry will not run any more. until you restore the windows or a major windows update.

PS:This solution might generate some error log entries.Because windows will still trying to run it.