Spotting CompatTelRunner.exe at the top of Task Manager with 30–60% CPU is unsettling — the name sounds like malware, and it’s doing something intensive with your files. It’s actually Microsoft’s compatibility telemetry: Windows scanning your apps and drivers to decide if your ASUS laptop is ready for the next feature update. Legitimate, but not something that should be grinding away for hours on end.
The nuance most guides miss: CompatTelRunner.exe high CPU comes in two flavors. The normal flavor runs for 10–30 minutes after updates or on Microsoft’s schedule, then stops. The broken flavor runs constantly, restarts immediately after ending, or never completes its scan — usually because a previous scan crashed, the task is misconfigured, or it’s choking on a specific application it can’t inventory. This guide helps you identify which flavor you have and fixes the broken one.
If your ASUS laptop is slow overall, our Windows 11 high memory usage fix and disabling startup programs guides cover the companion issues.
Why this happens
- Scheduled compatibility scan running: The normal trigger — Microsoft’s scheduled telemetry inventory, especially before feature updates.
- A crashed scan retrying in a loop: A scan that fails partway restarts repeatedly, producing endless CPU usage.
- Large software inventory: Many installed apps (common on ASUS laptops with preinstalled utilities) make each scan longer and heavier.
- Corrupt telemetry database: Damaged diagnostic data stores cause the scanner to redo work constantly.
- Misconfigured scheduled task: Task Scheduler settings that re-trigger the scan too aggressively.
- Disk slowness amplifying the scan: The inventory is disk-heavy; slow or full drives stretch a 15-minute scan into an hour.
- Impostor malware: Rare, but worth ruling out — verify the file location is System32.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Verify it’s legitimate and check whether it’s actually stuck
Rule out malware and confirm the problem before changing anything.
- In Task Manager, right-click CompatTelRunner.exe (it may show as “Microsoft Compatibility Telemetry”) > Open file location — it must resolve to
C:\Windows\System32. Anywhere else means malware: run a full Windows Security scan immediately. - Right-click > Properties > Digital Signatures — confirm it’s signed by Microsoft Corporation.
- Note when the high CPU started and whether it stops on its own within 30–60 minutes. Self-limiting runs are normal — only persistent runs need fixing.
- Check Settings > Windows Update — if a feature update is pending or recently installed, frequent telemetry runs are expected and will settle down within a week or two.
- If it’s been running at high CPU for hours across multiple days with no update activity, it’s stuck — continue.
Fix 2: Let the current scan finish under good conditions
Sometimes the fastest fix is giving it one clean run.
- Plug in the laptop, close heavy applications, and leave it alone for 45–60 minutes — a scan competing with your workload takes far longer and uses more CPU.
- Make sure you have at least 10 GB free on C: — the telemetry database needs working room.
- Don’t end the task repeatedly — each kill can corrupt the in-progress inventory, forcing a full rescan from scratch (which is likely how the loop started).
- After one uninterrupted run, check Task Manager — completed scans usually don’t recur for days or weeks.
- If it still restarts immediately after visibly finishing, the scheduled task configuration is the problem — move to Fix 3.
Fix 3: Disable the scheduled telemetry tasks
The most effective fix for the endlessly recurring case.
- Open Task Scheduler (
taskschd.msc) > navigate to Task Scheduler Library > Microsoft > Windows > Application Experience. - You’ll see tasks including Microsoft Compatibility Appraiser — right-click it > Disable. This is the task that launches CompatTelRunner.exe on schedule.
- Also check Task Scheduler Library > Microsoft > Windows > Customer Experience Improvement Program — disable the Consolidator and UsbCeip tasks if present.
- This does not break Windows Update — feature updates will still download and install; Microsoft just won’t get your compatibility telemetry ahead of time.
- Restart and monitor for 24 hours — CompatTelRunner.exe should no longer launch on its own. (It may still run briefly during actual feature-update installs, which is fine.)
Fix 4: Limit diagnostic data collection
Reduce what Windows collects, which reduces the telemetry workload.
- Go to Settings > Privacy & security > Diagnostics & feedback.
- Set Diagnostic data to the minimum available option — less data collected means less telemetry processing overall.
- Turn off Tailored experiences and Improve inking and typing if you don’t use those features — each feeds the telemetry pipeline.
- Under Feedback, set frequency to Never if desired — one less background task.
- Note: on some Windows 11 editions the minimum diagnostic setting still allows basic data; that’s fine — the goal is reducing the optional telemetry that drives CompatTelRunner.exe’s heaviest scans.
Fix 5: Use Group Policy to disable telemetry (Pro/Enterprise)
For Windows 11 Pro users who want a system-level switch.
- Press Win + R, type
gpedit.msc, press Enter. - Navigate to Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds.
- Open Allow Telemetry (or “Allow Diagnostic Data” on newer builds), set it to Enabled with the lowest option (Security/Basic), and click OK.
- Then navigate to Computer Configuration > Administrative Templates > System > Internet Communication Management > Internet Communication settings and set Turn off Windows Customer Experience Improvement Program to Enabled.
- Run
gpupdate /forcein Terminal, then restart. Verify in Task Scheduler that the Application Experience tasks stay disabled.
Fix 6: Clean up the software inventory it’s choking on
A leaner app list means faster, less frequent scans.
- Go to Settings > Apps > Installed apps — uninstall ASUS-preinstalled utilities you don’t use (duplicate photo apps, trial software, old game launchers). Each installed app is something the scanner must inventory.
- Remove old, abandoned software generally — the scanner struggles most with ancient apps that have broken uninstall entries.
- Run Disk Cleanup as administrator and clear temporary files — a cleaner disk speeds the inventory pass.
- Check Microsoft’s official Windows support page if you suspect a specific app is crashing the scanner — searching the app name plus “compatibility telemetry” sometimes reveals known conflicts.
- After cleanup, manually trigger one scan to confirm it completes: re-enable the Appraiser task temporarily, run it, watch it finish, then disable it again.
Fix 7: Repair system files if the scanner itself is corrupt
When CompatTelRunner.exe crashes and restarts endlessly, the component may be damaged.
- Open Terminal (Admin) and run
DISM /Online /Cleanup-Image /RestoreHealth, thensfc /scannow. - Check the Application event log (Event Viewer > Windows Logs > Application) for errors mentioning CompatTelRunner or telemetry around the times of high CPU — the faulting module name points to the corrupt component.
- If SFC finds corruption it can’t fix, the telemetry subsystem may need a repair install — download the Windows 11 ISO from Microsoft’s software download page and run setup keeping files and apps.
- After repair, leave the scheduled task disabled (Fix 3) — you want the component healthy but not running on its own schedule.
- Monitor for a week: a repaired system with disabled scheduled telemetry should show zero spontaneous CompatTelRunner.exe activity.
Closing
CompatTelRunner.exe is Windows doing homework for the next feature update — useful to Microsoft, but not something that should cost you hours of CPU. Verify it’s legitimate, give one clean scan a chance to finish, then disable the scheduled tasks if it won’t stop on its own. Your Task Manager — and your fans — will be quieter for it.
