A Task Manager is a built-in Windows tool that shows what apps and background processes are running, and how they use system resources. Techs rely on it because it replaces guesses with live data. For CompTIA A+ Core 2 (220-1202), Domain 1, Objective 1.4, you're expected to use Task Manager as a first-line troubleshooting tool in real scenarios.
In this guide, you'll learn how to use the Processes, Performance, Startup, Services, and Users tabs to diagnose common PC issues. These include a slow system, high CPU use, an app that won't respond, or unknown background activity. The goal is simple: confirm the symptom, find the cause, and choose a safe fix.
What Task Manager shows you, and when to open it
Task Manager answers a basic question fast: "What's happening on this PC right now?" That matters because many problems look the same at the surface. A "slow computer" could be high CPU, low memory, heavy disk use, or a stalled network transfer. Task Manager helps you confirm which resource is under stress, while the issue is happening.
Open Task Manager as soon as you see any of these signs:
- The cursor stutters or windows lag when you move them
- The fan runs loud for minutes, even at idle
- Apps freeze, show "Not responding", or take a long time to open
- Boot feels slow, with long waits after signing in
- Network feels fine, yet downloads crawl
Windows gives you several quick ways to open it, so you can choose what works even when the PC is partly frozen:
- Press Ctrl + Shift + Esc
- Press Ctrl + Alt + Del, then select Task Manager
- Right-click the taskbar, then select Task Manager
- Use Run (Windows key + R), type
taskmgr, then press Enter
When Task Manager opens, you may see a simple view that lists only open apps. Select More details to show full tabs and columns. Techs almost always use the detailed view because it shows resource usage, startup items, and services.
To connect what you see to what a user feels, keep these resource terms straight:
| Resource | What it measures | What users often notice |
|---|---|---|
| CPU | Processor work happening now | Heat, loud fan, lag, slow clicks |
| Memory (RAM) | Working space for active tasks | Slow app switching, freezes, heavy paging |
| Disk | Read and write activity on storage | Long load times, "stuck" installs, slow boot |
| Network | Data moving in and out | Slow downloads, choppy calls, cloud sync delays |
| GPU | Graphics processing work | Stutter in video, high GPU use in games or apps |
The key takeaway is that Task Manager links symptoms to evidence. Once you see the stressed resource, you can narrow the suspect list quickly.
A quick tour of the main tabs you will use on the exam
Processes answers: Which app or background process is using CPU, memory, disk, or network right now?
Performance answers: Which hardware resource is the bottleneck, and how does usage change over time?
Startup answers: What runs at sign-in, and which items slow boot?
Users answers: Which signed-in user sessions are consuming resources?
Services answers: Which background Windows services are running, and can you restart one to restore a function?
Some tabs and labels vary a bit by Windows version, but these core ideas stay consistent.
First safety checks before you end tasks
Ending the wrong process can cause data loss or a crash. That risk rises when the PC already feels unstable, because a "quick fix" can create a bigger problem.
Follow a simple safety routine:
- Save work first if the app still responds at all.
- Close the app normally before you end it in Task Manager.
- Treat Microsoft system processes with care, especially if you don't recognize the name.
- Write down what you changed, so you can reverse it or explain it later.
- Research unknown names, but watch for lookalike process names used by malware.
If you can't explain what a process does, pause and verify it first. Fast actions are useful, but safe actions fix more machines.
Use the Processes tab to find what is slowing a PC
The Processes tab is where most troubleshooting starts. It lists apps, background processes, and Windows processes, along with their resource use. The best approach is structured, so you don't chase the wrong clue.
Use this workflow when a user reports "the PC is slow":
- Sort by CPU to find sustained high usage. A process near 80 to 100 percent for several minutes is a strong suspect.
- Sort by Memory to spot a heavy app or a memory leak pattern. Large use is not always bad, but it can push the system into paging.
- Sort by Disk to find what's driving long load times. A single update or sync tool can keep a disk busy.
- Sort by Network when the complaint is slow browsing, slow downloads, or cloud sync delays.
Read the columns like evidence. CPU shows work rate, memory shows working set size, disk shows read and write activity, and network shows throughput. In addition, you can expand grouped apps to see their child processes.