Data Recovery Case File · Second Fixes & Trade Handoffs · A Reinstall Is a Write

The Fix Was Attempted Before the Data Was Discussed

His enquiry describes a sequence in which one step was consequential and nobody flagged it. A drive that failed to boot: "took the PC to a repair shop who confirmed the system on the drive was corrupt. They tried to reload the operating system, but found after further diagnostics that the drive was corrupt. The drive has documents and pictures I would like." Reinstalling an operating system writes tens of gigabytes to a drive — and it happened on a drive holding documents and photographs, before anybody established whether those mattered.

The decode: what happened in what order, and why it matters

Why the shop's first conclusion was reasonable: a machine that will not boot with an apparently intact drive very often has a damaged operating system, and reinstalling is the standard remedy. It fixes a great many machines and it is what a repair shop is for. The assumption underneath it is that the hardware works, and that assumption is usually correct.

What the attempt actually did: an installation writes a new filesystem and tens of gigabytes of system files across the drive, working outward from the start of available space. Whether or not it completed, it wrote — and it wrote into space that held documents and photographs, because a system drive holds both.

Why the order is the issue rather than the action: nobody did anything incompetent. But the customer's data was on that drive throughout, and the conversation about whether it mattered — and whether it should be secured before anything was attempted — appears not to have happened. A reinstall is reversible for a machine and irreversible for the files underneath it. That distinction belongs to the customer, and it is worth asking for explicitly next time: before you try anything, is there data on here I need?

What the second finding tells us: that the drive is faulty at device level, which explains why the reinstall did not resolve anything. The system was probably never the problem — a failing drive produces exactly the symptoms that look like a corrupt installation.

The two questions worth answering now: how far the installation got, and whether it completed. A reinstall that failed early wrote comparatively little; one that completed wrote a full system and then began updating. That figure defines what remains, and the shop can say.

Why the outlook is not as bad as it sounds: an installation writes a bounded amount from the beginning of the free space, so on a drive substantially larger than that footprint, everything beyond it was never touched. Files recovered from that region come back by carving — identified by their own structure, organised by type and date rather than by folder.

What the device-level fault changes: a drive that cannot be reached needs its controller addressed before any of this is readable, which is done through vendor technological modes rather than any software approach.

On the bench

The extent and completion state of the installation attempt were established before assessment — an installation writing a bounded amount outward from the start of available space, so how far it got defines what remains and the shop can state it. The drive was assessed on a direct connection with initialisation state read directly, the second finding of a device-level fault explaining why reinstallation resolved nothing. Written regions were measured against capacity and recovery scoped to unwritten areas, with files validated by opening.

The outcome

The installation extent established first, the drive assessed at device level and recovery scoped to the regions never written to. Free assessment, one fixed written figure including VAT; where a chip has to be removed, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: reinstalling is the standard remedy for a machine that will not boot, and it assumes the hardware works. It also writes tens of gigabytes to a drive holding your documents. The question worth asking any shop before work begins is whether there is data on it that matters.

Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.