What is Task Manager?
Task Manager is usually the first tool a technician opens when a Windows PC is slow, frozen or acting strangely. It shows what is running right now and which resource is under load. From the same window you can end a hung app, restart the Windows shell, disable startup items and start or stop services, without opening a separate console.
How to open Task Manager
- Ctrl+Shift+Esc opens it directly, the fastest route when the desktop is sluggish.
- Ctrl+Alt+Del, then Task Manager. This works even when the taskbar is not responding.
- Right-click the Start button (the Win+X menu) or, on current Windows 11 builds, right-click the taskbar.
- Type
taskmgrin Run (Win+R), Command Prompt or PowerShell.
Windows 10 may open a compact view that lists only open apps; select More details to see everything. Windows 11 version 22H2 and later replaced the tab strip with a navigation pane on the left and renamed the Startup tab to Startup apps.
The pages and what they answer
| Page | What it shows | Typical use |
|---|---|---|
| Processes | Apps, background processes and Windows processes with CPU, memory, disk, network and GPU columns | Sort a column to find the heavy user; End task; restart Windows Explorer; Efficiency mode on Windows 11 |
| Performance | Live graphs for CPU, memory, each disk, each network adapter and the GPU; the CPU page shows uptime | Identify which resource is the bottleneck; link to Resource Monitor |
| App history | Resource use accumulated over time, mainly for Microsoft Store apps | Spot an app that used heavy CPU time or data |
| Startup apps | Programs that launch at sign-in, with publisher, status and Startup impact | Disable unneeded items to speed up sign-in |
| Users | Signed-in user sessions and their resource use | Disconnect or sign out a session that is hogging a shared PC |
| Details | Every process by image name, with its process ID (PID), status and user name | Set priority or affinity, end a process tree, create a dump file, open the file location |
| Services | Windows services with PID and status | Start, stop or restart a service; open the Services console |
Troubleshooting with Task Manager
- Slow PC: on Processes, sort by CPU, then Memory, then Disk. A process holding high CPU for minutes is a suspect; a short spike while an app opens is normal. Disk stuck near 100% with low CPU often means updates, indexing, a malware scan, or a slow or failing hard drive.
- App shows Not responding: give it a moment if it is waiting on a file or network share, try closing it normally, then use End task. Unsaved work in that app is lost.
- Taskbar or desktop frozen: select Windows Explorer on Processes and choose Restart. If explorer.exe has closed completely, use Run new task and type
explorer. The same dialog has a checkbox to create the task with administrative privileges. - Slow sign-in: on Startup apps, disable High-impact items the user does not need. Disabling only stops the automatic launch; nothing is uninstalled.
- Suspicious process: right-click and choose Open file location or Search online. A Windows name such as svchost.exe running from a user's AppData folder instead of
C:\Windows\System32is a red flag. - Windows feature not working (printing, updates): restart the related service from the Services page.
Task Manager vs. similar tools
Task Manager is a live summary. Resource Monitor (resmon) goes deeper, down to the files, network connections and listening ports each process uses. Performance Monitor (perfmon) logs counters over time so you can compare against a baseline. The Services console (services.msc) shows startup type and recovery options that Task Manager's Services page leaves out. The command-line counterparts are tasklist and taskkill /PID 1234 or taskkill /IM app.exe /F.
Task Manager on the CompTIA A+ exam
Task Manager is one of the Windows tools in Core 2 (220-1202) objective 1.4, and it is a first-line tool for the slow-performance, slow-boot and frozen-app scenarios in objective 3.1. Know Ctrl+Shift+Esc and taskmgr, what each page shows, and the least risky action for each symptom. Cues: slow after sign-in, think Startup apps; which process is using the CPU, think Processes; you need a PID, think Details; a service has stopped, think Services; another user's session is eating memory, think Users.