Windows recovery,
screen by screen.
Ten blue screens that look interchangeable and rewind completely different things. Thirteen entries, ordered from the one that touches your settings to the one that touches your disk.
How to tell which thing you are actually rewinding.
Recovery options differ by what they touch, not by how alarming their screen looks.
Every one of these screens says it will fix your PC, and they operate on four different objects: the registry and installed programs, the system files, the boot configuration, or your own documents. A machine that will not start and a machine that lost a file are different problems that share a colour.
The habit worth acquiring is to name the object before choosing the option. Once you know which of those four you are about to rewrite, half of these screens turn out to be irrelevant, and the other half tell you exactly what to check first.
- Settings, files, boot, or data. System Restore does settings and programs. Previous Versions does files. Startup Repair does boot. Nothing does data that was never copied.
- Read the scan list. The restore wizard names the programs it will remove. That list is the warning, and it is the only one you get before the reboot.
- Check the safety net while it still works. reagentc /info answers whether the recovery environment exists, in the one moment when the answer is useful.
- Nothing here is a backup. Every option in this family needs a copy that already exists somewhere else, and none of them creates one for you.
The thirteen things a blue screen can actually do.
Ordered from the least invasive change of settings to the ones that rewrite a disk.
System Restore — the machine settings it rolls back, and the files it will not
- What it is
- A rollback of the system state to a saved snapshot: the registry hives, installed programs and their services, drivers, system files, Windows Update metadata and some script-based settings. It runs offline through a VSS snapshot and reboots twice.
- What changes
- Everything installed after the restore point is removed, including the programs you may have installed the same morning, and everything installed before it stays. Documents, photos, mail and desktop files are not touched — the feature deliberately excludes the user profile data. The dialog lists the programs it will remove and, since Windows 10, also the programs it will reinstall, because a program installed before the point and then uninstalled comes back.
- Risk
- Expensive The surprise is not the rollback itself, it is that a licensed application or a database engine you installed last week disappears and the data files it left behind arrive with no software able to read them. Read the scan list before you press Next.
Restore points are not created for you as often as you think
- What it is
- A restore point is generated by Windows before a feature update, before a driver or Windows Update installation, and when an application asks for one during its install. It is not a schedule. On a clean Windows 11 client, System Protection is switched off for the system drive until someone turns it on, which means there is often exactly one point: the day of the last update.
- What changes
- Enabling protection on the drive (sysdm.cpl → System Protection → Configure) starts a rolling allocation of disk space; when the pool fills, the oldest points are deleted. Creating a point by hand is available in the same dialog and takes seconds. Turning protection off does not delete existing points, but disabling it while a rollback is in progress leaves nothing to roll back to.
- Risk
- Careful Discovering this after the failure is the expensive version. Checking it takes one look: if the Create button is greyed and the drive shows No, there is nothing to restore to.
Shadow copies and Previous Versions — the same engine, a different question
- What it is
- The Volume Shadow Copy Service (VSS) is the snapshot machinery underneath everything. A restore point adds the registry and program state to a snapshot; a plain shadow copy of a volume is what gives you the Previous Versions tab on a folder, and it is also what backup software uses to read open files.
- What changes
- The tab shows versions only for files that were open on the volume when a snapshot existed, and it is silent about why a date is missing. Storage for those copies lives on the same volume and is bounded by its own limit, which is why an old version of a large file can be listed and then fail to restore. The state of the subsystem is visible with vssadmin list writers, list shadows and list shadowstorage from an elevated prompt.
- Risk
- Reversible A failed writer is a genuine fault, but it is a fault for backups, not for your documents. Read the writer error before you start reinstalling Windows.
WinRE — the recovery environment, where it lives, and how to be sure it is there
- What it is
- A compact Windows image that boots independently of your installation, holding Startup Repair, the command prompt, Safe Mode options, Uninstall Updates, System Restore, System Image Recovery and Reset this PC. It normally sits in a hidden recovery partition of a few hundred megabytes, or in Windows\\Recovery on machines that have no room for a partition.
- What changes
- Whether yours exists is a fact you can query: reagentc /info reports the state and the path, and reagentc /enable puts it back when a disk tool or a shrink removed the reference. If the partition was deleted to gain space, the recovery options in the Start menu still open but they fail with a message about the environment being unavailable, and the only route left is installation media.
- Risk
- Expensive Losing WinRE is discovered at the worst possible moment, when the machine will not boot. Run reagentc /info while everything works; it costs one line and tells you whether you have a safety net at all.
Getting into recovery when Windows will not start
- What it is
- Four doors: the Shift key held while you click Restart from the sign-in screen or the Start menu; three consecutive failed boots, which makes Windows start WinRE by itself; a bootable USB with the same Windows version; and from inside a working system, the Recovery page in Settings or shutdown /r /o.
- What changes
- The automatic route is the one people mistake for a fault: a machine that fails to boot three times lands in the recovery environment without being asked, and the blue screen that appears is not a crash screen but the beginning of that path. Interrupting boot with the power button repeatedly is how that trigger gets created on purpose, and it also risks writing to a half-finished update.
- Risk
- Careful Forcing power off during an update, rather than during a boot attempt, is how a repairable system becomes a rebuild.
Safe Mode and its three variants
- What it is
- A boot with a minimal driver set and no third-party services. Three flavours: Safe Mode alone, Safe Mode with Networking, and Safe Mode with Command Prompt. Servers add a Directory Services Restore Mode; a domain controller will not boot into anything else if it is in that state.
- What changes
- What Safe Mode proves is the negative: if the problem disappears there, it was caused by a driver or a service that does not load. What it does not prove is that your data is safe, because graphics and audio are degraded on purpose, some applications refuse to start, and disk operations are the same as always. msconfig's Boot tab sets the mode persistently, which is how machines get stuck booting into a minimal environment until someone clears the checkbox.
- Risk
- Careful The classic trap is leaving /safeboot set in the boot configuration and concluding the machine is broken. bcdedit /deletevalue {current} safeboot, or unticking the box, ends it.
Startup Repair — what it actually tries, and where it says so
- What it is
- An automated pass over the boot configuration data, the system files, the registry hives and recent updates, run from WinRE. It writes a report to the log files under Windows\\System32\\LogFiles\\Srt on the installed system, and the interesting detail is there rather than on screen.
- What changes
- It rebuilds the BCD store, replaces a missing or corrupt boot manager, rolls back a recent update that broke booting, and can run a check of the volume. It cannot fix a deleted user profile, a driver that loads and then hangs, or a disk with failing sectors, and when it cannot help it produces the screen that says so and offers five options — among them the command prompt, which is where the real work usually starts.
- Risk
- Reversible Repeating Startup Repair until it changes something is a waste of an afternoon. Read the result once, then choose the specific tool.
Reset this PC — the two choices, and the third that hides inside each
- What it is
- A reinstall of Windows that keeps or removes your account data. Keep my files leaves documents alone and removes the apps you installed; Remove everything wipes user data from the drive. Both then pick between Cloud download, which fetches a fresh copy of the same version, and Local reinstall, which uses the recovery image already on the machine.
- What changes
- A keep-my-files reset does not clear a second user account's saved passwords from the point of view of a browser that syncs, does not remove malware that lives outside the profile, and does not restore programs you licensed — the licences stay where the vendor keeps them, not on the disk. Remove everything with the clean-data option writes over free space, which is the slow path and the one meant for selling the machine; without it, deleted files remain recoverable.
- Risk
- Expensive Reset is not a backup strategy. It ends up reinstalling the OS, and the only thing that brings your work back is a copy that exists somewhere else.
Uninstalling an update, and the ten-day window on a feature update
- What it is
- Two different mechanisms with similar names. A quality update is removed from Update history → Uninstall updates, one at a time, and it can be removed again later because Windows hides it. A large version change is rolled back from Recovery → Previous version of Windows, which restores the whole previous installation from the Windows.old copy.
- What changes
- The rollback option expires: Windows removes the copy that makes it possible after a fixed period of days, and disk cleanup can remove it earlier if you run it with the system-files option. Once Windows.old is gone, going back means a clean reinstall. Uninstalling one quality update can leave its prerequisites in place, so the pair that caused the failure sometimes has to come out together.
- Risk
- Careful The irreversible action here is deleting the old installation to reclaim space while the problem you rolled back for is still in the new one.
The command prompt in recovery — the five commands worth knowing, and the one to fear
- What it is
- WinRE gives you a full administrative prompt against an operating system that is not running. That is the correct place for sfc /scannow with /offbootdir and /offwindir pointing at the offline installation, for DISM /Online /Cleanup-Image /RestoreHealth when the component store is damaged, for bootrec /fixboot and /rebuildbcd when the boot files are the problem, and for chkdsk when the volume reports corruption.
- What changes
- Offline servicing repairs files that the running system cannot replace, which is why the running system's sfc pass sometimes reports it fixed things it did not fix. diskpart is the dangerous one: it can delete a partition that holds the only copy of your data, it will not warn you, and its commands take effect immediately. A BitLocker-protected volume also shows as raw or unreadable in that environment until it is unlocked, which looks identical to a destroyed disk and is not.
- Risk
- Expensive Reading a locked drive as a dead drive, then repartitioning it, is the one recovery mistake that cannot be undone from the same screen.
The recovery drive and the system image, which are not the same object
- What it is
- A recovery drive is removable media that boots WinRE for you. The wizard has a checkbox to back up system files, and that is what changes the product: without it you get the tools but no image; with it you get the recovery environment plus a full image of the system drive. The older Backup and Restore panel is where a scheduled image lives, and its name is still the Windows 7 one.
- What changes
- System Image Recovery restores the disk exactly as it was, which includes any damage that was present, and it refuses if the target disk is smaller than the source. An image is the only consumer mechanism that returns programs, settings and files together; a restore point returns settings only, and Reset returns Windows only.
- Risk
- Reversible Creating the drive while the machine still boots is the cheapest insurance in this family, and it is the only one that survives a dead system disk.
File History and version history — what recovers a document, and what does not
- What it is
- File History copies changed files from the libraries, desktop and contacts to a second location on a schedule, keeping older versions. OneDrive does the equivalent inside its own storage and exposes it as version history on the file. Neither of them is a restore point: they never touch the registry, and a restore point never touches your documents.
- What changes
- File History stops quietly when its destination drive is disconnected, and the settings page keeps showing the last run time rather than an error, which is how people discover months later that nothing has been copied since the external disk left. A file deleted from the library and emptied from the recycle bin is gone from history too, because history tracks versions of files that exist.
- Risk
- Careful The distinction that matters when it is already late: restore fixes the machine, version history fixes the document, and nothing in Windows fixes both from one button.
What recovery in Windows cannot do, stated plainly
- What it is
- There are four things this whole family of screens will not give back, and the reason is that none of them is a backup: files encrypted by ransomware (the snapshot is encrypted too, because VSS copies the volume as it is), files deleted and overwritten, data on a disk with failing sectors, and settings from a Windows installation that was reinstalled over.
- What changes
- The folder that used to hold automatic registry backups, Windows\\System32\\config\\RegBack, is empty on modern builds: Windows stopped refreshing it, so the widely copied offline trick of restoring those five files no longer recovers anything on a current machine. Treating a restore point as the reason not to keep copies is the failure mode these screens were never designed to cover.
- Risk
- Expensive If the loss you are facing is user data, stop here and go to the copy that exists elsewhere. Every further action on a failing disk reduces what can still be read from it.
Adjacent screens.
Recovery sits between the updates that trigger it and the devices that fail first.
Windows Update, decoded
What pausing really stops, which updates can be uninstalled, and where the rollback window closes.
Read the reference device manager · error codesDriver errors, translated
The codes that send a machine into Safe Mode, and the difference between rolling back and reinstalling.
Read the reference every app · dialog verbsWhat this dialog box is asking
Keep changes against Revert, and the prompts that decide whether a repair commits or stops.
Read the reference the productToolTip AI
One application that explains, translates and reads aloud whatever control is under your pointer — including the option you have to decide in ninety seconds.
Read about the appRecovery screens are read under pressure, which is the worst condition there is.
Nobody learns these options before they need them, and the moment of need is a machine that will not start. That is exactly why the useful thing is done days earlier: one look at the drive showing whether protection is on, one line reporting whether the recovery environment exists, and one copy that is not on the same disk.
Get ToolTip AI on Microsoft Store