A desktop that feels slow is rarely a desktop that actually is slow. Most of the time, the hardware has more to give, and the operating system is wasting it through defaults that prioritize cold-boot safety over day-to-day feel. The good news is that the fixes cost nothing and take less than an hour in total. The bad news is they are not the kind of fix you can buy in a box, and there is no glossy box to look for.
I have run this checklist on a handful of systems over the years, and the part that consistently surprises people is how much of the supposed slowdown was self-inflicted. The list below is in the order I run it. Tweak at your own pace, reboot between changes, and only move on if the machine still feels right.
Start with the memory profile nobody enabled
Memory kits advertise a speed they almost never run at out of the box. Motherboards default to a conservative JEDEC profile (the standardized baseline frequency every memory module is guaranteed to hit, used so the system can boot on day one with any RAM installed) so that any combination of CPU and RAM will at least post, regardless of how good the silicon lottery is. That default is the difference between RAM running at the rated speed you paid for and running at the baseline JEDEC number on the box, which can be hundreds of MT/s lower. On a memory-sensitive workload, like compiling, video editing, or even heavy browser tabs, the gap is real.
Enabling the rated profile is a quick job. Reboot into the UEFI (the firmware settings menu built into the motherboard, replacing the older text-based BIOS), find the XMP (Intel) or EXPO (AMD) setting under the memory or overclock section, and pick the highest profile that matches your kit. Save, reboot, and confirm with a stress test (a program that deliberately maxes out the memory to catch instabilities).
If the system refuses to boot, do not panic. A small fraction of kits will not train at full speed on a particular CPU. Drop one timing step, lower the speed by 200 MT/s, and try again. The goal is the fastest profile you can hold under load, not a benchmark number. Treat the box as a ceiling, not a guarantee.
Common stress tools include TestMem5 and Karhu, which the open-source community uses to surface RAM errors after a memory change. If you see any errors, dial back. Stability matters more than headline speed, especially because the symptoms of an unstable profile are data corruption, not a clear crash.
Then clean the storage closet
A drive that is consistently above 90 percent full performs worse than the same drive at 50 percent. That is not a folklore rule, it is how SSDs handle the physical limits of writing to nearly-full flash. The reason nobody notices is that it happens slowly, until one day the Start menu takes a long beat to open and you start shopping for a new drive.
Two habits help more than any tweak. First, run cleanmgr as Administrator, including the system files option, on a quarterly schedule. Second, open Settings, Storage, and look at what is actually using space. The breakdown usually shows one large game you forgot you owned, a backup folder that never got pruned, and a dozen installer files in Downloads.
For SSDs, confirm TRIM is enabled. TRIM is a command the operating system sends to the SSD to tell it which blocks are no longer in use, letting the drive clean them up ahead of time instead of during a write. Without it, SSDs slow down as they fill. Run fsutil behavior query DisableDeleteNotify in an elevated command prompt. A zero means TRIM is active. Anything else, fix it with fsutil behavior set DisableDeleteNotify 0.
The honest part of this step is that you actually have to delete files. A six terabyte secondary drive makes the conversation easier. On a single 512 GB boot drive, the cleanup is more disciplined and the savings more visible.
Then look at the startup list, for real
Open Task Manager and click the Startup Apps tab. I check this twice a year on every machine I touch, and every time I find at least five things that have been booting for months without earning their keep. The startup tab also estimates impact, which is a useful proxy for where to start.
Disable anything you do not need at boot, and uninstall anything you do not need at all. The half-life of software on a personal machine is months, and the install list is rarely pruned.
For services, msconfig is still the friendliest tool. Hide all Microsoft services first, then disable the rest, one at a time. If something breaks a week later, re-enable that one service. The change is reversible, which is what makes this safe to do without a perfect understanding of every entry. The wins show up in the first minute of every login, where most people feel the slowness most.
Then update drivers and firmware, but on purpose
Drivers and firmware updates are a fix that earns trust slowly. Most are harmless. A few introduce regressions. The right posture is to update on a reason, not on a schedule, and to know how to roll back when you need to.
GPU drivers are the highest-value update and the most likely to bite you. Get them from the GPU vendor, not Windows Update. Motherboard firmware updates land less often, but they unlock RAM compatibility and occasionally patch security issues. Check the support page for your exact model, read the changelog, and only flash if a listed fix is something you actually need.
A reasonable rule: update when there is a specific game, application, or hardware feature you want, not because a notification said so. And keep the installer, or at least a screenshot of the version, so a rollback is one step rather than a research project.
Trade-offs
None of this replaces the upgrade you will eventually need. It does, in a measurable way, change how the machine you already have feels.
- The biggest single gain is also the only step with a real chance of failure. Memory training is mostly safe, but a bad profile can corrupt data, so treat the rated speed as a ceiling, not a guarantee.
- Storage cleanup is the highest-payoff quarterly habit, but a habit is what it has to be. A single decluttering session does not keep a drive healthy forever.
- Disabling startup apps changes boot time, not multitasking speed. People who think their PC is slow because of browser tabs are looking at the wrong place.
- Driver updates can regress. The fix is usually the next driver, but it costs an evening when it happens.
What I would tell past me
Run the four steps in order, with reboots between them, on a weekend when nothing important is scheduled. Most of the time, the system feels meaningfully newer after the changes, and the boot-to-desktop wait shrinks enough to be noticeable. Sometimes you will find a bad memory kit or a driver regression, and the cost of an evening is the price of a free upgrade that you cannot buy.