“Slow” can describe several different problems: reaching the desktop takes too long, a browser pauses, a game stutters or the whole machine freezes. Write down which one you mean, when it happens and what changed recently. That small description is more useful than trying every speed-up tip at once.

Observe the problem while it happens

Save your work, restart Windows and reproduce the ordinary task that feels slow. Open Task Manager with Ctrl, Shift and Esc. Its Processes view lets you compare CPU, memory and disk activity. Sort one column at a time and note the application names associated with sustained activity.

A momentary spike while an app opens is different from a resource staying busy throughout a slowdown. Compare an idle period with the troublesome task. Do not end an unfamiliar process simply because it appears near the top. A busy update, security scan or file transfer may be doing useful work.

Try a small, relevant change

If a familiar application is consuming resources, save its work and close it normally. Repeat the same task. For a slow sign-in, review startup applications instead of removing unrelated programs. For a nearly full system drive, inspect Windows storage recommendations and review files before deleting them.

Microsoft identifies limited storage, excess startup activity, outdated software and older hardware as possible contributors. These are investigation paths, not a diagnosis from one percentage reading. Installing a large collection of cleaner utilities makes it harder to know which change helped.

Check the physical and manufacturer side

Dell’s troubleshooting guidance includes clear air vents and appropriate thermal settings alongside software checks. For your own make and model, use its official support instructions. Keep the PC on a suitable surface and inspect external vents without opening equipment you are not comfortable servicing.

If the PC freezes, restarts unexpectedly or reports storage errors, back up important files and use the manufacturer’s applicable hardware diagnostic. A failure code is a reason to seek model-specific support, rather than trying increasingly aggressive Windows tweaks. Do not assume a diagnostic intended for one manufacturer belongs on another PC.

Build a useful before-and-after record

  • Describe the task and the point at which it slows down.
  • Record the applications open and the resource that stays busy.
  • Make one change and repeat the same workload.
  • Keep the result, even if there was no improvement.

That record also makes support easier if the issue remains. An older machine may have a genuine capacity limit, but choosing more memory, faster storage or a replacement PC should follow evidence about your workload.

Sources & further reading

Checked 17 Nov 2026. Source-based reporting and guidance; individual test results are identified where available.

Found something that needs correcting?

Tell us the article title, the detail and a supporting source.

Corrections & contact →