← Back to the catalog

Memory Card Not Recognized or Asks to Be Formatted

An SD or microSD card can fail to appear, show the wrong capacity, or ask to be formatted for reasons that sit at completely different layers: the reader or adapter it's plugged into, the file system the operating system expects to find, the controller and flash-translation logic inside the card, or the physical flash itself. A format prompt doesn't identify which of those it is. Formatting writes new logical structures onto the card and can overwrite or replace evidence needed for recovery, so it should not be used to diagnose why the card became inaccessible.

Recovery decision

Memory card not recognized or asks to format: what should you do next?

Answer one question about the current state. The result suggests the safer next step rather than diagnosing the failure.

Typical source stabilityLayer-dependent

Default action riskHigh

Default first actionIdentify the layer first

Check my situation

This guide classifies the next recovery action from observable information. It does not diagnose hardware condition or estimate a percentage chance of recovery.

First determine whether the card itself is visible and stable

A memory card usually reaches a computer through more path components than an internal drive does: the card itself, an SD adapter where a microSD card is used in an SD slot, a card reader, the reader's USB or host connection, and only then the operating system. Failing to appear through one reader or one adapter is not yet proof that the card has failed — a different reader, a different adapter, or a different USB port can behave differently for reasons that have nothing to do with the card's condition. This is worth checking once, in a reader that is known to work with other cards. It is not worth checking repeatedly if the card is already behaving unstably: if the card is already unstable, repeated insertion, power cycling and enumeration attempts can consume a limited window of usable access or aggravate an intermittent electrical, contact or controller problem, so testing should remain controlled and minimal.

Treat this table as a router, not a diagnosis. More than one row can apply as a situation develops — a card that first showed wrong capacity can also become unstable, for example.

A format prompt is a symptom, not a diagnosis

“You need to format this card before you can use it” is what an operating system says when it cannot mount a volume it recognizes as a storage device — it is a response to an unreadable or unrecognized volume structure, not a test result about the flash underneath it. Formatting is not a diagnostic step: it creates a new, empty file system on top of whatever is there, which is the opposite of what a recovery attempt needs. The operating system can see a block device while still being unable to recognize or mount a usable volume on it, so a format prompt describes the host's inability to use the current logical structure; it does not identify whether the underlying cause is partition damage, filesystem damage, an unsupported structure, or a lower-level read problem. For more depth on each of those, see Drive Shows as “RAW”, Accidental Formatting and File System Corruption, which cover the same logic for drives generally.

Correct capacity and stable reads change the recovery path

A card that reports its correct, expected capacity and holds a stable connection while reading is far more consistent with a purely logical problem — a damaged partition table, file system or directory structure — than with a failing card. That combination does not prove the card is otherwise healthy, but it does make ordinary file-system-level recovery from an image of the card a reasonable next step. A card reporting the wrong capacity, or one that reads unstably, points lower in the stack, toward the controller, the flash-translation layer, or the physical media, and changes what a safe first step looks like.

Reader/adapter problems can imitate card failure

Each of these components can produce symptoms that look like a dead card without the card itself being at fault: a worn adapter contact, a failing reader, or a flaky USB connection can all cause a card to fail to enumerate, appear intermittently, or show implausible capacity. Windows' own SD driver stack, for one documented example, passes a card through a bus driver and a storage class/miniport driver before it ever reaches a file system — several layers exist between the physical contacts and anything the user sees. Swapping to a different, known-good reader once is a reasonable and safe check; treating every reader as equally suspect and cycling through many of them on a card that is already unstable is not.

When wrong capacity points lower in the flash stack

Correct capacity does not prove a card is healthy, but wrong capacity is informative on its own — the same distinction covered in more general terms by Drive Shows the Wrong Capacity. Modern SD and microSD cards are not simple, unmanaged NAND chips: like an SSD, they contain a controller that handles bad-block management, error correction and logical-to-physical translation. A card that reports 0 bytes, a changing capacity or an implausibly small capacity points below an ordinary file-system problem toward the device, controller, translation or access path — the reported capacity alone does not identify which internal component or metadata structure failed. That can call for a different recovery path than a straightforward file-system scan, closer to the flash-level work described for controller and translation-layer failures elsewhere on this site. Chip-off extraction and monolithic-package reconstruction, where they apply, are a Method-level and hardware-level topic, not something this Case walks through.

Counterfeit capacity is a different failure mode

A card that reports far more capacity than is physically present is a distinct situation, not an ordinary case of controller wear or bad sectors. Typical symptoms include older files becoming unreadable as new data is written, files that appear to save successfully but cannot later be read back, and corruption that recurs once writes pass a real, much smaller physical boundary than the reported one. This is address aliasing on top of a smaller real flash array, and it behaves differently from ordinary flash degradation — see Counterfeit Flash Capacity and Address Aliasing for how that mapping works and what it changes about recovery.

What you can check safely

Before formatting, repairing or writing anything: note the card's brand, capacity and type; note whether a different known-good reader changes the result; record the exact capacity the operating system reports; note whether the card is being used with an adapter; note any error text verbatim; note whether the problem appeared gradually or immediately after a specific event, such as being removed while writing; and, if the card is stable, make a full image before running any repair or recovery tool against the card itself. None of this requires writing to the card.

The safer recovery path

When this becomes video recovery instead

A camera or card can be stable and correctly recognized while specific video files remain broken, incomplete or missing, because a recording was interrupted, allocation was lost, or container metadata was never finalized. Once the card itself reads reliably, that is a content-level problem rather than a card-access problem, and it is covered in more depth by Corrupted or Deleted Video from a Memory Card. If a specific video file already exists somewhere as a file — recovered or original — but won't play, see Corrupted Video File (MP4/MOV Won’t Play) instead; this Case does not repeat that container-level detail.

This Case is a router for memory-card access and format-prompt symptoms specifically; once the card mounts and the question is about specific missing or damaged files, see Corrupted or Deleted Video from a Memory Card and Corrupted Video File (MP4/MOV Won’t Play). For the underlying logical-layer explanations this page routes to, see Drive Shows as “RAW”, Drive Shows the Wrong Capacity, Drive Not Detected or Keeps Disappearing, USB Flash Drive Failure and File System Corruption · Counterfeit Flash Capacity and Address Aliasing.