Emergency · unstable card and reader
Memory card keeps disconnecting during access
How should I handle a memory card that repeatedly disconnects?
Short answer
Stop the copy or scan first: every dropout interrupts reads and can stress failing flash further. Change one variable at a time, such as reader, cable, adapter or port. If the card then stays connected, image it once and work from the image; if it still drops out, software cannot help and a lab is next.
The situation
The volume appears, vanishes, and reconnects during copies or scans.
A volume that appears and vanishes during a read is a hardware signal, not a file system problem. Each dropout aborts the transfer at an arbitrary point, and if failing flash is behind it, every further attempt costs read cycles the card may not have left.
01 / Diagnose
Work out what actually disappeared
The chain between card and computer has many weak links: a worn adapter, a cheap extension cable, a hub sharing bandwidth, a port that drops power under load. Those are cheap to rule out. The other possibility is the card itself, where a controller that overheats or a flash layer with failing blocks stalls and resets the connection mid-read, always around the same area.
A poor adapter, cable, port, controller, or degrading flash layer can interrupt sequential reads.
Check the last known path, trash and backups without writing to the original device.
02 / Protect the source
Preserve the best recovery chance
- 1
Stop the running copy or scan rather than letting it retry endlessly; repeated retries heat the card and buy nothing.
- 2
Change one thing at a time, first the reader, then the cable, then the port, so you learn which part of the chain caused the dropouts.
- 3
Once the card stays mounted, make a single sector image to another disk and disconnect the card afterwards.
- 4
Run every scan and export against that image, so the card is read once and the rest of the work costs it nothing.
Do not keep replugging the card in the hope that one attempt will run through, and do not start a full scan while the connection is unstable. A scan interrupted halfway is worth nothing and puts load on a card that may be close to failing.
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 dropping out in every reader, software has reached its limit, because the blocks never arrive at the operating system. File Recovery Hero works on stable sources and on unchanged images; a physically failing card needs a data recovery lab.
04 / Verify
Check the recovered content, not just its name
A good image runs from the first to the last sector without a reset and ends with the exact byte count the device reports. If the imaging tool logs read errors, note where they fall: files whose data sits in those regions are the ones to check most carefully after export.
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 unstable card and reader be recovered in this situation?+
A volume that appears and vanishes during a read is a hardware signal, not a file system problem. Each dropout aborts the transfer at an arbitrary point, and if failing flash is behind it, every further attempt costs read cycles the card may not have left. The result still depends on what remains readable on the source.
What should I avoid before scanning?+
Do not keep replugging the card in the hope that one attempt will run through, and do not start a full scan while the connection is unstable.
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 good image runs from the first to the last sector without a reset and ends with the exact byte count the device reports.