How do I find which app is making my computer work too hard?
Quick answer
On Windows, open Task Manager and review the Processes view for CPU, memory, and disk usage. Its Performance view shows real-time resource graphs. Note which apps are active and what you were doing, then check whether a high reading persists or appears during a particular task. A high reading by itself does not prove there is a problem or identify its cause, so look for a repeated pattern before drawing conclusions. [S1]
The question, the details, the next step.
How do I find which app is making my computer work too hard? I sometimes notice it feels sluggish, but I don't know what to look at.
On Windows, use Task Manager as an observation tool. In its Processes view, you can compare CPU, memory, and disk usage for apps and processes. The Performance view provides real-time resource graphs. [S1]
Start by checking what is active while the computer feels sluggish. Write down the app or process names and the readings you see; then note what you were doing at the time. A single high reading is only a clue: it does not establish that something is wrong or explain the cause. [S1]
What should I make of CPU, memory, and disk? Should I just focus on whichever number looks highest?
Treat them as separate readings, not as a contest where the highest number automatically wins. Task Manager shows these usage categories for apps and processes, while the Performance view lets you watch resource activity over time. [S1]
A useful question is not just “Which reading is high?” but “What was happening then, and does the same pattern return?” For example, a busy-looking process while you are actively using an app is not, on that evidence alone, a fault. Record the reading alongside the activity rather than labeling the process as a problem immediately.
Can you show me how to check without jumping to conclusions?
Try a short, repeatable observation:
- When the computer feels slow, note the time and what you were doing.
- In Task Manager’s Processes view, note visible app or process names and CPU, memory, and disk readings.
- Look at the Performance view to see whether activity changes while you wait or continue the same task.
- If practical, check again during a different ordinary activity and compare the notes.
Task Manager can show what is using resources at a particular time, but that snapshot does not by itself identify a cause. Observing the pattern in context is more useful than treating one high reading as proof. [S1]
What would a simple worksheet look like? I want something I can fill in before asking someone for help.
Use this copyable resource-monitoring worksheet. Leave anything you cannot tell blank; do not guess what a process does.
Observation [number]
- Date/time: [fill in]
- What I was doing: [task or app]
- What felt slow, and when: [brief description]
- Task Manager Processes view: [app/process names and CPU, memory, disk readings you observed]
- Performance view: [what changed over the observation period]
- Did the same pattern appear during another activity? [yes/no/not checked; notes]
- What I have not established: [for example, whether the reading caused the slowdown]
Example using placeholders: “Observation 1; [time]; using [app]; sluggishness noticed while [task]; Processes view showed [process] with [observed readings]; Performance view [what I saw change or remain steady]. Cause not established.” This is a record of what you observed, not a diagnosis.
If one process keeps appearing near the top, does that mean I should stop or remove it?
Not from that observation alone. A high reading does not establish that a process is problematic or identify why the computer feels slow. [S1] First check whether the same pattern appears repeatedly and note what you were doing at the time. If you need help, share the worksheet with a qualified support person and ask what the recorded pattern might mean before making changes. The observations can narrow the conversation, but they do not prove a cause.
A practical checklist
Check Task Manager while the slowdown is happening.
Record app or process names and CPU, memory, and disk readings.
Use the Performance view to observe activity over time.
Note what you were doing alongside each observation.
Compare more than one observation before deciding a process is a problem.
A few more useful answers
Does one high reading prove an app is causing the slowdown?
No. A high reading alone does not establish a problem or identify a cause. Compare it with what you were doing and whether the pattern repeats. [S1]
Which Task Manager views should I use?
Use Processes to compare CPU, memory, disk, and network usage for apps and processes. Use Performance to view real-time resource graphs. [S1]
What if the readings look busy but I cannot tell what they mean?
Keep the worksheet focused on what you observed and what was happening at the time. A qualified support person can help interpret the pattern; the readings alone do not establish its cause.
Sources
References used for this guide.
- [S1] Use a screen reader to navigate Windows support tools support.microsoft.com · Checked