Data Recovery Case File · Formatted & Logical Faults · Files or a Working System
Recovering an Installation Is Not the Same as Recovering What It Held
His enquiry asks for more than most. A drive removed from his son's laptop and tried in an enclosure on several machines without success, where — with a replacement already fitted — he would like "to recover the whole of his old drive, including the operating system." That is two objectives rather than one, and the second is achievable in a narrower sense than he probably means.
| Media | Laptop hard drive removed from its host and tested through an enclosure — not presenting on multiple machines; replacement drive already fitted to the laptop |
| Reported situation | Laptop drive failing · drive removed and fitted to an external enclosure · tested on several computers without success · replacement drive already installed in the laptop · recovery of the entire drive requested including the operating system · content required |
| Fault class | Device not enumerating across multiple hosts — fault travelling with the drive; deliverable to be defined as files or as a block-level image |
| Equipment used | Deliverable defined as files or block-level image before work began · current draw measured on a controlled bench supply · imaged write-blocked at the block level under strict per-sector timeouts · filesystem structures interpreted with their duplicate copies · image retained so either deliverable remains available |
The decode: what "the whole drive" can and cannot mean
What a recovery produces by default: files. Documents, photographs, settings and application data, extracted and delivered as a folder tree — which is what almost everyone wants and is straightforward to use.
What he appears to be asking for instead: the machine as it was, running. That is a restoration rather than a recovery, and it involves putting an installation back onto hardware and having it start.
Why that rarely works as hoped: a modern installation is bound to the hardware it was set up on. Drivers, activation and configuration are matched to the original machine, and an installation moved to different hardware frequently will not start or starts badly.
Why it is doubly awkward here: a replacement drive is already in the laptop with a fresh installation on it. Restoring the old system would mean displacing the new one, and the son would lose whatever has been set up since.
What is genuinely deliverable and usually better: a block-level image of the old drive. That is a complete copy of everything, including the operating system, kept as a single file — nothing is discarded, and it can be examined or mounted later.
Why an image satisfies the underlying wish: what he is really guarding against is something being missed. An image contains the entire drive rather than a selection, so nothing depends on anyone deciding in advance what mattered.
How the files are then produced: from the image rather than from the drive. The extraction runs against the copy, and the image is retained so anything overlooked can be revisited without touching the original again.
Why the enclosure test he ran was worth doing: several machines and a different connection. Consistent failure means the fault travels with the drive, which rules out the laptop, the port and the operating system in one step.
What the enclosure could not tell him: why. It supplies power and passes data and reports nothing about current draw, rotation or whether the drive completes its own initialisation — which is why the next step is assessment rather than another machine.
What is worth deciding before the work: whether an image, a file set, or both are wanted. Both is usually the right answer, and it costs little more than either alone once the capture exists.
On the bench
The deliverable was defined as files or block-level image before work began — recovery ordinarily producing extracted files as a folder tree, whereas restoring a working installation binds to the original hardware through drivers, activation and configuration and frequently will not start elsewhere. A block-level image contains the entire drive including the operating system as a single retained file, so nothing depends on deciding in advance what mattered. Imaging ran write-blocked under strict per-sector timeouts.
The outcome
The deliverable defined before work began, the drive assessed on a controlled bench supply, and a block-level image taken and retained. 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: the whole drive is deliverable as an image rather than as a running system. An installation is bound to the hardware it was built on — but an image contains everything, so nothing has to be chosen in advance.
Asking for everything rather than a selection
Ask for a block-level image as well as extracted files, since that's what "the whole drive" actually delivers — a complete copy of everything including the operating system, kept as one file, so nothing depends on someone deciding in advance what mattered. What generally isn't worth pursuing is restoring the installation to running order: a modern system is bound to the hardware it was set up on through drivers, activation and configuration, and moved elsewhere it often won't start. That's doubly awkward if a replacement drive is already in service, since restoring would displace it.
Ask for an image — call Manchester Data Recovery on 0161 871 0788; deliverable defined before work begins, imaged at the block level under capped timeouts, image retained so nothing is foreclosed.
Request a quote online →
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.