High CPU usage on Windows 11 is one of those problems that needs a five-second look before anything else. Open Task Manager right now (Ctrl + Shift + Esc) and click the CPU column to sort by usage. The process at the top of the list is consuming the most CPU — and that tells you almost everything about where to start. For the bigger picture, our Complete Guide to Fixing Windows, Browser, and Software Errors pulls everything together.
Some findings are immediately actionable:
- A game or video editor at the top — That’s expected. It’s not a problem.
- SearchIndexer.exe at 30–80% — Windows is rebuilding the search index, usually after an update. Wait it out or rebuild the index manually (see Fix 5).
- MsMpEng.exe (Windows Defender) at 40%+ — Antivirus scan running. Typically resolves within an hour. If it’s constant, check for malware.
- System (not System Idle Process) at high % — Driver issue. Check Event Viewer for hardware errors.
- An unfamiliar process name at high % — Check online what it is. Could be malware, could be legitimate software.
- svchost.exe with many instances — Right-click the highest-CPU svchost → Go to services → see which service it’s hosting.
If the CPU hog is obvious from Task Manager, skip to the section relevant to that process. If everything looks normal but the machine still feels sluggish with CPU at 70–90%, the issue is background aggregate load — multiple small processes adding up — and the broader fixes below apply.
Fix 1: Disable Startup Programs
Every application that launches at startup consumes CPU during the boot sequence and often keeps running in the background indefinitely. On a machine that’s been in use for a year or two, the startup program list frequently accumulates: Teams, OneDrive, Spotify, Discord, manufacturer utilities, browser update helpers, cloud backup clients. Each takes a small slice of CPU. Together they can add up to 20–30% constant background load before you’ve opened anything intentionally.
Task Manager → Startup apps tab → sort by Startup impact. Anything showing “High” impact is worth evaluating. Right-click → Disable for anything you don’t need running at startup — you can still launch these apps manually when you need them. Reboot and compare CPU at idle. The difference is often dramatic, especially on lower-spec machines.
Fix 2: Investigate svchost.exe
svchost.exe is a legitimate Windows process that hosts multiple Windows services. High CPU from svchost doesn’t mean something is wrong with svchost — it means one of the services running inside it is consuming too many resources. Finding which service requires one extra step.
In Task Manager → Details tab, right-click a high-CPU svchost.exe → Go to service(s). This highlights which service (or services) that specific svchost instance is hosting. Common high-CPU svchost culprits:
- wuauserv (Windows Update) — Normal during and after updates, abnormal if persistent
- DiagTrack (Connected User Experiences and Telemetry) — Windows telemetry service; can be disabled via Services if desired
- WSearch (Windows Search) — Indexing; high CPU after updates, should stabilise within hours
- BITS (Background Intelligent Transfer Service) — Windows Update downloading; should stop after updates complete
Fix 3: Disable Superfetch/SysMain
SysMain (formerly Superfetch) preloads frequently used applications into RAM to make them launch faster. On SSDs, this preloading is largely unnecessary because SSDs already load applications fast. On slower machines with insufficient RAM, SysMain can consume significant CPU and disk resources doing preloading that degrades performance rather than improving it.
Test by disabling it: Win + R → services.msc → find “SysMain” → right-click → Stop → right-click → Properties → Startup type: Disabled → OK. Restart and compare. If the machine performs noticeably better without SysMain, leave it disabled permanently. On SSDs with sufficient RAM, SysMain’s benefit is minimal and the CPU/disk overhead is real.
Fix 4: Check Power Plan
The Power Saver plan throttles the CPU, which creates a misleading high-CPU reading — the CPU is at 80% because it’s running at 40% of its normal speed, making even light workloads appear intensive. Checking this takes 30 seconds.
Win + R → powercfg.cpl → verify the current plan. If it’s Power Saver, switch to Balanced or High Performance. Also check: Settings → System → Power → Power mode → Balanced or Best performance. The improvement is immediate — clock speed increases and the same workload takes less CPU percentage to complete.
Fix 5: Rebuild the Search Index
SearchIndexer.exe at sustained high CPU for more than 24 hours after an update indicates a stuck or corrupt indexing process. Normally it completes and settles to near-zero usage; persistent high CPU means it’s looping or encountering errors it can’t resolve. Rebuilding the index from scratch is faster than waiting.
Search for “Indexing Options” in Start → Advanced → Rebuild → OK → confirm. Windows deletes the current index and builds a new one. During the rebuild (which takes 30 minutes to several hours depending on file count), SearchIndexer will use significant CPU — that’s expected and resolves when complete. To reduce future indexer overhead, click Modify in Indexing Options and narrow the indexed locations to just the folders you actually search.
Fix 6: Scan for Malware
Cryptomining malware produces exactly the symptom of high CPU usage — often showing as an unfamiliar process or disguised within a legitimate-looking process name. If CPU is high with no obvious legitimate cause and Task Manager shows unfamiliar process names at the top, malware is a real possibility.
Windows Security → Virus and threat protection → Full scan. Run Malwarebytes (free version) separately — it catches cryptominers and adware that Windows Defender frequently misses. After any malware removal, restart and check whether CPU returns to normal levels.
Fix 7: Update or Roll Back Drivers
A driver bug can consume CPU by entering an error loop — the driver tries to perform an operation, fails, and immediately retries, creating sustained high CPU from a process that should be nearly idle. GPU drivers and network adapter drivers are the most common culprits.
Event Viewer → Windows Logs → System → filter for Error and Warning entries. Look for hardware-related errors that repeat frequently (every few seconds). The source and description of these events identify which driver is looping. Update that driver from the manufacturer’s website, or roll it back if the CPU issue started after a recent driver update.
Fix 8: Runtime Broker High CPU
Runtime Broker manages permissions for Universal Windows Platform (UWP) apps from the Microsoft Store. It should use minimal CPU in normal operation. When it shows 20–30% or more: a Store app is misbehaving — constantly requesting permissions or refreshing data aggressively.
Settings → Apps → Startup apps → disable any Store apps (identified by the Windows/Microsoft Store icon) that you don’t actively use. Settings → Privacy and security → Background apps → toggle off background running for Store apps you don’t need active 24/7. News & Interests, Weather, Xbox Game Bar, and various third-party Store apps are typical offenders. After disabling background running for non-essential apps, Runtime Broker typically drops to near-zero.
Fix 9: Windows Update Running in Background
If high CPU appeared after a recent update or is happening now without apparent cause, Windows Update itself may be the culprit — downloading or staging a pending update. Check: Settings → Windows Update → see if a download is in progress. If so, let it complete — interrupting a Windows Update download sometimes causes it to restart from zero and consume CPU longer than necessary.
If no update is shown as downloading but Windows Update is still showing high CPU in Task Manager, check Update history (Settings → Windows Update → Update history) for recently installed updates and whether any are listed as failed — a failed update sometimes triggers repeated retry attempts that create persistent background CPU load.
When CPU Is High for No Identifiable Reason
If Task Manager doesn’t reveal an obvious culprit but CPU remains high: Resource Monitor (resmon.exe) provides more detail than Task Manager — particularly the CPU tab’s “Services” section which shows per-service CPU usage rather than per-process. The Analyze Wait Chain feature (right-click a process → Analyze Wait Chain) shows whether a high-CPU process is actually waiting for another blocked process, which reveals dependency chains that Task Manager alone doesn’t expose.
Performance Monitor (perfmon.exe) can log CPU usage over time with per-process detail, which is useful for catching CPU spikes that are intermittent and don’t appear during a manual check but cause sluggishness in practice.
Our guide on Windows 11 high disk usage covers the disk-side performance issues that often accompany high CPU — SysMain and search indexing affect both simultaneously. For the post-update CPU spikes where Windows Update triggered the high CPU, our post-update performance guide covers the background processes that are expected versus those that need fixing. Microsoft’s Windows performance troubleshooting documentation covers the Windows Performance Analyzer (WPA) tool for detailed CPU sampling that identifies the specific functions and drivers consuming CPU cycles beyond what Task Manager shows.
Thermal Throttling Creating Artificial High CPU
This is worth understanding: a CPU running hot doesn’t show lower CPU percentage — it can actually show higher percentage. Here’s why: when a CPU throttles due to heat, it runs at a lower clock speed. Work that would normally take 10% CPU at full speed now takes 30% at throttled speed because the processor is working three times longer to complete the same amount of computation. Task Manager shows the percentage of current clock cycles used, not an absolute measure — so a heavily throttled machine shows higher CPU percentages for the same workload.
If CPU is consistently high and the machine is also running warm — fan is loud, bottom of the laptop is hot, performance feels worse under load — check temperatures with HWiNFO64. CPU temperatures above 95°C under any workload indicate thermal throttling. Clean the heatsink with compressed air. On laptops, consider professional thermal paste replacement if cleaning doesn’t resolve the temperatures. After the thermal fix, CPU percentages at the same workload will drop significantly because the processor is running at its full rated speed.
Antivirus Scanning High CPU — Normal vs Abnormal
MsMpEng.exe (Windows Defender) at high CPU is expected during scheduled scans. The scheduled scan time can be changed: Windows Security → Virus and threat protection → Virus and threat protection settings → Manage settings → scroll to Exclusions (not to add exclusions, to navigate) → back out → Scheduled scan → change the schedule to a time when you’re not using the machine (2 AM instead of during business hours).
What’s not normal: MsMpEng.exe at high CPU for hours with no scan visibly running, or Defender CPU at 50%+ continuously day after day. This pattern often means Defender is scanning files being rapidly written by another process — like a development environment generating many small files, or a sync client uploading thousands of files. Adding the relevant folder to Defender’s exclusion list (Windows Security → Exclusions → Add an exclusion → Folder) prevents Defender from scanning every new file in real time and dramatically reduces CPU from this specific pattern.
Background App Processing from Third-Party Software
Applications installed on the machine can register background tasks that run on schedules — database indexers, email clients syncing on a timer, media libraries scanning for new files, and backup software running incremental backups all consume CPU in the background. Unlike startup programs (which are visible in Task Manager’s Startup tab), scheduled background tasks run independently and don’t appear there.
Check Task Scheduler for tasks consuming CPU: search “Task Scheduler” in Start → Task Scheduler Library → look for recently triggered tasks (the “Last Run Time” column shows when each task ran last). Tasks triggered frequently (every few minutes) with high CPU processes are worth investigating. Third-party software scheduled tasks that run every 15–30 minutes can cumulatively keep a machine’s CPU elevated throughout the day.
The Process Hacker vs Task Manager
Task Manager shows aggregate CPU per process but doesn’t show which specific threads within a process are consuming CPU. For high-CPU processes that aren’t obviously misbehaving — where the process is legitimate but seems to be using more CPU than expected — Process Hacker (or the more recent Process Hacker 2, available from their official site) provides thread-level CPU breakdowns, DLL maps, and network connection details that Task Manager doesn’t offer.
For example: a browser at 30% CPU in Task Manager might show in Process Hacker that a specific renderer thread associated with a particular tab is the source — pointing at a specific website rather than the browser generally as the root cause. This thread-level visibility saves time spent blaming applications that are actually the victims of misbehaving content or extensions running within them.
CPU Pinned at 100% During Specific Operations
CPU reaching 100% during specific operations — compressing a file, rendering video, compiling code — is expected behaviour rather than a problem. Modern applications are designed to use all available CPU for computationally intensive work. The machine feels slow during these operations because 100% of CPU is genuinely occupied, but this is the machine working correctly at maximum capacity rather than misbehaving.
The distinction: 100% CPU for 30 seconds while compressing a large file is expected. 100% CPU for hours while the screen saver is running is not. The appropriate response to expected 100% CPU is either accepting that the machine is at its computational limit for that task, or upgrading hardware if those tasks are routine and the current performance is inadequate. No Windows setting change will make a video export finish faster on hardware that’s already at 100% utilisation — the only fix is faster hardware or a more efficient application for the same task. Related: Chrome High CPU Usage.
