Call us — 0113 322 3083
Mon–Fri · 9am–5:30pm · No fix, no fee
Start a free diagnostic →

Data Recovery Case File · Solid State & Flash · Two Platforms, One Finding

Stick Registers on Windows but Not on a Mac

The enquiry described a device behaving differently on two machines and treated it as confusing. It is actually the most useful thing that could have happened. "My memory stick has suddenly stopped registering on my Mac. On a Windows PC it registers but doesn't open. Is it possible to retrieve the files and what is the cost?" Email contact was requested, as phone calls are difficult at work, and was honoured. Two platforms disagreeing about a device is not a contradiction — it is two independent tests giving two pieces of information, and together they place the fault precisely. The Windows result establishes that the hardware works. The Mac result reflects how macOS handles a volume it cannot make sense of. Between them they point at one layer, and it is the recoverable one.

MediaUSB flash drive — no longer appearing on a Mac; enumerated by a Windows PC but the volume will not open; contents required
Reported situationSudden onset · device invisible on macOS · recognised but inaccessible on Windows · email contact requested and honoured
Fault classPartition or filesystem damage over working hardware — enumeration confirmed by one platform, mount refused by both
Equipment usedWrite-blocked imaging (DeepSpar USB Stabilizer 10Gb) · partition and filesystem reconstruction on the image · signature carving for anything beyond structural repair · files verified by opening and delivered

The decode: what each platform is telling you

What Windows proves: the more valuable of the two results. For Windows to register the device, the stick must have received power, its controller must be working, and it must have identified itself successfully. That single fact eliminates the serious hardware faults in one go — a dead controller, cracked connector joints, a broken solder pad. The hardware is fine. That the volume then will not open means the failure is one layer up, in the partition structures or the filesystem, with the files sitting intact behind them.

Why the Mac shows nothing at all: not a different fault, a different presentation. macOS only places a volume on the desktop or in the Finder sidebar once it has mounted successfully, and it declines to mount a filesystem it cannot parse or does not recognise. A stick whose structures are damaged therefore produces exactly what was described: nothing visible, with no error and no explanation. It is still there — it will appear in System Information's USB section and usually in Disk Utility with Show All Devices enabled — but Finder, which is where everyone looks, shows an empty desktop. Windows is simply more talkative about devices it cannot use.

Why the disagreement is good news: because the pessimistic interpretation — that the stick has died — is ruled out by the Windows result. The two platforms are not contradicting each other; they are describing the same damaged filesystem from two different philosophies about what to display.

What to decline on both machines: and this is where the case is won or lost. Windows will offer to scan and repair the drive or to format it. macOS will offer First Aid, and may offer to initialise the disk. All four write to precisely the structures a reconstruction rebuilds from, and on a stick holding the only copy of anything they are the wrong order entirely. Repair belongs on an image, after the data is secured — never on the original while it is still the only one.

On the cost question: the assessment is free and establishes which layer has failed; one fixed figure follows in writing before any work; and on a stick whose hardware is working, nothing is payable unless the files come back.

On the bench

The stick was imaged write-blocked behind the DeepSpar USB Stabilizer 10Gb in a single pass, so that everything afterwards happened against a copy and neither platform's repair offers could reach the original. On the image the structures were examined in order — the partition records first, then the filesystem — establishing which layer had failed, and that layer was reconstructed until the volume mounted from the copy with its folder tree, filenames and dates intact. Signature carving swept alongside for anything the structural repair could not reach. The files were verified by opening rather than counted, and delivered on fresh media, with progress reported by email throughout.

The outcome

The volume rebuilt from a write-blocked image and the contents verified and delivered. Free assessment, one fixed written figure including VAT, no recovery, no fee. The decode, for anyone whose device behaves differently on two computers: that is two tests rather than one puzzle — a platform that registers the device proves the hardware, the controller and the connector are all working, which rules out the serious faults; a platform showing nothing is usually declining to mount a filesystem it cannot parse, which is a display philosophy rather than a worse fault, and the device will still appear in the deeper system views. Between them they place the failure in the partition or filesystem layer, with your files intact behind it — provided you decline every offer to scan, repair, initialise or format on either machine.

Device visible on one computer and not the other

Treat that as useful information rather than a contradiction. If any machine registers the device, its hardware is working — power, controller and connector are all fine — and that rules out the failures that make sticks genuinely unrecoverable. A machine showing nothing at all is usually just declining to mount a filesystem it can't parse; on a Mac, check System Information's USB section and Disk Utility with Show All Devices enabled and you'll generally find it sitting there. So the fault is in the partition or filesystem layer, with your files intact behind it. The critical part is what you refuse: Windows will offer to scan and repair or to format, and macOS will offer First Aid or to initialise. All of those write over the structures a recovery rebuilds from. Say no on both machines, stop reinserting it, and have it imaged once with the repair done on the copy.

Seen on one machine, invisible on another?
That combination is a diagnosis — call or email Leeds Data Recovery on 0113 322 3083; imaged write-blocked, structures rebuilt on the copy, files verified by opening.
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.

0113 322 3083