Recommended Free Tools
Diagnostic Policy Service high CPU usage is one of those Windows performance issues that can feel random—until you trace what’s actually waking it up. That service is tied to diagnostics, telemetry, and policy-driven reporting, so it can spike when a configuration, dependency, or data store goes sideways.
This guide walks you through the safest, most effective fixes to free up CPU without blindly disabling critical Windows components. Follow the steps in order; most cases stabilize after a targeted repair plus a quick policy sanity check.
As an Amazon Associate I earn from qualifying purchases.
Applies to Windows 10 and Windows 11 (and often Server builds). If you’re on a domain-managed PC, read the “Managed Device” section before changing policies.
What Diagnostic Policy Service Is and Why It Can Spike CPU
“Diagnostic Policy Service” is part of Windows’ diagnostics pipeline (commonly surfaced under the Services app as a service with a name related to diagnostics/policy). It runs under the Diagnostic or Network-related host processes depending on your build and can consume CPU while it evaluates policy rules, collects diagnostic info, or tries to write results.
#1 Best Overall
- [Brand Overview] Thermalright is a Taiwan brand with more than 20 years of development. It has a certain popularity in the domestic and foreign markets and has a pivotal influence in the player market. We have been focusing on the research and development of computer accessories. R & D product lines include: CPU air-cooled radiator, case fan, thermal silicone pad, thermal silicone grease, CPU fan controller, anti falling off mounting bracket, support mounting bracket and other commodities
- [Product specification] Thermalright PA120 SE; CPU Cooler dimensions: 125(L)x135(W)x155(H)mm (4.92x5.31x6.1 inch); heat sink material: aluminum, CPU cooler is equipped with metal fasteners of Intel & AMD platform to achieve better installation, double tower cooling is stronger（(Note:Please check your case and motherboard for compatibility with this size cooler.）
- 【2 PWM Fans】TL-C12C; Standard size PWM fan:120x120x25mm (4.72x4.72x0.98 inches); fan speed (RPM):1550rpm±10%; power port: 4pin; Voltage:12V; Air flow:66.17CFM(MAX); Noise Level≤25.6dB(A), leave room for memory-chip(RAM), so that installation of ice cooler cpu is unrestricted
- 【AGHP technique】6×6mm heat pipes apply AGHP technique, Solve the Inverse gravity effect caused by vertical / horizontal orientation, 6 pure copper sintered heat pipes & PWM fan & Pure copper base&Full electroplating reflow welding process, When CPU cooler works, match with pwm fans, aim to extreme CPU cooling performance
- 【Compatibility】The CPU cooler Socket supports: Intel:115X/1200/1700/17XX AMD:AM4;AM5; For different CPU socket platforms, corresponding mounting plate or fastener parts are provided（Note: Toinstall the AMD platform, you need to use the original motherboard's built-in backplanefor installation, which is not included with this product)
High CPU typically happens when Windows is repeatedly re-triggered—most often due to:
- Corrupted system files or broken diagnostic components.
- Stale or inconsistent diagnostic data stores that keep failing to update.
- Policy conflicts from Group Policy, registry edits, security baselines, or third-party “privacy” tools.
- Malware or a broken dependency causing repeated failures and retries.
- Managed environment overrides (domain policies continuously enforce settings).
Before You Start: Quick Checks That Prevent Wasted Time
Do these in 2–3 minutes. They also help you avoid disabling the wrong thing.
Confirm the CPU consumer and the exact process
1) Press Ctrl+Shift+Esc to open Task Manager.
2) Go to the Processes tab.
3) Enable Show process details if needed, then sort by CPU.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsYou’re looking for the process tied to Diagnostic Policy Service (often shown under a “service host” container). Note the PID and name of the container so you don’t chase a different service.
Check if it’s a temporary spike
Let it run for 5–10 minutes. Some builds spike briefly after updates, new network profiles, or driver changes. If it stays high (for example, consistently 20–60% for 10+ minutes), treat it as a real fault.
Identify your Windows version/build
Go to Settings > System > About and note the version (Windows 10 22H2, Windows 11 23H2, etc.). Certain known issues correlate to builds—this matters for Event Viewer interpretation.
Step-by-Step Fixes (Try in Order)
Start with verification, then work from least risky to most disruptive. You’ll often fix the underlying trigger without breaking diagnostics.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →1) Confirm It’s Truly Diagnostic Policy Service
If Task Manager shows a host process, confirm which service is inside it.
Rank #2
- Simple, High-Performance All-in-One CPU Cooling: Renowned CORSAIR engineering delivers strong, low-noise cooling that helps your CPU reach its full potential
- Efficient, Low-Noise Pump: Keeps your coolant circulating at a high flow rate while generating a whisper-quiet 20 dBA
- Convex Cold Plate with Pre-Applied Thermal Paste: The slightly convex shape ensures maximum contact with your CPU’s integrated heat spreader, with thermal paste applied in an optimised pattern to speed up installation
- RS120 ARGB Fans: RS ARGB fans create strong airflow and high static pressure, with easy ARGB control via a compatible motherboard. CORSAIR AirGuide technology and Magnetic Dome bearings ensure great cooling performance and low noise
- Easy Daisy-Chained Connections: Reduce the wiring in your system by daisy-chaining your RS ARGB fans and connecting them to just one 4-pin PWM fan header and one +5V ARGB header
- Open Task Manager > Details.
- Right-click the CPU-heavy process (service host container) and choose Go to service(s) (if available).
- If you don’t see that option, open Services app (Win+R →
services.msc), then locate the diagnostic policy service entry and correlate its status.
Once you’ve confirmed the service, move to Event Viewer—the fastest way to learn what it’s failing on.
2) Check Event Viewer for the Actual Trigger
When the CPU spike is persistent, Windows usually logs errors that explain why diagnostic policy is retrying.
- Press Win+R, type
eventvwr.msc, press Enter. - In the left pane, go to Windows Logs > System.
- In the right pane, choose Filter Current Log….
- Filter by Error and Warning first, then search for entries with keywords like diagnostic, policy, telemetry, or the service name.
- Also check Applications and Services Logs > Microsoft > Windows (look for diagnostics-related subfolders).
If you see repeated timestamps that match the CPU spikes, focus on the underlying failing component (network profile service, policy engine, WMI provider failures, etc.). Repair steps below typically resolve corrupted dependencies.
3) Restart the Service (and Related Diagnostic Components)
Sometimes the service gets stuck in a retry loop. A restart clears the immediate backlog.
- Open Services (Win+R →
services.msc). - Find the Diagnostic Policy Service entry.
- Right-click → Restart. If Restart isn’t available, do Stop, wait 10 seconds, then Start.
- Restart dependent diagnostics-related services if they exist on your system (common candidates include diagnostic tracking or related telemetry-related services). Avoid random “Stop” unless you confirm dependencies in the service properties.
Test for 10 minutes. If CPU drops and stays stable, the issue may be transient or triggered by a temporary policy/data mismatch.
4) Repair System Files (SFC and DISM)
Corruption is a top cause of diagnostic components repeatedly failing and reattempting. Use the standard Windows repair toolchain.
Run Command Prompt as Administrator:
- Press Start, type cmd, right-click Command Prompt → Run as administrator.
- Run:
sfc /scannow
After SFC finishes, run DISM:
DISM /Online /Cleanup-Image /RestoreHealth
Reboot after repairs. Then check Task Manager again for CPU stability.
5) Clear Stale Diagnostic Data (Targeted)
Diagnostic components can loop when old or partially written records break their update logic. Clearing the wrong folders can cause bigger problems, so keep it targeted and use built-in tooling when possible.
Rank #3
- CONTACT FRAME FOR INTEL LGA1851 | LGA1700: Optimized contact pressure distribution for longer CPU life and better heat dissipation
- ARCTIC's P12 PRO FAN: More power at any speed - more powerful and quieter than the P12, especially at low speeds. Higher maximum speed for optimal cooling performance under high load
- NATIVE OFFSET MOUNTING FOR INTEL AND AMD: Shifting the cold plate center towards the CPU hotspot ensures more efficient heat transfer
- INTEGRATED VRM FAN: PWM-controlled fan that lowers the temperature of the voltage converters and thus ensures reliable performance
- INTEGRATED CABLE MANAGEMENT: The PWM cables of the radiator fans are integrated in the sheathing of the hoses so that only a single visible cable is connected to the motherboard
Start with Windows’ Disk Cleanup for diagnostic-related files:
- Open Settings > System > Storage.
- Choose Temporary files.
- Select categories related to diagnostics (varies by build). If you see Diagnostic data or Diagnostics entries, select them.
- Click Remove files.
If Disk Cleanup doesn’t show relevant entries, don’t jump to deleting large folders manually. Instead, proceed to policy sanity checks and dependency repair, which are typically safer.
6) Fix Policy/Telemetry Conflicts (Group Policy and Registry sanity)
Third-party “privacy” tools and aggressive hardening can break the assumptions diagnostic services use. Group Policy overrides can also re-apply changes and keep the service in a failing state.
Step A: Check Group Policy for diagnostic/telemetry settings
- Press Win+R, type
gpedit.msc, press Enter (Windows Pro/Enterprise only). - Review policy sections related to data collection, diagnostics, and telemetry.
- If you recently changed privacy settings, revert those policies to Not Configured or match your organization’s approved baseline.
Step B: Undo third-party modifications
If you installed tools that “disable telemetry,” “fix tracking,” or edited services/registry to stop diagnostics, reverse those changes. Diagnostic Policy Service can’t do its job if the environment it expects is partially disabled.
Step C: Validate service permissions and dependency health
In Services (services.msc) → right-click the service → Properties, check:
Free tools Windows power users keep installed
One-click scans. No signup required.
- Startup type (don’t force Disable as the first move).
- Log On user (verify it’s the expected system account).
- Dependencies tab (don’t disable required services).
7) Rule Out Malware or a Corrupted Dependency
If an attacker disrupts services or injects failures, diagnostic components often become the scapegoat because they respond to errors.
Rank #4
- [Brand Overview] Thermalright is a Taiwan brand with more than 20 years of development. It has a certain popularity in the domestic and foreign markets and has a pivotal influence in the player market. We have been focusing on the research and development of computer accessories. R & D product lines include: CPU air-cooled radiator, case fan, thermal silicone pad, thermal silicone grease, CPU fan controller, anti falling off mounting bracket, support mounting bracket and other commodities
- [Product specification] Thermalright PA120 SE ARGB; CPU Cooler dimensions: 125(L)x135(W)x155(H)mm (4.92x5.31x6.1 inch); heat sink material: aluminum, CPU cooler is equipped with metal fasteners of Intel & AMD platform to achieve better installation, double tower cooling is stronger
- 【2 PWM Fans】Model:TL-C12C-S; Colorful and gorgeous ARGB light effects; Standard size PWM fan:120x120x25mm (4.72x4.72x0.98 inches); Product weight:0.97kg(2.1lb); fan speed (RPM):1500rpm±10%; power port: 4pin; Voltage:12V; Air flow:66.17CFM(MAX); Noise Level≤25.6dB(A), leave room for memory-chip(RAM), so that installation of ice cooler cpu is unrestricted
- 【AGHP technique】6×6mm heat pipes apply AGHP technique, Solve the Inverse gravity effect caused by vertical / horizontal orientation, cpu cooler TDP is 120 to 245W. 6 pure copper sintered heat pipes & PWM fan & Pure copper base&Full electroplating reflow welding process, When CPU cooler works, match with ultra-silent airflow fans, aim to extreme CPU cooling performance
- 【Compatibility】The CPU cooler Socket supports: Intel:115X/1200/1700/17XX AMD:AM4;AM5; For different CPU socket platforms, corresponding mounting plate or fastener parts are provided
- Run Microsoft Defender: open Windows Security → Virus & threat protection → Quick scan.
- If you suspect persistence, run Microsoft Defender Offline scan.
- Check for unusual scheduled tasks: open Task Scheduler, sort by Last Run Result and look for repeated failures that align with CPU spikes.
Also verify that related event sources aren’t reporting access denied or repeated provider crashes.
8) If You’re on a Managed Device: Verify Your IT Policies
If your PC is joined to a domain or managed by Intune/SCCM, local fixes can get overwritten. In managed environments, the “right” fix is usually aligning with the approved diagnostic baseline.
- Check if Windows policies are being enforced (look for policy sync notifications, or check gpresult /h output if you have access).
- Tell IT that Diagnostic Policy Service is high CPU and include the Event Viewer error IDs you found.
- Avoid repeated manual changes that will be rolled back.
When Restarting or Repair Doesn’t Work: Advanced Options
If the service continues to hammer CPU after SFC/DISM and policy sanity checks, you’re dealing with an underlying trigger that needs isolation.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Reset the Service State by Recreating Diagnostic Policy Config
Some diagnostic services rely on configuration and state that can become inconsistent. Instead of random registry edits, focus on clearing the specific state using supported tooling where available. If Event Viewer points to a particular component failing to store data, target that component rather than blanket deletion.
If your logs show consistent corruption errors tied to a diagnostic state store, you can:
- Rebuild the related Windows service state using approved command sequences (when referenced by your error IDs).
- Prefer “repair” actions (SFC/DISM) over manual registry surgery.
Because the exact registry keys and state paths vary by Windows build and policies, use the Event Viewer error ID to guide a precise fix. Share the event ID text with support if needed.
Perform a Clean Boot to Identify the Culprit
A clean boot reduces third-party interference and helps you isolate whether a background app keeps triggering diagnostics.
- Press Win+R, type
msconfig, press Enter. - On the Services tab, check Hide all Microsoft services.
- Click Disable all.
- Go to the Startup tab and click Open Task Manager.
- Disable all startup items.
- Reboot and watch CPU for 10–20 minutes.
If CPU drops, re-enable items in batches until you find the trigger (security suites, “optimizer” tools, privacy blockers, network monitoring agents, and broken drivers are common causes).
Best Value
- Cool for R7 | i7: Four heat pipes and a copper base ensure optimal cooling performance for AMD R7 and Intel i7.
- Quiet Cooling Fan: SickleFlow 120 Edge with Dynamic PWM control (690–2,500 RPM), designed for low noise and peak cooling performance.
- Simplify Brackets: Redesigned brackets simplify installation on AM5 and LGA 1851|1700 platforms.
- Versatile Compatibility: 152mm tall design offers performance with wide chassis compatibility.
- Easy Installation: Easy to install with included thermal paste for hassle-free setup and optimal cooling performance.
In-Place Repair Upgrade (Last Resort)
If system corruption persists beyond SFC/DISM, an in-place upgrade can refresh Windows system components while keeping apps and settings.
- Download the latest Windows 10/11 ISO or use the official installer from Microsoft.
- Run setup while keeping files and apps.
- After completion, reboot and confirm the CPU issue is gone.
This is heavier than a repair scan, but it’s often the fastest path when event logs show broad component failures.
Common Mistakes and Gotchas
- Disabling the service permanently without understanding dependencies. This can break diagnostic reporting and cause other system components to retry.
- Ignoring Event Viewer. High CPU spikes almost always have a logged reason. Treat logs as your compass.
- Using privacy tools that partially disable telemetry. They may stop data collection while leaving policy tasks active, creating retry loops.
- Deleting folders blindly. Diagnostic caches have internal relationships; manual deletions can worsen instability.
- Not rebooting after repairs. SFC/DISM repairs often require a restart to fully load corrected components.
Compare Fix Approaches: What Usually Works Fast vs What Lasts
| Approach | Effort | Likelihood of Fixing | Best For |
|---|---|---|---|
| Confirm process and restart service | Low | Medium | Stuck retry loops, temporary spikes |
| Event Viewer log correlation | Low | High | Ongoing high CPU with identifiable errors |
| SFC + DISM repair | Medium | High | Component corruption and broken dependencies |
| Clear targeted diagnostic files | Low to Medium | Medium | Stale diagnostic data causing update failures |
| Undo policy/telemetry hardening conflicts | Medium | Medium to High | Recent privacy or baseline changes |
| Clean boot isolation | Medium | Medium | Third-party trigger keeps reactivating diagnostics |
| In-place repair upgrade | High | Very High | Persistent corruption beyond repair tools |
FAQs
Is it safe to disable Diagnostic Policy Service to stop the CPU usage?
It’s usually not the best first move. Disabling it can interfere with diagnostics and may cause other Windows components to retry or behave unexpectedly. Prefer restart, repair (SFC/DISM), and policy conflict checks first.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →How long should it take to stabilize after repairs?
After SFC/DISM and a reboot, test for 10–30 minutes. If the service immediately re-enters a retry loop, check Event Viewer for matching error IDs and focus on the underlying failure.
Does this happen after Windows updates?
Yes. After feature updates or cumulative updates, diagnostic policy tasks may rescan settings, rebuild caches, or re-evaluate telemetry/policy rules. If CPU stays high for hours, treat it as a fault and proceed with Event Viewer + repairs.
Could a driver or network issue be the root cause?
Absolutely. If the service is reacting to repeated network/profile or policy evaluation failures, fixing the driver, resetting network components, or addressing the event log trigger can stop the CPU spike.
Bottom Line
To fix Diagnostic Policy Service high CPU usage and free up CPU, confirm the exact service container, then use Event Viewer to find the repeated failure pattern. In most real cases, SFC + DISM repair plus reversing telemetry/policy conflicts resolves the retry loop.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11If the CPU spike persists, use a clean boot to identify a third-party trigger or escalate to an in-place repair upgrade when corruption is broad. With this workflow, you’ll get to a stable system without risky guessing.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
