The logo spins, the desktop never arrives, and the first advice you see is Reset this PC. That is the wrong first move. A reset can keep your documents and still wipe the apps, drivers, and settings you use every day. How to Windows repair starts by matching the symptom to the least destructive tool, then ruling out a dead drive before anyone talks about reinstalling.
Pick the Least Destructive Repair First
Jumping straight to reset throws away a working environment to fix a boot problem that a smaller tool might already cover. Microsoft documents the Windows Recovery Environment as the platform that starts on its own after repeated failed boots on current Windows 10 and Windows 11. WinRE is not one button. It offers Startup Repair, System Restore, Startup Settings, Command Prompt, System Image Recovery, and Reset this PC.
The order is the repair. Non-destructive steps come first. Reset comes last, after those tools have failed and you know why.
Startup Repair targets corrupted system files and damaged boot-configuration data. System Restore reverses system changes and is built to leave personal files in place. You can open the environment from Advanced startup, including by holding Shift while you select Restart on the sign-in screen.
| Tool | Use it when | Personal files | Main risk |
| Startup Repair | Windows won't boot and boot files look damaged | Kept | Cannot fix hardware failures |
| System Restore | A driver, app or settings change broke Windows | Kept | Removes apps and drivers installed after the restore point |
| Uninstall Updates | Trouble started right after a Windows update | Kept | Security fixes are removed until the update is reinstalled |
| SFC and DISM | Windows starts but system files are corrupted | Kept | Takes several minutes and needs a healthy repair source |
| System Image Recovery | A saved image of a working system exists | Replaced by image contents | Changes made after the image was created are lost |
Match the symptom, then stop
A black screen after a driver install is a restore-point problem, not a reinstall. A loop that started the minute Windows Update finished is an uninstall-updates problem. A PC that reaches the desktop and then throws file-corruption errors is an SFC and DISM problem. An image restore only makes sense when you already captured a working system, because everything newer than that image is gone.
Practical rule: If you cannot name the change that broke Windows, start with Startup Repair, not reset.
I would rather spend twenty minutes on the wrong small tool than an evening rebuilding licenses after a reset that was never required.
Back Up and Reach Recovery Before Changing Anything
Say the laptop failed an update overnight. It now asks for a BitLocker recovery key, and last weekend's photos never finished syncing. Fix the files you can still reach before you change the system.
Finish this checklist before step one of any repair:
- BitLocker recovery key: Save the 48-digit key from the Microsoft account or the printed key file. Without it, an encrypted drive stays locked.
- Browser sync: Confirm Chrome, Edge, or Firefox shows sync as current, not paused.
- Cloud folders: Open OneDrive or the other cloud client and wait until every folder says it is fully synced.
- Password manager: Export the vault to a USB stick you control, then eject it.
- Email archives: Copy PST or OST files if mail lives only on this PC.
- Program list and licenses: Write down installed apps and the keys you will need to reinstall them.
- VPN and work clients: Note server addresses and certificate names before settings disappear.
- OEM recovery partition: Check whether the maker left a recovery partition. If it is missing, you will need USB media later.
Three ways into recovery
Windows drops into WinRE by itself after repeated failed boots. If you can still reach the sign-in screen, hold Shift, select Restart, then choose Troubleshoot.
If no recovery screen appears at all, use a second PC and the Microsoft Media Creation Tool. Match the installed Windows version, language, and architecture, boot the USB, and choose Repair your computer. Firmware that refuses the USB is a separate problem. Secure Boot checks explain what the firmware is testing before you disable protections at random.
A short walkthrough of the recovery menu helps if the labels on your screen differ slightly from a written list.
You should now have the BitLocker key, copies of photos and email, the program list, and one working way into recovery. Do not start a repair until those four things are true.
Run Startup Repair and System Restore Step by Step
The PC that dies on the spinning dots, then lands you in recovery, is a boot problem until proven otherwise. Startup Repair is the first tool to run because it only touches boot files and disk metadata. System Restore comes next, and only for a point older than the change that broke the machine. A reset is still the wrong move.
- From Advanced options, open Startup Repair. It is an automated check for common boot failures, such as damaged or deleted boot files and disk metadata, and it repairs them when it can. A finished run does not guarantee a fix. Treat it as a test: if Windows boots, stop. If it does not, the boot path was not the whole problem.
- Let the tool finish. It may restart the PC more than once. Pulling power mid-run leaves the boot files in a worse state than the one you started with.
- If Windows still will not start, return to Advanced options and choose System Restore. Skip this only when no restore point exists. Do not jump to a reset because the first tool came back empty.
- Pick a point dated before the failure, then run Scan for affected programs. The rollback returns system files, registry settings, and installed programs to that moment. Documents and photos stay. The common slip is choosing a point from after the bad driver, which rolls back nothing useful.
- Confirm and wait. The PC restarts, and the rollback takes several minutes. Do not force a shutdown because the screen looks idle.
- After you sign in, open Documents and Pictures, then reinstall any app the scan said would be removed.
When there is no restore point
No points usually means System Protection was off. If the break followed a Windows update, use Uninstall Updates. If Windows can start and the symptom looks like damaged system files rather than a bad boot, use the file-repair commands instead of wiping the install.
A disk that clicks, disappears from the restore list, or fails the same way after a clean boot file repair is a hardware problem. Restoring or resetting that drive copies the failure onto whatever you write next.
Safe Mode and a bad update
If the sign-in screen appears but the desktop misbehaves, open Startup Settings and press 4 for Safe Mode. Windows starts with a minimal driver set, so you can remove the recent driver from Device Manager or the bad app from Settings. That keeps your files and the rest of the installed software.
When the failure began the moment an update finished, I would use Uninstall Updates under Advanced options instead of a broad restore. That removes the quality or feature update without rolling back unrelated apps. Reinstall the security update later, once the PC stays up through a normal boot. Leaving it uninstalled is a temporary trade, not the end state.
A restore point from yesterday beats a reset from today, but only if that point is older than the change that broke the PC.
Repair Corrupted System Files With SFC and DISM
DISM repairs the component store. SFC uses that store to replace protected files. Run them backward and SFC has nothing healthy to copy from.
Microsoft's repair guidance puts Deployment Image Servicing and Management first. From an administrator Command Prompt, the online command is DISM.exe /Online /Cleanup-image /Restorehealth. DISM can take several minutes to start and several more to finish. Leave the window open. Closing it does not cancel cleanly.
When DISM reports success, run sfc /scannow. It shows progress and ends with the message "Verification 100% complete." If it found corrupt files and could not fix them, run DISM again, then SFC again. Open C:\Windows\Logs\CBS\CBS.log and search for the file names that failed. Those names tell you whether you are looking at a Windows component or a third-party driver that neither tool will touch.
Commands by situation
| Scenario | Command | Note |
| Windows starts, system files suspect | DISM.exe /Online /Cleanup-image /Restorehealth, then sfc /scannow | Run DISM first; it supplies the source SFC uses |
| Offline install, repair from WinRE Command Prompt | DISM /image:D:\ /cleanup-image /restorehealth | Replace D:\ with the drive letter that holds the Windows folder |
| Offline system file scan | sfc /scannow /offbootdir=D:\ /offwindir=D:\windows | Confirm the drive letter with BCDEdit first |
| DISM reports missing source files | DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess | Source edition, language, architecture and build must match the installed Windows |
Offline repair from WinRE
Inside recovery, the Windows volume is often not C:. Run bcdedit and read the osdevice line before you type a path. The classic mistake is /Online while you are booted into recovery: that command services the recovery environment, not the installed system.
If DISM says the source is missing, point it at a matching installation image with /Source and /LimitAccess. Edition, language, architecture, and build have to match. A Windows 11 image will not repair a Windows 10 store, and a different language pack will not either.
These tools replace files. They do not resurrect a failing SSD, and they do not rebuild a boot menu that Startup Repair already gave up on. If the same errors return after a clean SFC pass, stop repeating the commands and look at the disk.
Fix Repairs That Fail or Cannot Reach Recovery
The failure I see most often is a boot loop that started right after Windows Update. On Windows 11, Quick Machine Recovery can pull a Microsoft-provided remediation through Windows Update once the device is in WinRE, then apply it automatically. That path needs a reliable internet connection. A cafe hotspot that drops every few minutes is not reliable.
Without a network, use Uninstall Updates and System Restore from WinRE. If a servicing action is stuck pending, revert it with offline DISM against the actual Windows volume, using the drive letter you already confirmed. SFC and DISM are the wrong first move when the trigger is a bad update, a broken boot configuration, a dead drive, or a recovery image you cannot reach.
What each failure is telling you
| Failure | Likely cause | Next move |
| Boot loop right after a Windows update | Pending or faulty update | Uninstall Updates, or revert the pending action with DISM offline |
| Startup Repair finishes but Windows still will not boot | Damaged boot configuration | Run bootrec /rebuildbcd, then try System Restore |
| Recovery environment will not load | Damaged recovery partition | Create installation media on another PC and boot from USB |
| SSD missing from firmware or setup | Drive, cable or controller failure | Stop software repairs and check hardware or vendor diagnostics |
| Quick Machine Recovery stalls | No reliable internet connection | Use Uninstall Updates or a local reinstall instead |
| Cloud reinstall download stalls | Unstable or slow internet connection | Switch to a local reinstall if recovery files are still on the PC |
If Startup Repair completes and Windows still will not boot, open the WinRE Command Prompt and run bootrec /rebuildbcd. That rebuilds the boot configuration data. Run Startup Repair once more after it. Only then consider a reset.
A recovery partition that will not load is a media problem. Build installation media on another computer and boot the USB. A cloud reinstall that stalls is a bandwidth problem. Switch to a local reinstall when the recovery files are still on the disk. Cloud rebuild controls matter here because a cloud path also depends on Wi-Fi being available from recovery, which many desktops do not have.
If the SSD does not appear in firmware or in Windows Setup, stop. Cable, drive, and controller come before another software pass.
Signs the problem is hardware: the drive vanishes between reboots, Setup shows no disks, SMART warnings appeared before the crash, or the same file errors return on a disk that clicks or disappears under load. No repair command fixes a drive the firmware cannot see.
Reset or Reinstall Only When Repairs Fail
Keep my files is not a gentle repair of your working PC. Microsoft's reset documentation says that option preserves personal files while it removes installed applications and resets settings. WinRE still has Startup Repair, System Restore, update uninstall, and Command Prompt. Reset is the step you take after those have failed and you have an inventory of what you must put back.
What does not survive Keep my files: application licenses, custom drivers, VPN clients, game launchers, encryption settings, and locally stored app data. Your photos can be fine while Outlook profiles, Steam libraries, and VPN certificates are gone.
| Option | Personal files | Apps and settings | Internet needed |
| Reset this PC, Keep my files | Kept | Apps removed, settings reset | Optional, for local reinstall |
| Reset this PC, Remove everything | Erased | Erased | Optional |
| Cloud download reinstall | Depends on what you keep | Fresh Windows install | Yes, a reliable connection |
| Local reinstall | Depends on what you keep | Fresh Windows install | No, uses recovery files already on the PC |
| Clean install from USB | Erased when the drive is formatted | Fresh Windows install | No, uses media from another PC |
Choose the wipe on purpose
Before you reset, go back through the backup checklist and add one step: export the installed-program list so you can reinstall each app afterward. Remove everything is for a PC you are selling or recycling, because it erases the drive. A clean install from USB is the route when the OEM recovery partition is missing or damaged. Build that media on another PC.
Edition support also changes which install is worth keeping. Windows 11 23H2 end-of-life dates are worth checking before you reinstall an old ISO that will be out of support the week you finish.
After the new Windows is up, reinstall apps from the list, open the backed-up files, and run Windows Update. If the same fault returns on a clean system, treat it as a probable hardware problem and run the PC maker's diagnostic. Another reset will not change a failing drive.
NeoTeo publishes practical Windows recovery walkthroughs, security explainers, and PC repair guides you can follow without a support contract. If the next boot failure shows up on a different machine, the same symptom-first order still applies. Visit NeoTeo for more hands-on repair and Windows coverage.
