Computer Won’t Boot but the Drive May Still Be Healthy
A failed Windows, macOS or Linux boot is not automatically a storage failure; preserve the data before using reinstall, reset or repair options that can write to the disk.
Before attempting repair, determine whether the storage source is identified consistently, reports the expected capacity and can be read without severe errors, stalls or disconnects. If not, treat acquisition as the first problem.
Boot failure is a symptom above several layers
A computer can fail before the operating system loads because of firmware settings, bootloader damage, an interrupted update, file-system corruption, encryption state, missing system files or actual storage hardware failure. The key recovery question is whether the storage device itself is identified correctly and can be read stably—not whether the OS reaches the desktop.
Separate system recovery from data recovery
If the files matter more than restoring the installation, do not begin with Reset this PC, reinstall macOS/Windows, partition repair or automated “fix boot” tools. Those procedures are intended to restore bootability and may write extensively to the same storage that contains the only copy of the data. Data recovery can often be done without making the original OS boot again.
What to observe safely
Check whether firmware sees the drive with the correct model/capacity and whether a trusted read-only or external environment can enumerate it without severe errors. Note BitLocker, FileVault, LUKS or other encryption credentials before changing hardware or firmware settings. If the drive disappears, reports the wrong size, clicks, or stalls under reads, treat it as a storage-access problem rather than an OS problem.
Recovery path for a stable drive
For a stable device, image or otherwise preserve it, then mount or recover the data from the copy. A damaged bootloader does not require file carving if the file system itself remains intact. If the file system is corrupted, use file-system-aware recovery. Only after the data is secure should repair, reinstall or reset be considered.
When the drive is not healthy
If boot failure coincides with SMART warnings, I/O errors, timeouts or repeated disconnects, repeated boot attempts can generate heavy random reads and writes. Move to controlled acquisition or professional diagnosis. The fact that the machine “almost boots” is not proof that continued boot attempts are safe.
Do not save recovered files, install software, create partitions, format, initialize or run write-capable repair tools on the only copy of the affected data. When practical, work from a verified image or another preserved copy.
Related reading: Drive Not Detected · Filesystem Corruption · Os Reinstall Overwrite · Data Recovery Workflow · Understanding Storage Layers Before Recovery · Recovery Copies.
This page describes the general situation, not a guaranteed fix for a specific case. If the source is unstable or the data is irreplaceable, consider a professional evaluation before further attempts.