SD Card Not Detected: An Emergency Decision Tree

An SD card not detected by any device is four different faults wearing one symptom. A card that produces no reaction, one that appears with zero capacity, one that asks to be formatted, and one the camera reads but the computer ignores are separate conditions with separate outcomes. Treating them as one problem is how people format a card that still held every photograph.

Here is the shortest version of the decision: never accept the format prompt, never run a repair utility, and test the reader before you test the card. Then use the table below to identify your case.

What to Stop Doing Immediately

The rules below hold for all four cases, and they are ordered by how much damage the wrong action does.

1. Do not click Format. The prompt is offered because the operating system cannot read the filesystem, not because the filesystem is empty. Formatting rewrites the structures a recovery tool needs.
2. Do not run a “repair” or “fix” utility. Tools that rewrite the boot sector or rebuild a partition table can convert a recoverable case into a permanent one.
3. Do not use the card to test other devices repeatedly. Every mount writes. On Windows, the moment a card mounts, indexing, antivirus, and thumbnail generation may write to it.
4. Do not re-insert the card into the camera “just to check.” Some cameras will offer to repair or format an unreadable card on insertion, and some will do it without asking.
5. Do not photograph or record onto the same card later in the day. Buy or borrow another card; a suspect card should go straight into a static bag.
6. Do not put the card in a phone or tablet to check it. Mobile operating systems are more aggressive about writing to removable storage than desktops are.

If you have already done one of these, stop and reassess — one format attempt usually leaves the original data intact, while several attempts over the same sectors do not.

The Four Cases at a Glance

Case	What you see	Most likely cause	Next action	Realistic outcome
1. Dead silence	No drive letter, no error, no sound; card is not listed in Disk Management	Reader or cable fault, then contact or controller failure	Test the reader and a known-good card first	Good if the reader is at fault; lab referral if the card is silent everywhere
2. Zero capacity	Drive letter appears; capacity shows 0 bytes; properties show no filesystem	Controller cannot read the logical-to-physical mapping table	Stop powering the card; do not attempt repair	Low from software; a lab with chip-off capability is the realistic path
3. Format demand	Drive letter appears with correct capacity; “You need to format the disk”	Filesystem structures damaged; the media itself is usually fine	Image the card, then scan the image	High — the most recoverable of the four
4. Camera only	Camera plays back files; computer shows nothing or the wrong drive	Reader, driver, USB port, partition scheme, or exFAT support	Try another reader, another port, and a different computer	High — often not a card problem at all

Case 1: No Reaction, No Drive Letter, No Error

This is the only case where “nothing happens” is literal. The card does not appear in File Explorer, does not appear in Disk Management, and produces no error message. Software cannot recover data from a device the operating system does not acknowledge.

Work through the causes in cost order:

Test the reader with a different card. A failed reader is far more common than a failed card, and it produces exactly this symptom. If another card mounts in the same reader, the reader is fine and the problem is with the card. If no card mounts, replace the reader before drawing conclusions.

Test the card in a different reader on a different port. Front-panel USB hubs and cheap multi-card readers fail in ways that look like card failures. Prefer a reader that connects directly to the machine.

Inspect the card. Look at the contact pads for contamination, and check for a crack in the body or a lifted contact. Physical damage is manufacturing territory, not software. The causes of physical card damage covers what can be done about a broken body but not yet a broken controller.

If the card is silent everywhere, stop. Repeated power cycles on a card with a failing controller can finish it off. A card that produces nothing in three different readers and two different computers is a laboratory case or a total loss, and each further attempt risks the remaining chance.

Case 2: A Drive Letter With Zero Capacity

Flash cards hide their internals behind a controller and an FTL (Flash Translation Layer) that maps logical addresses to physical memory cells. The card’s identification data — the manufacturer, the nominal capacity, the supported modes — is answered by the controller directly. The actual capacity and file layout come from the mapping table the controller maintains. When a card reports zero capacity while still answering identification requests, the controller is working well enough to introduce itself and not well enough to describe its own contents. The NAND inside is frequently intact.

That distinction explains the outcome. There is no scanning to be done, because there is no addressable data to scan. The recovery path for this failure is reading the memory chips directly, bypassing the controller — a chip-off procedure that requires a laboratory, a matching controller for the same die revision, and a non-trivial chance of failure. Attempting to reformat the card to “reset” it will not restore the mapping table; it will overwrite whatever the controller could still have described.

