Data Recovery Case File · Formatted & Logical Faults · The Wrong Test
A Drive That Will Not Boot Another Machine May Still Read Perfectly as a Second Drive
His enquiry describes a sensible action producing a misleading result. His sister's laptop has died with baby photographs on the drive, so he removed it and "tried plugging it into another laptop but it won't boot." Booting and reading are different operations — a healthy drive from one machine routinely fails to start another, and the test he ran cannot answer the question he needs answered.
| Media | Hard drive removed from a failed laptop — not starting a second machine when installed as its system drive; approximately 10GB of photographic content held |
| Reported situation | Laptop ceasing to function · hard drive removed by a family member · drive installed in a second laptop · second machine not starting from the drive · approximately 10GB of photographs and video sought · recovery requested on the owner's behalf |
| Fault class | Boot failure in a foreign machine — inconclusive as to drive condition; hardware and licensing differences sufficient to prevent starting a healthy drive |
| Equipment used | Boot failure treated as inconclusive rather than as evidence of drive fault · drive read as secondary storage rather than as a system volume · imaged write-blocked at the block level under capped timeouts · user profile regions extracted with system files excluded · recovered content validated by opening at full resolution |
The decode: why the test misleads, and what to do instead
What booting from a drive requires: the system on it to match the machine. An installed operating system carries drivers, hardware configuration and activation tied to the computer it was installed on, and a different machine presents different hardware at every level.
Why a healthy drive commonly fails that test: the system does not recognise the machine it wakes up in. It may stop at a startup error, restart repeatedly, or simply not be offered as a boot option — all with the drive reading perfectly.
Why that makes his result uninformative: failure to boot is the expected outcome for a working drive in a foreign machine. He has not learned whether the drive reads, because the test does not measure that.
What the right test is: connecting it as a second drive rather than as the system drive. The machine boots from its own drive and simply lists the other as additional storage, at which point files can be copied off.
Why that works where booting does not: reading files requires only that the filesystem be interpretable. No drivers, no configuration and no activation are involved — the system reads it as it would any external drive.
What is needed to do it: an adapter or enclosure appropriate to the drive's connector. It is an inexpensive item and the commonest way this whole situation resolves at no cost.
Why it is worth telling him rather than quoting him: if the drive is healthy, he does not need a laboratory. Ten gigabytes of photographs copied over an afternoon is the best outcome available, and it costs him the adapter.
What the second machine attempt may nonetheless have cost: possibly something. A foreign system attempting to start from a drive can write repair entries or modify boot structures, though it rarely reaches the user's files.
Why he should stop attempting it now: repeated boot attempts add writes without adding information. Each one runs a repair sequence that was never going to succeed.
What would indicate a genuine fault, as distinct from this: the drive not appearing at all when connected as secondary storage, or appearing without a readable volume. Those are meaningful findings; failing to boot is not.
On the bench
Boot failure was treated as inconclusive rather than as evidence of drive fault — an installed system carrying drivers, hardware configuration and activation bound to the machine it was installed on, so a foreign machine commonly refuses to start from an entirely healthy drive. Reading files requires only an interpretable filesystem, involving no drivers, configuration or activation. The drive was read as secondary storage rather than as a system volume.
The outcome
Boot failure treated as inconclusive, the drive read as secondary storage, and user regions extracted with system files excluded. Free assessment, one fixed written figure including VAT — with the honest advice offered first where a drive proves this readable. The decode: booting and reading are different operations. A healthy drive routinely refuses to start a machine it was never installed in — so that test tells you nothing about whether the photographs can be copied.
Testing a drive taken out of a dead machine
Don't try to boot from it — connect it as a second drive instead, using an inexpensive adapter or enclosure, and let the machine start from its own drive while listing yours as extra storage. A system installed on one computer carries drivers, configuration and activation bound to that machine, so a perfectly healthy drive routinely refuses to start a different one. Stop repeating the boot attempt, since each try runs a repair sequence that was never going to work. Not appearing at all as a second drive would be a real finding.
That is the wrong test — call Manchester Data Recovery on 0161 871 0788; boot failure treated as inconclusive, drive read as secondary storage, honest advice offered before any quotation.
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.