The Windows installation USB is still in my desk drawer. I made it in 2021 during a panicked reinstall that took an entire Saturday. It has not been needed since. The reason is a handful of built-in repair tools that handle the cases that would have pushed me to reinstall back then. None of them are magic, but together they cover most of the strange behaviors Windows can develop.
Why reinstall used to be the default
A Windows reinstall takes hours once you factor in the installation itself, the post-install updates that download the same version you already had, the driver hunt, the application reinstalls, and the slow process of getting the desktop back to a state that does not actively annoy me. For most of the last decade, that was the rational response to a Windows PC that was acting up.
It is also the wrong response in most cases. Reinstalling Windows does not fix hardware problems. It does not fix a bad driver you are about to reinstall. It does not fix a corrupt user profile if you bring the profile forward. The time spent reinstalling is wasted in exactly the situations where the user thinks it will help. The four tools below cover the most common scenarios where a reinstall feels inevitable but is not.
SFC and DISM: repairing corrupted system files
Windows relies on thousands of system files to keep itself working. When some of those files become corrupted (from a bad shutdown, a failing disk, a botched update, or a malware cleanup that went sideways), the result is the kind of vague brokenness that makes people reach for the reinstall USB.
Two built-in tools repair those files, and they work as a pair. SFC (System File Checker, a tool that scans protected Windows system files and replaces corrupted ones with cached copies) handles the file-level repairs. DISM (Deployment Image Servicing and Management, a tool that repairs the Windows component store, which is the cache of installation files SFC uses as its source) handles the underlying component store SFC pulls from. If you run SFC against a corrupted component store, SFC reports corruption it cannot fix because its source files are also bad. Running DISM first gives SFC a clean baseline to work from.
To use them, open Windows Terminal or Command Prompt as an administrator (right-click the Start button, choose Terminal (Admin) or Command Prompt (Admin)). Run DISM first:
DISM /Online /Cleanup-Image /RestoreHealth
DISM downloads replacement files from Windows Update when needed, which can take 10-30 minutes on a slow connection. When DISM finishes, run SFC:
sfc /scannow
SFC scans the protected system files and replaces corrupted ones with the cached copies. Another 10-20 minutes is typical. If both finish without errors, the file corruption that was causing your symptoms is usually gone.
This is the single highest-yield repair on Windows. It fixes more weird behaviors than anything else in the toolkit, and it is the first thing to try before anything else on this list.
System Restore: rolling back without losing personal files
Sometimes a Windows PC starts misbehaving right after a configuration change, an update, or a driver install. The fix is to undo the change, and Windows has had a built-in undo for this since the XP days. It is called System Restore, and it works by capturing a snapshot of important system files, drivers, registry settings, and installed applications at specific points in time. If something breaks, you restore from an earlier snapshot.
System Restore is turned off by default on some Windows installations and turned on by default on others. Check by searching “Create a restore point” in the Windows search bar, opening the System Properties dialog that appears, and looking at the protection status for your system drive. If it says Off, turn it on. The cost is a few gigabytes of disk space for the restore points, and the benefit is being able to undo a bad change without losing your files.
The standard usage: open the same Create a restore point dialog, click System Restore, follow the prompts, and pick a restore point from before the problem started. Windows reboots, applies the older configuration, and your personal files stay where they were. It is faster than a reinstall and does not require reinstalling applications.
The two real limitations of System Restore. First, it only helps if a usable restore point exists. Windows creates restore points automatically before major updates and some driver installs, but not before every change. Manually creating a restore point before risky configuration changes is a habit worth building. Second, System Restore is not a full backup. It does not save your personal files, your application data, or your installed applications. If a hardware failure takes out your disk, System Restore does not help. Pair it with a real backup (a cloud backup, an external drive, or both) if you do not have one.
Rolling back a bad driver or update
Drivers and Windows updates are both candidates for “this thing worked yesterday and does not work today” debugging. Both have a built-in rollback path.
Driver rollback: open Device Manager, find the device with the bad driver, open its Properties, switch to the Driver tab, and click Roll Back Driver if the option is available. The button is grayed out if no previous driver version is on the system, which happens for newly installed devices. Rolling back takes 30 seconds and a reboot, and it is the fastest fix for a device that started misbehaving right after a driver update.
Update rollback: open Settings, then Windows Update, then Update history, then Uninstall updates. Pick the update that matches the date the problem started, and uninstall it. Some updates cannot be uninstalled (Microsoft marks certain security updates as non-removable). For the ones that can, uninstall and reboot, and the offending update is gone.
Both rollbacks are easier than reinstalling, and both address the case where a recent change is the cause of the problem. The catch is that you have to identify the change. If you do not know when the problem started or what changed, the rollback path is harder to use. The pattern that works: if a Windows PC was working fine a week ago and is broken today, the change is somewhere in the last week. Check Windows Update history and Device Manager for changes in that window.
Trade-offs
The four tools above cover most of what a Windows reinstall used to handle. The cases they do not cover are the cases where reinstall is the right answer.
Hardware failures do not get fixed by SFC. A failing disk that is dropping bits, a flaky RAM stick, or a dying power supply will produce symptoms that look like software corruption. SFC can repair the corrupted files those failures create, but the failures keep happening. Run SFC once and the file corruption clears up. The hardware failure causes new file corruption a week later. The fix is the hardware, not the repair tools.
User profile corruption is a partial case. SFC fixes system files, not user profile files. If the problem is a corrupted user profile (symptoms: the same user account behaves strangely while other accounts work fine), the fix is to create a new user profile and migrate the data over, not to run SFC. That is a smaller operation than a full reinstall, but it is more work than the other repairs on this list.
Malware cleanup is another partial case. SFC can repair files a malware infection has modified, but it does not remove the malware itself. Run a real antivirus scan (Windows Defender is fine for most cases) before running SFC, so the repair tools are not running against a system that is actively being damaged.
The time costs in practice. SFC plus DISM is 20-50 minutes. System Restore is 15-30 minutes including the reboot. Driver or update rollback is 5-10 minutes. Reinstalling Windows is 4-8 hours. The math favors the repair tools any time you can use them.
What I would tell past me
Four habits from this article are worth keeping:
- Run DISM and SFC as a pair, with DISM first. Running just SFC against a broken component store wastes 20 minutes and reports corruption you cannot fix. Running DISM first gives SFC a clean source to draw from.
- Create a manual restore point before risky changes. Updating a graphics driver manually, installing a new kernel-level application, or tweaking a registry setting you do not fully understand all qualify. The 30 seconds to create a restore point beats the 30 minutes to fix what you broke.
- Pair these tools with a real backup. System Restore covers configuration rollbacks. It does not cover disk failure, ransomware, or accidental file deletion. None of the repair tools above help if the disk dies. A real backup (cloud plus an external drive, or a NAS with snapshots) is the layer underneath these tools.
- Stop reinstalling Windows as a first response. Reinstall is the right answer in maybe 10% of the cases it gets used for. The repair tools above handle the other 90%, and they handle it in an evening instead of a weekend.
The Windows installation USB stays in the drawer. It has not earned its space back since I started using these repair tools as the first response instead of the last resort.