Read Task Manager

Choose the Task Manager view that answers the question

Microsoft lists Task Manager among Windows system configuration tools for monitoring applications, processes, performance and startup behavior. The Processes page is a live workload view; Performance shows longer resource graphs; Startup apps concerns sign-in behavior; Users separates active sessions; Details exposes lower-level process information.

Do not search every tab for the same answer. If the PC feels slow now, begin with Processes and Performance. If sign-in is slow, use Startup apps. If another signed-in user is consuming resources, use Users. Details and Services are advanced views where names are less friendly and mistakes have wider effects.

Create an idle and workload baseline

Open Task Manager with Ctrl + Shift + Esc and wait one minute without launching new applications. Record overall CPU, memory and disk use. Then perform the normal task that feels slow—such as opening a project, exporting a file or joining a call—and watch what changes. A brief CPU spike during launch is normal; a sustained bottleneck that matches the symptom is more useful evidence.

Click a column heading to sort descending. Expand an application group to see related child processes. Names such as Service Host can represent Windows services and should not be ended simply because they appear often. Right-click a process and use Search online or Open file location only when you need to identify it; verify the publisher and path.

1. 1

   Press Ctrl + Shift + Esc.

2. 2

   On Processes, wait one minute and record overall CPU, Memory and Disk percentages.

3. 3

   Sort by CPU and note the top process, then repeat for Memory and Disk.

4. 4

   Run one normal workload and observe which process changes with the symptom.

5. 5

   Open Performance and note the graph shape rather than only the latest number.

6. 6

   Save a screenshot or written snapshot with timestamp and workload description.

Interpret common resource patterns

High CPU means the processor is busy; it can come from useful work, updates, browser tabs, compression or a stuck process. High memory means applications are holding a large share of RAM; Windows also uses memory for caching, so the goal is not zero use. Disk at 100 percent indicates the drive is fully busy at that moment, but the transfer rate and response time help distinguish a slow drive from a genuinely large workload. Network use should be tied to an app and expected transfer.

Microsoft's performance guidance recommends checking resource-heavy apps, startup load, updates and storage as part of a broader process. Task Manager identifies correlation; it does not automatically prove the root cause.

End a task only for a clear user-level failure

If a normal application is unresponsive and work cannot be saved through its interface, select that application and choose End task. This forcibly closes it and can discard unsaved data. Reopen the application and check its recovery feature. Repeated freezing needs application updates, add-on checks, file testing or vendor support—not repeated force-closing as a permanent fix.

Avoid ending Windows processes, security tools, storage services or unfamiliar background components. A process that immediately returns may be managed by a service or scheduled task. Restarting Windows is safer than terminating a chain of system processes when you do not understand their dependencies.

Common mistakes to avoid

• Ending the process with the highest number before understanding its purpose.
• Treating every short CPU or disk spike as a fault.
• Comparing readings taken during different workloads without noting the difference.
• Using Task Manager as proof of malware based only on an unfamiliar process name.