Storage media · card and removable reader
Card reader disconnects during a recovery scan
Should I continue when the reader disconnects during scanning?
Short answer
No, stop the scan: results from a dropped connection are incomplete, and repeated attempts strain a possibly unstable card. Change one variable, such as a known-good reader, cable or port. If the card then stays connected, image it and analyse the image; if it keeps vanishing, consult a data recovery lab.
The situation
A scan stops because the device vanishes from macOS or Windows.
Stop the scan. A pass that continues across a dropped connection produces a result list nobody can rely on, because whole regions were never read at all, and every retry pushes a possibly weak card a little further. Change one thing at a time before trying again.
01 / Diagnose
Work out what actually disappeared
Disconnects during a long read have three usual causes. Bus-powered readers and hubs can fail to deliver steady power under sustained load; worn cables, extension leads and stacked adapters lose contact; and a card whose controller is failing drops off the bus by itself. The symptom looks identical in all three cases, which is why the variables must be separated one at a time.
Reader power, cable quality, adapters, or source instability can make scan results incomplete.
Check the last known path, trash and backups without writing to the original device.
02 / Protect the source
Preserve the best recovery chance
- 1
Cancel the running scan and unmount the card properly instead of pulling it out while the pass is still active.
- 2
Swap a single component, a known-good reader, a shorter cable or a port directly on the machine, and try mounting again.
- 3
If the card now stays connected, capture a sector image first, so the reading happens once instead of repeatedly.
- 4
Run the analysis against that image and export recovered files to an internal disk, leaving the card untouched afterwards.
Do not restart the same scan over and over on the same setup, and do not connect the card through a hub shared with other busy devices. A card that keeps disappearing regardless of reader, cable and port should not be scanned again at all.
03 / Choose the method
Match the tool to the source
For stable, readable exFAT, NTFS and FAT16/FAT32 or uncompressed IMG, DD, RAW and BIN images.
Unconfirmed exports are marked .UNVERIFIED.
If the card keeps vanishing with every reader and cable, the hardware is failing and a data recovery laboratory is the only remaining route. File Recovery Hero reads what the operating system delivers; it cannot address a device that is not present.
04 / Verify
Check the recovered content, not just its name
A trustworthy pass runs from start to finish without the device disappearing, reports a sector count matching the card capacity, and produces a stable set of results on a second run. Files that open completely in their own application confirm that the read was sound.
Keep the source until two verified copies exist. One working preview is not enough.
Sources and technical references
FAQ
Questions about this recovery case
Can card and removable reader be recovered in this situation?+
Stop the scan. A pass that continues across a dropped connection produces a result list nobody can rely on, because whole regions were never read at all, and every retry pushes a possibly weak card a little further. Change one thing at a time before trying again. The result still depends on what remains readable on the source.
What should I avoid before scanning?+
Do not restart the same scan over and over on the same setup, and do not connect the card through a hub shared with other busy devices.
Does scanning write to my memory card?+
Your memory card is only read. Nothing is saved to it.
How do I know whether the result is complete?+
A trustworthy pass runs from start to finish without the device disappearing, reports a sector count matching the card capacity, and produces a stable set of results on a second run.