# High CPU Usage on Windows: Find the Program Doing the Work

When the fans become loud and switching windows feels slow, high CPU usage is a useful clue. Find the program doing the work before clearing caches. Builds, video exports and updates can keep a processor busy until the task finishes.

## Identify the program and watch the duration

Press `Ctrl + Shift + Esc` to open Task Manager, sort Processes by CPU, and note the busiest program and what you were doing. Look again after a short wait. A task making progress is different from sustained activity with no obvious work.

A browser can have processes for pages, extensions and background features. One process name does not necessarily mean one independent application. Check downloads, synchronization, updates and open content inside the app before ending every process with the same name.

| What you observe | What to check first |
| --- | --- |
| Usage rises during a build, export or installation, then falls | Whether the task has finished |
| A browser stays busy | Pages, extensions and its own browser task manager |
| Several programs are busy just after sign-in | Startup apps, synchronization and updates, then whether activity settles |
| A system process stays busy without an obvious task | Windows Update, Windows Security and device drivers; keep the process running while investigating |

Microsoft's [performance troubleshooting guidance](https://support.microsoft.com/en-us/windows/experience/performance-optimization/tips-to-improve-pc-performance-in-windows) treats background apps, storage, updates and hardware as separate considerations. A CPU percentage alone does not establish that the PC needs cleaning.

## Follow an app and its child processes in Mole

Mole's Status page puts CPU, memory, disk and network activity together. The process list can be sorted by usage and searched by app name, process name or PID. Background children can lead you back to their owning app rather than leaving you to guess among repeated names.

Open a process to inspect the available information about its parent, services, startup source and listening ports. Unavailable information remains unknown. Establish what the program belongs to before stopping its task, quitting normally or investigating Windows logs.

Those details explain how a process appeared. They do not prove why it is using CPU. Relate them to the action you performed and the readings that follow.

## Save your work before ending a process

Save documents, projects and browser forms. Cancel a task inside its app when possible, then quit normally and check whether CPU usage falls. Ending a process can lose unsaved work or interrupt file writes. System processes and runtimes shared by several apps should not be ended just to reduce a number.

For Edge activity after its windows close, see [why Edge keeps running in the background](/windows/blog/edge-running-in-background). For many apps launching at every sign-in, use the [startup review guide](/windows/blog/manage-windows-startup). Each has a different control.

## Repeat the same work to check the result

After changing one page, extension or background setting, repeat the work that was slow. Lower CPU usage together with smoother operation supports that change for this problem. A quiet moment after restarting does not establish that the cause is fixed.

If sustained activity comes with overheating, blue screens or disk errors, record the program, time, Windows version and app version for system or vendor troubleshooting. Cleaning can recover storage space; it does not diagnose those failures.


Canonical: https://mole.fit/windows/blog/windows-high-cpu-usage