sodcalculator

10 Tech How-To

Fix Microsoft Compatibility Telemetry High CPU

Guide 10-57940 · Updated · Step by step

Microsoft Compatibility Telemetry (also known as CompTel or the “Compatibility Telemetry” process) can consume a significant amount of CPU and disk resources, especially on Windows 10 and Windows 11 systems. This article explains what this process is, why it sometimes uses high CPU, and provides clear, safe steps to reduce or disable it without harming your system’s stability.

What Is Microsoft Compatibility Telemetry?

Microsoft Compatibility Telemetry is a built-in Windows service that collects diagnostic and usage data about your computer. Its official purpose is to help Microsoft improve Windows by identifying compatibility issues with hardware and software. The process runs in the background, often appearing as “Microsoft Compatibility Telemetry” or “CompatTelRunner.exe” in Task Manager.

It is part of the Windows Diagnostic Tracking Service (also called DiagTrack). While telemetry is common in modern operating systems, the compatibility telemetry process is known to occasionally spike CPU usage, particularly after system updates or during scheduled maintenance tasks. This can slow down your PC, especially if you have an older processor or limited RAM.

Why Does It Cause High CPU Usage?

The telemetry process is designed to run periodically, but certain conditions can cause it to work harder than necessary:

  • Post-update scans: After a Windows Update, the system may re-run compatibility checks, causing a temporary CPU spike.
  • Faulty drivers or software: If a program or driver is misbehaving, the telemetry may repeatedly try to collect data about it.
  • Corrupted system files: Damage to Windows components can make the telemetry process loop or retry, increasing resource usage.
  • Low disk space: If the system drive is nearly full, the telemetry may struggle to write logs, leading to repeated attempts.

It’s also worth noting that the process is designed to run at low priority, but in some cases, it may not yield CPU time properly, causing noticeable slowdowns.

How to Check If It’s Really the Problem

Before making changes, confirm that Microsoft Compatibility Telemetry is indeed the cause of high CPU usage:

  1. Press Ctrl + Shift + Esc to open Task Manager.
  2. Click the Processes tab and look for “Microsoft Compatibility Telemetry” or “CompatTelRunner.exe” under the “Windows processes” section.
  3. Check the CPU column. If it’s consistently above 30% for several minutes, it’s likely the culprit.
  4. Also check the Performance tab to see overall CPU usage. If the system is idle but CPU is still high, telemetry may be the cause.

If you see high CPU usage only for a few seconds after boot or after an update, it’s probably not a problem. The process is designed to run briefly and then stop.

How to Reduce or Disable It Safely

There are several methods to limit or disable Microsoft Compatibility Telemetry. Choose the one that fits your comfort level. Always create a system restore point before making system changes.

Method 1: Disable the Diagnostic Tracking Service

This is the most direct way to stop the telemetry process:

  1. Press Windows + R, type services.msc, and press Enter.
  2. Scroll down to Connected User Experiences and Telemetry (or “Diagnostic Tracking Service” on older builds).
  3. Right-click it and select Properties.
  4. Set Startup type to Disabled.
  5. Click Stop to end the process immediately.
  6. Click OK and restart your PC.

Note: On Windows 10 Home, the service may re-enable itself after updates. You can also disable it via the Registry (see below) to prevent this.

Method 2: Use the Registry Editor

If the service keeps re-enabling, you can disable telemetry via the registry:

  1. Press Windows + R, type regedit, and press Enter.
  2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection.
  3. If the DataCollection key doesn’t exist, right-click on Windows, select New > Key, and name it DataCollection.
  4. Inside DataCollection, right-click and create a new DWORD (32-bit) Value named AllowTelemetry.
  5. Set its value to 0.
  6. Close the Registry Editor and restart your PC.

This sets the telemetry level to “Security” (the minimum) and effectively disables most data collection.

Method 3: Use Task Scheduler to Disable Related Tasks

Microsoft Compatibility Telemetry also runs via scheduled tasks. Disabling these can help:

  1. Press Windows + R, type taskschd.msc, and press Enter.
  2. Navigate to Task Scheduler Library > Microsoft > Windows > Application Experience.
  3. Look for tasks named Microsoft Compatibility Appraiser and ProgramDataUpdater.
  4. Right-click each and select Disable.

This prevents the telemetry from running on a schedule, but it may still run when triggered by other events.

What If the Problem Persists?

If you’ve disabled telemetry and still see high CPU usage, the issue may be something else. Check for other processes like “Runtime Broker” or “Windows Update” which can also cause spikes. Run a full antivirus scan to rule out malware that might be mimicking the process name. Also, ensure your Windows is updated to the latest version, as Microsoft has fixed several telemetry-related bugs over time.

Is It Safe to Disable?

Disabling Microsoft Compatibility Telemetry is generally safe. You may lose some diagnostic data that Microsoft uses to improve Windows, but you won’t break your system. However, be aware that some Windows updates may re-enable the service. Also, if you’re using a work or school computer, group policies may force telemetry on, and disabling it locally may not work.

One common misconception is that disabling telemetry will speed up your PC dramatically. In most cases, the CPU usage is temporary and not a constant drain. If you have an older PC, disabling it can help, but you may see more benefit from disabling other startup programs.

Frequently Asked Questions

Will disabling Microsoft Compatibility Telemetry affect my Windows updates?

No, disabling telemetry does not block Windows Updates. You will still receive security and feature updates. However, some updates may be delayed because Microsoft uses telemetry to prioritize rollout, but this is not a significant issue for most users.

Can I delete the CompatTelRunner.exe file?

No, you should not delete the file. It is a system component, and deleting it may cause errors. Instead, disable the service or scheduled tasks as described above.

Why does Microsoft Compatibility Telemetry keep coming back?

Windows Updates can reset the service startup type to automatic. Also, some system maintenance tasks may re-enable it. Using the registry method to set AllowTelemetry to 0 is more persistent than just disabling the service.

Is this the same as the “DiagTrack” service?

Yes, “Connected User Experiences and Telemetry” is the service name, and “DiagTrack” is its short name. Microsoft Compatibility Telemetry is the process that runs under this service.

Will disabling telemetry void my warranty?

No, disabling telemetry is a user setting and does not affect your hardware warranty. It only changes what data is sent to Microsoft.

What if I want to keep telemetry but reduce its CPU usage?

You can set the telemetry level to “Basic” instead of “Full” via Settings > Privacy & Security > Diagnostics & feedback. This reduces the amount of data collected and may lower CPU usage, though it won’t eliminate it entirely.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →