Data Recovery Case File · Formatted & Logical Faults · The Shop Was Right
The Reset Was Both a Write and a Load
His enquiry describes an attempt to fix that made things worse in two ways at once. A laptop that stopped working: "tried restoring factory settings but it stopped working again. I took it to a shop — they said the hard drive is damaged and any further use is just damaging it more. So it's a physical problem. Therefore I'd like a professional to look and see if they can retrieve my data." The shop gave him accurate advice and he acted on it, which is more than most. But the reset he tried first is worth understanding, because it is the standard remedy and it is precisely wrong here.
| Media | Laptop internal hard drive with physical damage — factory restore attempted and completed before failure recurred; further use discontinued on advice |
| Reported situation | Machine ceasing to work · factory restore attempted by the owner · machine failing again afterwards · assessed by a shop reporting physical drive damage and advising against further use · machine taken out of service · data required |
| Fault class | Physical read failure compounded by a factory restore — sustained load applied and system data written across existing content |
| Equipment used | Machine removed from use on advice already followed · Atola Insight Forensic error-rate assessment · imaged write-blocked under per-sector timeouts with weak regions revisited · restore extent measured against total capacity · recovery performed against the image |
The decode: why a reset is the wrong tool here, and what remains
Why it is the standard advice: most machines that stop working have software problems, and a factory restore fixes a great many of them. It is what support articles suggest, what shops suggest, and what anybody reasonable would try. The assumption underneath it is that the hardware works — and where that assumption holds, it is good advice.
Why it was doubly damaging here. First, a restore writes — tens of gigabytes of system files laid down across the drive, into space that held his data. Second, and less obvious, a restore is a sustained read and write load lasting an hour or more: verifying, decompressing and writing continuously, at temperature, on a mechanism that was already failing. So it consumed data and margin at the same time.
Why the reset then failed anyway: because the underlying fault was physical. Rewriting the operating system does not repair a drive that cannot read reliably, so the machine came back up and then stopped again — which is itself the strongest evidence that the problem was never software. A machine that fails again immediately after a clean restore has a hardware fault. That is a useful rule in general.
Why the shop deserves credit: "any further use is just damaging it more" is exactly right, and it is not what every shop says. A great many would have tried a recovery scan, run a repair utility, or kept the machine powered while investigating — all of which are more of the same load. Telling a customer to stop, and that the answer lies elsewhere, is the correct call and it is worth acknowledging.
What actually survives, and it is not nothing: a restore writes a bounded amount, working outward from the beginning of the available space. On a drive substantially larger than that footprint, everything beyond it was never written to. Files recovered from that region come back by carving — identified by their own internal structure, organised by type and date rather than by folder, since the original index is gone.
Why imaging comes first regardless: a drive with physical read failure cannot support a recovery scan, which reads the whole surface. It is captured once under strict per-sector timeouts, with weak regions revisited on later passes, and the recovery run against the image.
On the bench
The machine had already been removed from use on the shop's advice, which was correct and which most people do not receive. The Atola Insight Forensic assessed error rates before anything else. The drive was imaged write-blocked under per-sector timeouts with weak regions revisited on later passes, the restore extent measured against total capacity to establish how far the new system had written and therefore how much lay beyond it untouched, and recovery performed against the image rather than the drive.
The outcome
The error rates measured, the drive imaged under timeout control and recovery run against the image with the restore footprint established. 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, for anyone who reset a machine that would not work: it is the standard advice and it assumes the hardware is fine. On a failing drive it does two things at once — writes tens of gigabytes over your data, and applies an hour of sustained load to a struggling mechanism. And a machine that fails again straight after a clean restore has a hardware fault.
Factory reset that didn't fix a machine
Stop using it — and if a shop has already told you that, they gave you good advice that not everyone gives. Worth understanding what the reset did, because it's the standard suggestion everywhere and it assumes your hardware is fine. On a drive that's physically failing it does two damaging things at once: it writes tens of gigabytes of system files into the space your data occupied, and it applies an hour or more of continuous reading and writing to a mechanism that was already struggling. The fact that it failed again afterwards is actually the clearest evidence you have — rewriting the operating system can't repair a drive that won't read, so a machine that stops again right after a clean restore has a hardware problem. Material beyond the restore's footprint is often untouched.
That points at hardware — call Newcastle Data Recovery on 0191 406 1051; error rates measured first, imaged under per-sector timeouts, restore footprint established and recovery run against the image.
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.