Microsoft Compatibility Telemetry (CompatTelRunner.exe) High CPU Windows Process – How to Fix It

Introduction

Windows 10 and 11 users often notice their PCs slowing down, with CompatTelRunner.exe consuming excessive CPU or disk resources. This process, known as Microsoft Compatibility Telemetry, is part of Windows Customer Experience Improvement Program (CEIP) and is responsible for sending telemetry data to Microsoft.

While it’s not malware, high CPU usage from this process can degrade system performance. In this guide, we’ll explain what CompatTelRunner.exe does, why it may cause slowdowns, and provide multiple solutions to safely reduce or disable it.

Quick Triage

If you need a fast fix without digging deep:

1. Restart your PC – temporary relief if CPU spikes are short-lived.
2. Update Windows – patches sometimes optimize telemetry performance.
3. Run Disk Cleanup – removes compatibility logs that may trigger scans.

If the issue persists, follow the full step-by-step guide below.

Prerequisites

• A Windows 10 or 11 system with administrative rights.
• Basic familiarity with Task Manager and Windows Services.
• Optionally, Group Policy Editor (for Pro/Enterprise users).

Step-by-Step Guide

1. Identify CompatTelRunner.exe in Task Manager

• Press Ctrl + Shift + Esc to open Task Manager.
• Locate CompatTelRunner.exe under the Processes tab.
• Confirm it’s the legitimate Windows process (file path: C:\Windows\System32\CompatTelRunner.exe).

Warning: If it’s running from a different location, it could be malware masquerading as telemetry. In that case, run a full antivirus scan immediately.

2. Disable CompatTelRunner.exe via Task Scheduler

• Press Win + R, type taskschd.msc, and press Enter.
• Navigate to:
  Task Scheduler Library > Microsoft > Windows > Application Experience
• Locate Microsoft Compatibility Appraiser.
• Right-click and select Disable.

This prevents CompatTelRunner.exe from launching automatically during system scans.

3. Use Group Policy Editor (Pro/Enterprise Only)

• Press Win + R, type gpedit.msc, and press Enter.
• Go to:
  Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds
• Double-click Allow Telemetry.
• Set it to Disabled (or Basic if you prefer minimal telemetry).

This reduces or fully disables telemetry data collection.

4. Edit the Registry (Home Users)

Warning: Back up your registry before editing.

• Press Win + R, type regedit, and press Enter.
• Navigate to:
  HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection
• If the DataCollection key doesn’t exist, create it.
• Create a new DWORD (32-bit) value named AllowTelemetry.
• Set its value to 0.

This effectively disables telemetry on Home editions where Group Policy is unavailable.

5. Remove CompatTelRunner.exe (Advanced Option)

Some users choose to remove the executable completely.

• Boot into Safe Mode.
• Navigate to: C:\Windows\System32\CompatTelRunner.exe.
• Take ownership of the file (right-click > Properties > Security > Advanced > Change Owner).
• Rename it to CompatTelRunner.old.

Note: This is not recommended unless other methods fail, as it may interfere with future Windows updates.

Validation and Testing

After applying changes:

• Reboot your PC.
• Open Task Manager and monitor CPU usage.
• CompatTelRunner.exe should no longer spike CPU or disk activity.

If you experience system instability, revert changes by re-enabling the scheduled task or restoring registry values.

Security Hardening

• Use a local account instead of a Microsoft account for reduced data sharing.
• Run privacy tools such as O&O ShutUp10++ to manage telemetry settings centrally.
• Keep Windows updated to ensure performance fixes and security patches.

Conclusion

CompatTelRunner.exe is a legitimate Windows process, but its aggressive CPU usage can frustrate users. By disabling it via Task Scheduler, Group Policy, or Registry, you can reclaim performance without harming system stability.

For most users, disabling the scheduled task is the safest and most effective fix. Advanced users may go further by editing registry values or renaming the executable, but these steps should be performed with caution.

FAQ