When a PC suddenly feels sluggish, Task Manager is the first place to look. It shows you exactly which programs are using your CPU, RAM, disk and network in real time, so you can identify the culprit and shut it down in seconds rather than guessing.

Key takeaway: Task Manager lets you instantly see which background apps are hogging resources and close them safely without hunting through menus.

Opening and reading Task Manager

  1. Right-click the taskbar and select Task Manager, or press Ctrl+Shift+Esc.
  2. Click More details if you see the simplified view.
  3. On the Processes tab, click the CPU column header to sort by highest usage, then click Memory to check RAM usage the same way.
  4. Look for anything unexpected sitting near the top of the list, especially entries grouped under "Background processes".
  5. Right-click a resource-heavy item and choose End task to close it immediately.

Before you start: Never end tasks under "Windows processes" unless you're certain what they are – these are core system components. Only close items you recognise as ordinary applications or background helpers.

Identifying what's safe to close

Background processes are typically apps that are open but minimised, browser extensions, or helper tools for hardware and software you've installed. If you see multiple entries for the same browser (Chrome and Edge are common offenders) each open tab and extension can appear as its own process, all adding up in RAM usage.

  1. For a browser using excessive memory, close unused tabs first, then check its own task manager (in Chrome, press Shift+Esc) to find the specific tab or extension responsible.
  2. For unfamiliar process names, right-click the entry and choose Search online or Properties to see which program it belongs to before ending it.
  3. If an app keeps relaunching itself in the background after every restart, go back and disable it properly via Task Manager > Startup apps rather than closing it manually each time.

Tip: The Performance tab in Task Manager gives you a live graph of overall CPU, memory and disk usage, which is handy for confirming that closing a process actually freed up resources.

Using Resource Monitor for more detail

If you want more depth than Task Manager offers, type Resource Monitor into the Start menu search box. It breaks down exactly which process is reading or writing to your disk at any moment, which is particularly useful for tracking down a program causing disk activity to spike (shown as 100% disk usage) on machines with a traditional hard drive.

Setting up recurring checks

Rather than only opening Task Manager when things already feel slow, it's worth getting into the habit of glancing at it every week or two, especially after installing new software. Many programs quietly add themselves to your background processes and startup list without asking, and catching this early stops the slowdown building up gradually over months until it becomes hard to ignore. A quick sort by CPU and Memory takes only a few seconds and tells you everything you need to know.

Tip: You can pin Task Manager to your taskbar for quick access – right-click its icon while it's open and choose "Pin to taskbar" so it's always one click away.

Combined with trimming your startup programs list, regularly checking Task Manager for runaway background apps is one of the simplest habits you can build to keep an older or budget PC feeling consistently responsive, rather than needing an occasional big clean-up once things have already slowed to a crawl.

Frequently asked questions

Is it safe to end any task in Task Manager?
Most ordinary applications and background apps are safe to end, but avoid closing anything listed under Windows processes unless you know exactly what it does.
Why does my PC show 100% disk usage with hardly anything open?
This is common on machines with a traditional hard drive rather than an SSD, often caused by Windows Update, Superfetch/SysMain, or antivirus scans running in the background.
Will ending a task close the program permanently?
Ending a task only closes it for the current session; it will run again next time you open it or restart your PC unless you also disable it from starting automatically.