SD Card Not Detected? Safe Steps Before Data Recovery

Quick answer

If an SD or microSD card is not detected by any device, recovery software cannot scan it yet. Do not format, initialize, repair, or repeatedly reconnect the card. First find out whether a computer can identify the physical card and report its correct capacity.

If the card appears consistently with the correct size, the problem may be logical and a sector-level image is usually the safer starting point. If it is absent everywhere, reports zero or the wrong capacity, becomes hot, or repeatedly disconnects, stop DIY attempts and consider a professional flash-recovery service.

The 60-second safety checklist

Stop using the card immediately. Do not:

Take more photos, record video, download files, or let an app use the card.
Accept a Format, Erase, Initialize, Repair, Scan and fix, or Set up card prompt.
Run CHKDSK, First Aid, DiskPart clean, or a partition-repair tool on the only copy.
Recover files back to the same card.
Scrape contacts, bend the card, heat it, freeze it, open it, or attempt soldering.
Keep cycling through phones, cameras, readers, and recovery programs after the same failure is confirmed.

If one phone, camera, or computer can still display the files, do not keep testing. Copy the most important files to a separate healthy device first, then open a representative sample to verify the copy.

“Not detected” can describe four different states

What you see	What it means for the next step
The camera or phone sees the card, but one computer or reader does not	A reader, adapter, port, driver, or capacity-compatibility problem is still possible
Windows Disk Management or macOS Disk Utility shows the correct capacity, but no usable volume mounts	The card is physically communicating; a partition or file-system problem may be involved
The card appears as RAW, Unallocated, Not Initialized, or macOS asks to erase it	Do not create a new file system; preserve an image if the card is stable
The card is absent in every compatible reader, reports zero bytes or the wrong capacity, or repeatedly disappears	Normal recovery software does not have a stable device to read; specialist evaluation is the safer path

A missing drive letter is not the same as a missing physical card. Likewise, a format prompt does not prove that the card is empty. It only shows that the current device cannot mount the expected file system.

Step 1: Consider what happened before the card disappeared

History changes the risk. Stop immediately and avoid further power if the card:

Is cracked, bent, chipped, corroded, wet, burnt, or unusually hot.
Failed during a power loss, device crash, interrupted write, or unsafe removal.
First showed read errors, severe slowness, corrupted files, or a warning to back up.
Worked intermittently and now disappears during reads.
Contains the only copy of irreplaceable photos, recordings, or business data.

Visible damage is not required for a flash card to fail. A card can look perfect while its controller, internal connections, or flash memory no longer communicates normally.

Step 2: Run one controlled compatibility check

For a card with no visible damage and no heat:

Turn off the original phone, camera, recorder, or player before removing the card.
If it is a microSD card inside a full-size adapter, try one known-good adapter. The adapter itself can fail.
Use one known-good USB card reader that supports the card type and capacity.
Connect the reader directly to the computer rather than through a hub.
Try one other USB port and, if available, one other computer.
Record exactly what each device reports, including capacity and error text.

Kingston’s memory-card support guidance notes that some built-in readers do not support higher-capacity cards and recommends testing a compatible external reader. That makes one compatibility check reasonable. It does not justify dozens of reconnection attempts.

A full-size SD card’s lock switch controls write protection when the host respects it. It does not repair a card, make an incompatible reader compatible, or guarantee true hardware write blocking.

Step 3: Check Windows Disk Management without changing the card

Open Disk Management and locate the card by capacity, not only by drive letter.

Correct capacity and a recognized volume

If the expected card appears consistently with the correct size and a recognized file system, copy accessible files to another physical device. A missing drive letter may be a mounting issue, but verify that you have selected the correct volume before changing anything.

Correct capacity but RAW, Unallocated, or Not Initialized

Cancel any initialization or format prompt. Microsoft describes initialization as a process for a new disk with no existing data and warns that initializing a disk already in use erases data. A previously working memory card with needed files is not a new empty disk.

If the card is stable, create a sector-level image to another healthy drive before scanning or repair. Do not create a new partition merely to make the card appear in File Explorer.

