Windows Reset vs Clean Install: What Each One Leaves Behind

What Reset actually does

Reset this PC, under Settings > System > Recovery, lays down a new Windows image using either local files or a fresh download from Microsoft — the cloud-download option, roughly 4 GB, which also repairs a corrupted local copy. "Keep my files" reinstalls Windows and removes every third-party app and setting while preserving your personal folders; "Remove everything" adds your files to that list. The second page of the wizard matters more than the first: a plain file removal leaves data recoverable to anyone who gets the disk, while the "clean the drive" option overwrites the volume first. What Reset never touches is the partition layout itself — extra partitions, the recovery image, your D: drive with its data, and the firmware settings all pass through untouched.

What survives both Reset and a clean install

Even the cleanest reinstall is not full sterilization. Assume these survive:

• Firmware and UEFI settings: passwords, boot order, Secure Boot state — and in the worst case a firmware implant, which no disk operation removes
• Other physical drives and every data partition you did not explicitly delete during setup
• BitLocker recovery keys and Microsoft-account binding, which is why a PC can feel "already activated" after reinstalling
• OEM recovery partitions: Reset often reinstalls from them, which is how the manufacturer's trialware comes back after "starting fresh"
• Files on the disk if you chose the fast "remove files" path instead of "clean the drive"

When each one is the right call

Reset is the tool of speed: a broken update, a system that will not boot into a usable state, a hand-me-down within the family, or a laptop being sold with "clean the drive" ticked — twenty minutes versus an evening, and on a modern machine the result is nearly indistinguishable. The USB install earns its hassle in specific cases: years of accumulated drivers and services you want truly gone, a rootkit-class infection where you do not trust the running system to clean itself, an inherited machine with an unknown history, or a desire to rebuild the partition table and reclaim OEM partitions. In both cases, back up first, sign out of everything you can, and remember the honest limit — if the threat lives in firmware, neither option saves you; that is a different problem and a different machine.

Questions and Answers

Read next