Do not run a partition-recovery utility against a zero-capacity volume. It will either fail immediately or write attempt logs to the device. Bag the card, note the failure description, and treat the recovery lab comparison as the next step.

Case 3: The Format Prompt

Counterintuitively, the case with the scariest message is the most recoverable. A card that appears with its correct capacity and then triggers “You need to format the disk in drive X” is telling you two good things: the controller is functional, and the storage layer is readable. What has failed is the filesystem — the boot sector, the FAT or exFAT structures, or the root directory.

Almost nothing has been lost at that point. The photographs and videos are still in their clusters; the index that names them has been damaged or replaced with an unreadable structure. This is the case where an emergency scan does the most good, and where the format prompt does the most harm.

The correct sequence:

1. Do not format. Dismiss the dialog without acknowledging it where possible, and disable auto-play and auto-mount before reconnecting the card.
2. Image the card first. A byte-level image on a different drive becomes your working copy. The first-hour stabilization steps cover how to do this without touching the original.
3. Scan the image, not the card, in deep mode. Damaged filesystem structures mean the normal file listing is unavailable, so the scan must find files by signature rather than by directory entry.
4. Save results to a third location. Never back onto the card, and never onto the image.
5. Only format after recovery succeeds — and only if you intend to keep using the card, which is itself worth questioning. Cards that corrupt their filesystem usually do it again; see the underlying causes of filesystem corruption and the corrupted card recovery procedure.

The expected outcome here is good: most files return, with the most recently written files being the most at risk because their cluster chains were the last to be finalized.

Case 4: The Camera Sees It, the Computer Does Not

The most common misdiagnosis in this entire decision tree. A card that plays back fine in the camera and mounts as nothing on a computer is usually not a damaged card. It is a mismatch between how the card is formatted and what the computer or reader can present.

Work through these, in order:

• Reader compatibility. Older readers and adapters may not handle SDXC or exFAT at all, and will present an SDXC card as unreadable rather than as too large. Try a reader rated for SDXC/UHS-II.
• Partition scheme. Cameras format cards for their own use. Most produce a single exFAT or FAT32 partition, but some produce layouts that certain operating systems mount unhelpfully. Disk Management will show whether a volume exists even when File Explorer shows nothing.
• The write-protect tab. On a full-size SD adapter, a tab in the locked position can prevent mounting on some controllers and cause silent failure on others.
• The macOS/Windows difference. A card with a partition map macOS created may be unreadable on Windows without third-party support. Video files larger than 4 GB also exceed FAT32’s file size limit, which is why exFAT is standard on modern cards.
• A dying card that the camera tolerates. If none of the above applies, the card may be degrading in a way the camera’s own error correction masks. Test its health before trusting it again.

If you need the files on a computer and the camera is the only device that reads them, the camera itself is a legitimate transfer mechanism — many cameras support USB mass storage or can copy internally between two card slots. That route also lets you verify files play before you touch the original card.

Matching Your Case to the Right Expectations

Getting the diagnosis right matters less than not making the card worse while you wait, so the honest summary is short. Cases 3 and 4 usually end with your files back. Case 1 is a hardware question first and a data question second. Case 2 is a laboratory question, and the answer is often no.

If you are on Windows and the card is still detected by a computer, a purpose-built recovery tool such as XRecovery (xappset.com) can scan SD, microSD, and other memory cards for deleted or formatted photos and videos. As with any recovery tool, stop writing to the card first and always save recovered files to a different drive. When the card cannot be detected by Windows at all, no scanning tool can help — that is where the card error message reference and the card health testing procedure become the useful next reads.

Frequently Asked Questions

Should I click Format when the card says it needs formatting?

No. That prompt means the filesystem cannot be read, not that the card is empty. The photographs are usually still there. Dismiss the dialog, power the card down, and image it before running any scan.

My card shows 0 bytes. Is it dead?

It is not dead in the way a snapped card is, but it is outside the reach of software. A zero-capacity reading means the controller can identify itself but cannot describe its own storage. Recovery requires a laboratory to read the memory chips directly, and success is far from guaranteed.

Why does my camera read the card when my computer will not?

Usually because the reader, driver, or operating system cannot handle the card’s format or capacity class, while the camera was designed around it. Try a different reader and a different port before concluding the card is damaged.

Is it safe to keep using a card that once failed to mount?

Only after testing it. A card that failed to mount once has demonstrated that something in the chain is unreliable, and cards rarely improve with age. Copy everything off it, run a health check that writes and verifies the full capacity, and retire it to non-critical use if it shows any error.