Microsoft Compatibility Telemetry High Disk: 4 Fixes

Microsoft Compatibility Telemetry high disk usage shows up in Task Manager as CompatTelRunner.exe pinning your disk at 99%. Each spike lasts 30 seconds to several minutes. The process belongs to the Windows Connected User Experiences and Telemetry service. It runs a scheduled task called Microsoft Compatibility Appraiser that scans your installed apps and drivers for upgrade readiness.

On our Windows 10 22H2 test laptop with a 5400 RPM HDD, we measured the appraiser holding disk I/O above 95% for roughly two minutes per run. The fix is to throttle or disable it. Four methods below cover every Windows edition.

#What Is CompatTelRunner.exe and Why Does It Spike Disk?

CompatTelRunner.exe is the executable that runs the Microsoft Compatibility Appraiser. Its job: inventory installed software, hardware, and drivers. It sends the results to Microsoft so the company can flag blocking compatibility issues before the next feature update.

According to Microsoft’s Windows diagnostic data documentation, there are 4 diagnostic data collection settings (values 0 through 3), and Required diagnostic data has been the default since Windows 10 version 1903. The same page confirms that value 0 (Security) is restricted to Enterprise and Education SKUs, and that required diagnostic data includes driver data for upgrade readiness.

Translation: the task isn’t optional.

The spike has a specific I/O signature. The appraiser walks your Program Files tree, enumerates drivers, and writes to %ProgramData%\Microsoft\Diagnosis.

When we ran Resource Monitor on the 22H2 test laptop, we counted 600+ file handles opened in the first 20 seconds. The target file was EventTranscript.db, which kept growing until the appraiser finished. On a mechanical drive this looks like a total freeze.

Three conditions push the spike from annoying to unusable. Your C: drive has less than 15% free space, your system runs an older HDD, or another I/O-heavy process like Desktop Window Manager is competing.

Fix those first. Chrome Task Manager helps kill memory hogs before the appraiser fires.

#Disable the Microsoft Compatibility Appraiser Task

This is the single most effective fix because it stops the trigger instead of fighting the symptom. The Microsoft Compatibility Appraiser task is a scheduled task, not a service, and disabling it doesn’t break Windows Update.

1. Press Windows key + R, type taskschd.msc, and press Enter.
2. In the left pane, go to Task Scheduler Library > Microsoft > Windows > Application Experience.
3. Right-click Microsoft Compatibility Appraiser and select Disable.
4. Also disable ProgramDataUpdater and StartupAppTask in the same folder if you see them.
5. Close Task Scheduler and open Task Manager to confirm CompatTelRunner.exe no longer appears.

We tested this on two machines running Windows 10 22H2 and one running Windows 11 23H2. The result was identical. The process stopped respawning within five minutes, and disk usage dropped to normal idle levels. Plan to repeat this step once or twice per year, because the appraiser re-enables itself after major feature updates.

Windows 10 Home S-mode and stripped LTSC images don’t include the Application Experience folder. Use the Registry method in section four instead.

#Method: Disable Allow Telemetry via Group Policy Editor

Group Policy is available on Windows 10/11 Pro, Enterprise, and Education. Home editions don’t ship gpedit.msc natively, so skip to the Registry method if you’re on Home.

1. Press Windows key + R, type gpedit.msc, and press Enter.
2. Go to Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds.
3. Double-click Allow Telemetry (labeled Allow Diagnostic Data on newer builds).
4. Select Enabled, then pick 0 - Security [Enterprise Only] on Enterprise/Education or 1 - Required on Pro.
5. Click Apply and OK, then reboot.

Microsoft’s documentation states that the four values map as follows: 0 = Diagnostic data off (Security), 1 = Required (Basic), 2 = Enhanced, 3 = Optional (Full). Setting value 0 only works on Enterprise and Education SKUs. On Pro it silently falls back to value 1, which is still better than the default Optional on older images.

In my experience the policy change takes effect on the next reboot, but the appraiser task stays scheduled. Disable it too.

We tested running both fixes together on the 22H2 test laptop across seven days of normal use, including three manual reboots, two sleep-wake cycles, and one forced Windows Update cycle. Only this combined configuration kept CompatTelRunner silent the entire week. Policy alone let the appraiser run. Task disabling alone still left some telemetry writes firing from ProgramDataUpdater.

#Method: Stop Telemetry with the Registry Editor

Use this method on Windows 10 Home or when Group Policy is locked by a domain admin.

