Problems · How to check
Why is my CPU at 100% in Task Manager?
Open Task Manager with Ctrl+Shift+Esc, click the CPU column to sort by it, and read the top row: that is your answer. A machine at 100% always has a reason with a name, and the name determines whether you wait, retime it, update it or remove it.
The usual names: Windows Update and its installer worker, the search indexer, antivirus scans, browser tabs, and sync clients. Each is legitimate software behaving badly at the wrong moment, which is why removal is rarely the right first move.
First, notice when it happens
The causes, ranked
1. Windows Update and its workers
most commonHow to confirm it
TiWorker, Windows Modules Installer Worker, Service Host groups high for long stretches; Settings shows update activity.
The fix
Let it finish, plugged in, ideally overnight. If the same item churns for days, run the Update troubleshooter and then install that KB manually.
2. Search indexing
most commonHow to confirm it
SearchIndexer or Microsoft.Search processes busy, usually after a big file move, a new drive, or an OS update reset the index.
The fix
Let it complete once; rebuilding repeatedly is worse than finishing once. Excluding huge media folders from indexing is a reasonable long-term trim.
3. Antivirus scans, scheduled inconveniently
commonHow to confirm it
Defender's or a third-party scanner's process high mid-workday; two security products installed makes it far worse.
The fix
Reschedule to hours you do not work. Never run two real-time scanners: pick one and remove the other, which alone fixes a surprising share of these cases.
4. A browser tab or extension
commonHow to confirm it
The browser's own task manager (Shift+Esc in Chrome-family browsers) attributes the load to a specific tab or extension, which the OS view lumps together.
The fix
Close or reload the offender; audit extensions, which are the quiet cause of a great many mysterious pinned cores.
5. A stuck process or genuine malware
occasionalHow to confirm it
An unfamiliar process at high CPU with the machine idle, especially with unexpected network activity. Search the exact process name before acting.
The fix
End it, then investigate: legitimate names return, malicious ones need a full scan and possibly a clean install. Do not end processes you cannot identify without searching first.
6. System Interrupts and driver trouble
occasionalHow to confirm it
System Interrupts holding several percent or more persistently points at a driver or device misbehaving rather than an application.
The fix
Update chipset and device drivers from the maker; disconnect peripherals one at a time to find a guilty device.
Measure it instead of guessing
Once the process list is quiet, the sustained test answers the second question: is the machine slow because something was stealing it, or slow anyway. A flat curve on an idle-clean machine says the CPU was fine and the thief was software; a sliding curve says heat is the second problem waiting behind the first.
What software cannot tell you here
- We cannot see your process list; Task Manager is the tool and this article is the map for reading it.
- We cannot judge whether an unfamiliar process is malicious; searching its exact name is the honest first step.
Asked, in people’s own words
- Why is my CPU at 100% when nothing is open?
- Because something is open that has no window: indexing, updates, scans and sync all run headless. Sorting Task Manager by CPU always names it, and the name is nearly always one of that short list rather than anything sinister.
- Is 100% CPU usage bad for the processor?
- No: processors are designed to run at full load indefinitely and protect themselves with throttling. The cost is responsiveness now, heat, and battery drain, not damage. Sustained 100% at idle is worth fixing for those reasons, not out of fear for the silicon.
- How do I fix 100% CPU usage in Windows?
- Name it, then treat it: wait out updates and indexing, reschedule scans, close or audit browser tabs and extensions, update drivers for System Interrupts, and scan for malware only after ruling the legitimate suspects out. Blind fixes and cleaner utilities skip the naming step, which is where the whole answer lives.