Data Recovery Case File · Desktop Externals & Aging Drives · Go Back to What Worked
They Worked on My Dad's Computer
Her enquiry contains its own solution and she has not spotted it. Several external drives from her college years, "which previously I thought were corrupted. Since then my dad has plugged them into his home PC and they all worked fine — he was able to view and navigate the contents on an older Windows machine, and labelled the basic contents accordingly. He simply plug-and-played them. Since getting them back I have tried running them on my 2015 MacBook Pro as well as a Windows machine and I can"not. The drives are demonstrably fine. Somebody read every one of them, browsed them and wrote down what was on them. What has failed is not the storage — it is the pairing of those drives with her machines.
| Media | Several external hard drives written between approximately 2010 and 2015 — read successfully and catalogued on an older Windows PC; not accessible on the owner's newer Mac or Windows machine |
| Reported situation | Drives previously believed corrupted · subsequently read in full on an older Windows machine with contents browsed and listed · returned to the owner · not accessible on a 2015 Mac or a current Windows machine |
| Fault class | Host-side compatibility rather than device or data failure — drives and contents demonstrated intact on a machine that could read them |
| Equipment used | Compatibility branch established before any bench work · drives read write-blocked on native equipment where required · filesystems identified independently of any host's support · contents delivered on cross-platform media |
The decode: what her father proved, and what changed
The strongest evidence in the archive: a person sat at a computer, opened every drive, navigated the folders and wrote down what was in them. That is not a partial success or a hopeful sign — it is proof that the drives spin, respond, present their filesystems and return data. No assessment could establish more. Whatever is happening now, the contents are not the problem.
Why an older machine could read them and newer ones cannot: two likely causes, both host-side. Drives formatted years ago may use older filesystem variants that newer operating systems have quietly dropped or reduced support for — a change that arrives with an update and is announced to nobody. And drives of that era sometimes depended on manufacturer software for access or encryption, which no longer runs on current systems. In both cases the drive is untouched and the machine simply cannot make sense of it any more.
Why her Mac is the least likely to help: macOS declines to mount filesystems it cannot parse and shows nothing at all — so a drive that would at least produce an error on Windows appears simply absent. Testing on a Mac first makes a compatibility problem look like a dead drive.
What she should do, and it costs nothing: take the drives back to the machine that read them. That computer has already demonstrated it can, and the sensible move is to copy everything off there — onto a new drive, formatted for whatever she uses now. Her father has already done the hard part by producing a contents list, so the copying can be checked against it. This is not a recovery job while a working route exists.
The urgency nobody has mentioned: those drives are ten to fifteen years old and have been sitting unused. They are not going to keep working indefinitely, and the machine that reads them is also ageing. The window in which both exist is open now and will not stay open. Copying them this month rather than next year is the whole of the advice.
When it does become a bench job: if a drive that read on her father's machine subsequently stops reading anywhere — which, at that age, is entirely possible — then the position changes. That is worth knowing in advance so it is not a surprise.
On the bench
The compatibility branch was established before any bench work, since drives demonstrably read and catalogued on another machine do not have a fault and saying so is the honest answer. Where a drive had since stopped reading anywhere, it was read write-blocked on native equipment and its filesystem identified independently of any host's support — which distinguishes an unsupported-but-intact volume from a damaged one. Contents were delivered on cross-platform media formatted for current use.
The outcome
The working route identified first at no cost, with bench work reserved for drives that had genuinely stopped reading. Free assessment, one fixed written figure including VAT, no recovery, no fee. The decode, for anyone whose drives work on one machine and not another: somebody browsing the contents and writing them down is the strongest proof there is that your drives and data are fine — so the fault is the pairing, not the storage; older filesystem variants and manufacturer software have quietly stopped being supported by newer systems, and a Mac shows nothing at all rather than an error, which makes a compatibility problem look like a dead drive. Go back to the machine that worked and copy everything off there, now.
Drives that read on one computer and not another
Go back to the computer that read them and copy everything off there — that's the answer, and it's free. If somebody has browsed the contents and written down what was on them, your drives and your data are proven fine; what's failed is the pairing with your current machine. Older operating systems support older filesystem variants that newer ones have quietly dropped, and some drives of that era relied on manufacturer software that no longer runs. A Mac makes this look worse than it is, because it declines to mount anything it can't parse and simply shows nothing. Do it soon, though: drives that old aren't going to keep working indefinitely, and neither is the machine that reads them. Copy onto a new drive formatted for what you use now, and check it against the contents list.
Copy them off there now — or call Newcastle Data Recovery on 0191 406 1051; compatibility ruled out before anything is charged, filesystems identified independently of any host.
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.