Zero bytes, No Media, wrong capacity, or repeated disconnects

Stop. These states do not provide recovery software with a stable, correctly addressed source. Trying another recovery application will not make the missing hardware interface appear.

Microsoft’s Disk Management troubleshooting documentation says that a missing or non-initializing disk or memory card can have hardware problems and that failure is a common cause. The label alone does not diagnose the failed component, but it is a reason not to write new metadata.

Step 4: Check macOS Disk Utility without running First Aid

Open Disk Utility, then choose View > Show All Devices. Look for the physical card and its reported capacity, not only a volume name.

If the physical card and correct capacity appear, note any containers, partitions, and file-system status.
If only the reader appears with no usable media, or the card is absent, normal file recovery cannot begin.
Do not click First Aid or Erase on the only copy before preserving the data.

Apple’s Disk Utility guidance says to have a current backup before repair and notes that a storage device missing from Disk Utility may need service. For external media, Apple recommends checking the connection and power path; with an SD card, the equivalent controlled checks are the reader, adapter, and port.

Step 5: Interpret phone, camera, and recorder messages carefully

If the original device says SD card corrupted, card not inserted, unsupported card, or format card, do not accept the prompt while data recovery is the goal.

When the original device can still preview files:

Do not record anything new.
Connect the powered device to a computer if that is the manufacturer’s normal transfer method.
Copy the most important files first to a separate drive.
Verify several photos, videos, documents, or recordings before assuming the transfer is complete.

When the original device cannot see the card but a computer reports the correct capacity, treat the card as a computer-based imaging case. When neither the original device nor two compatible reader paths can identify it, stop software testing.

If Android previously set up the card as internal or adoptable storage, the data may be encrypted and tied to that device. Android’s official file-based encryption documentation explains that adoptable storage can use file-based and metadata encryption. A sector image can preserve the current state, but it does not guarantee that another phone or recovery program can decrypt the files.

The decision table

Current state	Safe DIY action	Recovery software?	Professional help?
One reader fails, but another reads the files normally	Copy and verify files immediately	Usually unnecessary	Usually unnecessary
Correct capacity, stable connection, no physical damage, volume will not mount	Make a sector-level image to another drive	Scan the image, not the only card	Consider if the data is unique
RAW or Unallocated with correct capacity and stable reads	Do not format; image first	Yes, from the image	Consider for high-value data
Zero bytes, No Media, wrong capacity, or absent in every compatible reader	Stop after recording the state	No; there is no stable source to scan	Yes
Cracked, burnt, wet, hot, or intermittently disconnecting	Power down and store safely	No	Yes
Android adoptable storage from a dead or reset phone	Preserve both card and original phone	Software may see encrypted data only	Specialist assessment may be needed

When making an image is the right next step

A sector-level image is a file on another healthy drive that attempts to preserve every addressable block of the card. It is different from copying visible folders, and it is not a recovery result by itself.

Imaging is a reasonable DIY step only when:

The card appears consistently with its correct capacity.
It is not physically damaged or unusually hot.
Reads are stable enough to proceed.
You can identify the source and destination with certainty.
The destination has enough free space for the card’s full addressable capacity.

Use a recovery-oriented imaging tool that can log progress and resume. Do not copy a command from a forum unless you can independently verify every device identifier; reversing source and destination can overwrite the only copy.

Keep the source card disconnected after imaging. If the data is important, retain one untouched master image and scan a duplicate or working copy.

The CGSecurity image documentation explains that TestDisk and PhotoRec can work with a disk image and that the destination must have enough space. The GNU ddrescue manual describes a recovery-oriented copy process and a mapfile that allows work to resume. Both are advanced workflows, not a guarantee that unstable flash media will remain readable.

If the card starts disconnecting, slows dramatically, produces growing read errors, or changes capacity during imaging, stop. A long DIY read may consume the remaining stable access.

When recovery software can help

Recovery software is appropriate only after the card or image is readable with a stable, plausible capacity. It may help with:

Accidental deletion from a healthy card.
An accidental quick format with no later recording.
A damaged file system or lost partition on a stable card.
A card that mounts but has missing folders or files.

