Recovery is planned before the failure, not after
Every recovery option depends on something prepared in advance. A restore point must have been created before the fault. A backup must exist before the disk failed. Recovery media must have been written while the machine still worked.
That is the real content of this chapter: the techniques are straightforward, and the examinable insight is that none of them helps a person who did nothing beforehand.
| Tool | Recovers from | Prepared in advance? |
|---|---|---|
| System restore point | a bad update or driver | yes — a snapshot of settings |
| File backup | deleted or corrupted files | yes — a copy elsewhere |
| System image | total disk failure | yes — a full copy of the drive |
| Recovery media | a machine that will not boot | yes — a bootable USB |
| Safe mode | a faulty driver or startup program | no — built into the OS |
| Reset / reinstall | irrecoverable corruption | no, but it erases your data |
Restore points, images and backups are three different things
Students routinely treat these as interchangeable, and the exam distinguishes them sharply.
A system restore point saves system files, settings and installed programs — not your documents. It undoes a bad driver or update; it will not bring back a deleted essay. A file backup copies your documents but not the operating system; restoring one onto a dead machine still leaves you with no machine. A system image is a complete copy of the whole drive, which restores everything exactly but is large and quickly out of date.
A sensible strategy uses more than one: frequent file backups for the documents that change daily, plus an occasional system image so a failed disk can be replaced without reinstalling everything.
What a restore point will not do
Restoring to a point from last Tuesday does not recover files deleted since then, and it does not remove a virus that has infected your documents. It rolls back system configuration only. Students frequently offer it as the answer to data loss, and it is the wrong tool for that job.
Safe mode and startup repair
When a machine will not start normally, safe mode loads the operating system with only the essential drivers and no startup programs. If the fault disappears in safe mode, it was caused by one of the things safe mode left out — a driver, or a program launching at startup — which narrows the search enormously.
From there the process is elimination: disable startup items, re-enable them in groups, and find the one that reintroduces the fault. If the machine will not reach safe mode either, the problem is deeper and recovery media is needed — a bootable USB that starts an independent copy of the OS from which the disk can be repaired or data rescued.
A computer shows a blue error screen a few seconds after logging in, every time. Describe how to diagnose it.
- Note the error code or message shown, then boot into safe mode.The code often names the failing driver directly, and safe mode loads almost none of them.
- If safe mode is stable, the fault lies in a driver or startup program, not in the core system.This single test rules out most of the possibilities in one step.
- Recall what changed recently — a new device, a driver update, newly installed software.A fault that appeared on Tuesday almost always follows something that happened on Monday.
- Roll back or uninstall the suspect item, or use a system restore point from before the change.This is the situation a restore point is actually designed for.
- If safe mode also fails, boot from recovery media and run startup repair or a disk check.A fault present even in safe mode points at the disk, the file system or the memory.
Test in safe mode first: stable there means a driver or startup program, and a restore point from before the change is the fix.
Advanced maintenance
Beyond recovery, the syllabus expects the routine tasks that keep a system healthy and the reasons for them.
Disk clean-up removes temporary files and caches that accumulate steadily. Defragmentation reassembles files scattered across a mechanical hard disk so the head moves less — but it should not be run on an SSD, which has no moving parts and whose cells wear out with each write. Updates close security holes as well as fixing faults. Disk health monitoring reports the drive's own error counters, often warning of failure days before it happens.
Why defragmenting an SSD is harmful
On a hard disk, a fragmented file makes the head travel, which costs time. An SSD reaches any location equally fast, so there is nothing to gain — and every write consumes a little of the limited number a flash cell can take. Defragmenting an SSD performs millions of pointless writes and shortens its life. Modern operating systems refuse to do it, and knowing why is worth a mark.
Before you leave this chapter
- Every recovery option depends on preparation done before the failure.
- Restore point = system settings only. Backup = your files only. Image = everything.
- Safe mode loads minimal drivers; if the fault vanishes there, it is a driver or startup program.
- Recovery media must be created while the machine still works.
- Never defragment an SSD — there is nothing to gain and it wears the drive.