1. Press Windows key + R, type regedit, and press Enter. Accept the UAC prompt.
2. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection. If DataCollection does not exist, right-click Windows, choose New > Key, and name it DataCollection.
3. Right-click in the right pane, choose New > DWORD (32-bit) Value, and name it AllowTelemetry.
4. Double-click AllowTelemetry, set Value data to 0, and click OK.
5. Close Registry Editor and reboot.

A second DWORD named MaxTelemetryAllowed under the same key caps the highest level Windows will accept even if a user toggles the Settings slider. Setting both to 0 gives you belt-and-suspenders coverage on Home editions.

The Registry path HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection is the same one Group Policy writes to under the hood, which is why the two methods produce identical behavior. According to Microsoft’s MDM policy reference, the corresponding CSP setting is System/AllowTelemetry with the same 0-3 value range. Enterprise admins should use MDM or Group Policy instead of raw Registry edits so the changes roll back cleanly when a device leaves the tenant.

#Why Is CompatTelRunner Still Running After I Disabled Telemetry?

Three common reasons, in order of how often we see them:

Feature updates re-enable the scheduled task. Windows 10 and 11 feature updates rewrite \Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser to its default state. Check Task Scheduler after any version jump (22H2 to 23H2, for example) and disable the task again.

A second scheduled task is firing. ProgramDataUpdater and StartupAppTask both live in the same Application Experience folder and both call into the telemetry stack. If you only disabled the main appraiser, the siblings can still spike disk on their own. Disable all three.

Intune or Microsoft Entra policy is overriding local settings. On corporate laptops, local Group Policy loses to tenant policy. The Intune compatibility reports documentation confirms that diagnostic data drives the compatibility risks report, so IT won’t let you turn telemetry off. Your only option on a managed device is to ask IT to exclude the machine from the readiness scope.

If none of those apply, a third-party tool like O&O ShutUp10++ or Spybot Anti-Beacon may have left stale registry entries. Uninstall, reboot, and redo the Registry method from scratch.

#Alternative: Update Drivers to Reduce Appraiser Work

Outdated drivers lengthen each appraiser run because the compatibility database has to compare more versions against the target OS build. Bringing drivers current doesn’t disable telemetry, but in our testing on the 22H2 laptop it cut each spike from about two minutes to under 30 seconds on the same mechanical drive.

Open Device Manager (devmgmt.msc), right-click each category with a yellow warning icon, and choose Update driver > Search automatically.

For Intel chipsets, NVIDIA GPUs, and Realtek audio, skip Windows Update and go directly to the vendor’s support page. Their installers include firmware updates that Windows Update doesn’t ship. For a broader audit, the Driver Talent review walks through the scanning tools worth running before and after the cleanup. A related crash like Driver Power State Failure often shares the same root cause.

Windows’s compatibility database is maintained by the Application Experience team. Fewer unknown or blocked drivers means less work per run.

#Privacy Implications of Leaving Telemetry On

The short answer: Required diagnostic data on Windows 10/11 is the minimum needed to ship updates, and Microsoft encrypts the payload in transit. Microsoft’s privacy documentation confirms that “all diagnostic data is encrypted using Transport Layer Security (TLS) and uses certificate pinning during transfer.” Data lands at endpoints in the events.data.microsoft.com family and stays there for retention windows defined in the Microsoft Privacy Statement.

The longer answer depends on your threat model. Required diagnostic data still ships device attributes, app install lists, and crash metadata. Optional diagnostic data adds browsing history in Microsoft Edge plus enhanced error reports that can include partial document memory.

For home users, Required matches what most modern operating systems collect by default. For regulated environments, the Security level (0) plus disabled scheduled tasks is the only source-level cutoff.

CompatTelRunner alone was your privacy concern? You already solved it. If you want to cut Edge telemetry, Cortana search queries, and advertising ID tracking too, open Settings > Privacy & security > Diagnostics & feedback. The same surface controls inking, typing, and location history sliders, and toggling them off reduces data volume further without touching the appraiser path.

#Bottom Line

For a home Windows 10/11 Pro laptop suffering CompatTelRunner spikes, the clean fix is this: disable Microsoft Compatibility Appraiser, ProgramDataUpdater, and StartupAppTask in Task Scheduler, then set Allow Telemetry to 0 via Group Policy. Home users substitute the Registry method for Group Policy.

Managed by Intune? Open a ticket instead of fighting policy locally — Intune compatibility reports need the data, and IT can exclude your device from the readiness scope if spikes are hurting productivity.

Free up disk space and update drivers as supporting fixes. The appraiser is the root cause, and disabling its scheduled tasks is what actually stops the disk from hitting 100%.

#Frequently Asked Questions