Scan the image where possible. Preview several important items before paying, including large videos as well as small photos. A filename, thumbnail, or large “found data” total does not prove that the content is intact.

Always recover to another physical device. For a readable card with deleted photos, follow the deleted SD card photo guide. If the card was formatted but remains stable and detectable, the formatted removable-drive workflow explains the same no-write principle.

Compare data recovery software only after the detection and stability checks are passed. In a stable logical-loss case, a free scan and preview can help decide whether a paid license is useful. In a no-detection case, buying another program does not solve the missing hardware access.

When to stop and use a specialist

Consider a professional flash-recovery service before more DIY attempts when:

No compatible reader or original device can identify the card.
The reported capacity is zero, implausible, or changes between attempts.
The card disconnects during reads or becomes unusually hot.
It is cracked, bent, corroded, wet, or electrically damaged.
It came from an encrypted or proprietary device workflow.
The files are irreplaceable and one failed attempt would be unacceptable.

Do not attempt chip removal, board-level wiring, sanding, heating, or improvised contact work. A specialist first needs to determine whether the problem is the reader path, card controller, internal connection, flash memory, or encryption. Not every failure is recoverable, and no responsible service can promise an outcome before evaluation.

Use the software-versus-professional-service guide to compare risk, not just price.

What recent users are actually asking

Public posts show the language people use in emergencies; they do not establish technical facts or recovery rates.

In one recent SD card case, a 128 GB card first produced a warning and later disappeared from phones and readers. The real question was whether any safe DIY step remained once nothing detected the card.
Another user reported a microSD card that showed “not inserted” in two Android devices despite no visible damage. That distinction matters because visual condition does not tell us whether the host can communicate with the card.
An X post about a corrupted SD card in an MP3 player captures the same first decision: preserve the card before accepting a format or repair path.

These reports support the search intent behind this guide. The safety and technical recommendations come from the primary documentation linked above, not from replies or anecdotes.

Frequently asked questions

Should I format an SD card so the computer can detect it?

No. Formatting creates new file-system structures and can remove directory information. The SD Association’s formatter FAQ says to copy wanted data elsewhere before formatting and explains that overwrite format erases the user data area.

Can recovery software find a card that does not appear anywhere?

No normal file-recovery program can scan a card that the operating system does not expose as a readable device. The card must at least appear stably with a plausible capacity. Kingston’s official support page makes the same distinction between a recognized card that software can scan and an unrecognized card that needs a service path.

Does “No Media” mean the files are already gone?

It means the current reader path is not exposing addressable media. It does not prove why, and it does not establish a recovery outcome. Stop software scans and seek an evaluation if the data matters.

Should I run CHKDSK or First Aid?

Not on the only copy when files are missing. Those tools aim to repair file-system structures, which is different from preserving recoverable evidence. Read why CHKDSK should usually come after data recovery.

Can the lock switch make an SD card safe to scan?

The switch asks a compatible host to block writes. It is useful against accidental writes only when the reader honors it; it is not a substitute for a verified hardware write blocker, and it does not make a failing card stable.

Is a microSD-to-SD adapter part of the card?

No. It is a separate passive adapter and can be the point of failure. One known-good replacement is a reasonable test. Stop if the microSD card remains absent or unstable in a compatible reader.

What if the camera sees photos but the computer does not?

Do not format the card. Stop shooting and copy through the camera’s normal USB transfer path if it remains stable. Verify the files on another drive before doing anything to the card.

Can I reuse the card after recovery?

Do not trust a card that became unreadable, changed capacity, disconnected, or produced unexplained errors as the only copy of future data. Replace it after the recovery question is resolved.

Primary sources

Bottom line

The key question is not which recovery app to buy. It is whether a host can still identify the SD card with the correct capacity and read it stably.

If yes, stop writes, make an image, scan the image, preview files, and recover elsewhere. If no, or if the card is physically damaged, hot, wrong-capacity, or unstable, stop DIY attempts and seek a specialist before the card’s condition changes further.