Debloating without breaking Windows: the checklist I actually follow
Removing things from Windows is easy. Removing the right things, in an order you can walk back, is the part nobody writes down. So I wrote it down.
Four rules before you start
Every debloating disaster I have read about — and the two small ones I caused myself — came from skipping one of these. They are boring. That is the point.
Have a way back before you need one
Restore point, registry backup, and a configuration export of the machine as it is now. If you cannot name where all three live, you are not ready to start.
Change one category at a time, then restart
Twenty changes at once means twenty suspects when something misbehaves. One category at a time means a five-minute diagnosis.
Read the technical detail, not just the label
Most tools, Winhance included, can show the registry path and the value being written. Turn that on. A label tells you what someone hoped the setting does; the path tells you what it does.
Write down what you changed
An exported config counts as writing it down. So does a text file. Future you, three months from now, will not remember.
The order I work in
I go from most reversible to least, so that if I lose my nerve halfway through I am always standing somewhere safe.
| Stage | What I change | Risk | Restart needed |
|---|---|---|---|
| 1 | Customization — taskbar, Start, Explorer, theme | Very low | No |
| 2 | Notification and sound settings | Very low | No |
| 3 | Privacy and telemetry toggles | Low | Some |
| 4 | Power and performance settings | Low | Yes |
| 5 | Update behaviour | Medium | Yes |
| 6 | Store app removal | Medium | No |
| 7 | Windows features, capabilities, packages | High | Yes |
Stages one and two are pure preference and cannot hurt you. Stage seven is where people get into trouble, and it is the only stage I do on a machine I have just imaged rather than one I have been living on for a year.
Things I no longer remove
This list is shorter than it used to be, because experience trimmed it.
- Windows Security. If you are not deliberately replacing it with something else that works, leave it running. A machine with no active protection is a worse outcome than a machine with a few megabytes of overhead.
- The Microsoft Store itself. Removing it is possible and I regretted it inside a week; several unrelated apps update through it.
- Print and scan components, unless I am certain the machine will never meet a printer. Drivers pull on dependencies you cannot see from the label.
- Anything on a machine I do not own.
Edge, OneDrive, Copilot and Recall
These four are the headline removals in every debloating guide, and they are genuinely removable. They are also the four most likely to be re-added by a feature update, and the ones most likely to break a workflow you forgot you had — a work file syncing quietly, a link that opens a support tool, a saved password. Decide deliberately rather than because the toggle was there.
Reversible, irreversible, and how to tell
Roughly three tiers exist. Registry-based toggles are almost always reversible: the tool wrote a value, it can write the old one back. Service and scheduled-task changes are reversible but may need a restart before the machine agrees. Package and capability removals are the dangerous tier — some can be reinstalled from Windows Update or the Store, and some cannot be reinstalled at all without a repair install.
Good tools mark this in the interface. A good one shows an indicator on removals that cannot be undone. Read those indicators as though they were written by someone who has already made the mistake, because they were.
After the restart
Restart even when nothing tells you to, then spend ten minutes doing ordinary things: open a PDF, print a test page, join a video call, plug in a USB drive, sign in to the thing you sign in to every morning. Problems from debloating rarely announce themselves. They wait until you are in a hurry.
Then export the configuration again and keep both files — before and after. That pair is the most useful thing you will produce all afternoon, and it is what makes the second machine take fifteen minutes.
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.