Data Recovery Case File · Formatted & Logical Faults · Replaced Halfway

An Interrupted Update Leaves a System Made of Two Versions

His enquiry is short and the sequence is complete. A laptop that "last week said that it needed updates and wouldn't work beyond that. I have bought a new one, but I have stuff to recover from this old one — mainly photos and documents." An update replaces system components in stages, and one that stops partway leaves a machine assembled from two incompatible halves — which is a start-up problem and nothing to do with his photographs.

The decode: what an update does, and why stopping is worse than not starting

How an update is applied: in stages. Components are replaced one after another, and the system is only consistent at the beginning and at the end — in between, it is part old and part new, which is why updates ask not to be interrupted.

What stopping partway produces: a machine whose system files disagree with each other. New components expecting new counterparts find old ones, the start-up fails, and it fails identically every time because nothing changes between attempts.

Why an interrupted update is worse than an update never attempted: the original system was consistent. The half-updated one is not, and the machine has no route back to the version it was working from unless a rollback mechanism completed properly.

Why none of that touches his files: updates replace system components. They do not visit documents or photographs, which sit in an entirely separate part of the drive and are unaffected by which version of the operating system is or is not correctly installed.

Why his position is unusually straightforward: he has already bought a replacement machine, so nothing needs to be repaired. The old laptop does not have to start again — the drive comes out, reads on another computer, and the photographs and documents transfer to the new machine.

Why that makes this retrieval rather than recovery: the storage is very probably healthy. An update failing is a software event, and unless the drive was failing beforehand and caused the interruption, there is nothing wrong with the device at all.

What is worth establishing, since it changes the picture: whether the machine was showing any signs before the update. Updates fail more often on drives that are already struggling, because they involve heavy sustained writing — so a machine that was slow or crashing beforehand may have a hardware fault that the update exposed rather than caused.

What must not happen: no repeated attempts to start it, and no acceptance of any offer to reset or reinstall. A reinstall would produce a working machine he no longer needs, at the cost of writing over the files he does.

On the bench

Update interruption was distinguished from device failure before any assessment — updates replacing system components in stages and being consistent only at the beginning and end, so an interruption leaves new components paired with old counterparts and a start-up that fails identically each time, while user content is never visited. The drive was removed and read independently of the machine and imaged write-blocked on a matched adapter.

The outcome

The interruption distinguished from device failure, the drive read independently, and content delivered without reference to the installation. Free assessment, one fixed written figure including VAT; where a drive has to be opened, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: an update replaces system components in stages, and one that stops leaves a machine made of two versions that disagree. Your photographs sit elsewhere entirely and were never involved.

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.