Ninety days of notes: what actually changed
I rebuilt a five-year-old laptop, a gaming desktop and a work machine with the same tool. Here is the honest ledger — what improved, what I imagined, and what I had to put back.
Three machines, one method
I did not set out to write about this. I set out to stop losing an afternoon every time I reinstalled Windows. Over three months I put the same tool through three machines that have almost nothing in common: a thin 2021 laptop with 8 GB of soldered RAM, a desktop I built for games, and the laptop I actually earn a living on. Same process each time, notes taken at every step.
The utility I settled on is an open-source one — Winhance — which groups the usual Windows housekeeping into four screens: apps, optimizations, customizations, and a set of advanced tools for building installation media. It does not invent anything Windows cannot already do. What it does is put a few hundred registry values, package removals and service changes behind labelled switches, with the registry path visible next to each one if you ask for it.
That last detail is the reason I kept using it. A tool that shows me what it is about to write is a tool I can argue with.
What the first run actually does
On first launch it creates a system restore point, takes a full registry backup, and writes a configuration file capturing the current value of every setting it manages. Those three artefacts are your entire safety net, and they are only created once, so the very first launch matters more than any launch after it.
Check the backups exist before you touch anything
Open C:\ProgramData\Winhance\Backups and confirm there are files with today's
date. Then open System Protection and confirm the restore point is listed. Thirty seconds of
checking has saved me twice.
My habit now is to launch it, close it, verify the backups, and only then start flipping anything. It feels pedantic. It is pedantic. It is also the reason I have never lost a machine.
The 2021 laptop
This is the machine where debloating earns its reputation. Eight gigabytes of RAM, a slow-ish NVMe drive, and a factory image carrying a manufacturer's support suite, three trial applications and the usual pinned tiles. Idle memory sat around 4.1 GB with nothing open.
I removed the store apps I could name and would never open, disabled the widgets feed, turned off the suggested-content surfaces in Start and Settings, and set the power plan to something less apologetic. Idle memory after a restart: roughly 2.9 GB. Cold boot to a usable desktop went from a stopwatch-honest 51 seconds to 38.
Is that a transformed machine? No. It is a machine that stopped fighting me for the first thirty seconds after login, which on an 8 GB laptop is most of the experience.
The gaming desktop
Here the results were far less dramatic and I want to be blunt about it. A desktop with 32 GB of RAM and a current GPU does not care that OneDrive is running. Average frame rates in three titles moved by less than the run-to-run variance. I measured, I re-measured, and I could not honestly claim a win.
What did change was the shape of the frametime graph in two of the three titles — fewer of the small hitches that come from background work firing at the wrong moment. And the machine stopped deciding to install a driver update mid-session, which was the actual complaint I had.
On a fast machine, debloating buys you predictability, not speed. Those are different products and it is worth knowing which one you are shopping for.
The work machine, where I stopped
I applied maybe a fifth of what I applied elsewhere. No package removals at all. Privacy toggles that do not touch anything my employer's tooling depends on, the taskbar and Explorer changes that save me clicks, and nothing else.
If a machine is managed by someone else, or if you cannot afford a bad Tuesday morning, the correct amount of aggressive debloating is close to zero. The tool will happily let you do more. That is not the same as it being a good idea.
Two things I had to put back
I removed a Windows component on the laptop that a scanner driver quietly depended on, and I disabled a notification category that turned out to carry my calendar reminders. Both were reversible in under five minutes because I had a config export from before. Neither would have been obvious from the label alone.
The ninety-day verdict
Three months in, all three machines are still running the configuration I applied, and I have rebuilt the laptop once from an exported config in about fifteen minutes. That last number is the one that changed how I work.
The tool did not make my computers fast. My computers were already as fast as their hardware. What it did was remove a category of low-grade friction — the ads in Start, the feed I never opened, the update that arrived at the worst moment — and make the resulting state something I can save, review and reapply. For an afternoon of careful attention, that is a fair trade.
If you are coming to this from a machine that feels slow, read the checklist first. If you are coming from a machine that feels noisy, start with privacy and telemetry.
Written on my own hardware, with my own money, on my own time. Nobody paid for a mention here. If a page ever does contain a paid placement or an affiliate link, it will say so at the top — see the disclaimer.