Memory card suddenly read-only: what to check before replacing it

A camera displays “Card locked.” Windows says the disk is write-protected. Existing photos still open, but no new file can be saved and formatting fails. Those symptoms look identical to the user, yet they can come from four different layers: the adapter, the reader, the operating system or the flash controller.

The first move is not formatting. Copy every readable file to another device. Read-only operation can be the card's last useful state before complete failure.

Full-size SD has a lock tab; microSD does not

SD Association's form-factor comparison lists a write-protect switch for full-size SD and none for microSD [1]. The full-size card's side tab is also unusual: it does not electrically lock the NAND. The SD specification says a matching switch in the socket reports the tab position to the host, and the host is responsible for respecting it; the card's internal circuitry does not know the slider position [2].

That explains two common cases:

• a loose full-size SD tab slides toward Lock when inserted;
• a microSD is fine, but its microSD-to-SD adapter or the reader's detection switch is faulty.

Remove and reinsert the card, move the tab fully to the unlocked position, and test with a known-good adapter or direct microSD reader. Do not tape a broken switch and return the assembly to field use; replace the adapter.

Separate the four possible layers

Use a controlled sequence instead of trying random “unlock” utilities.

Change one variable at a time. If the card works in a second reader, repeatedly formatting it will not repair the first reader.

When a Windows read-only attribute is the cause

Microsoft documents DiskPart's attributes disk command for displaying, setting and clearing the read-only attribute [4]. This can help when Windows metadata or an administrative action—not the card hardware—marked the disk read-only.

There is a serious trap: DiskPart operates on the selected disk. Selecting the wrong number can damage another drive. Identify the removable card by capacity, confirm it again, and copy data before changing anything.

Clearing an OS attribute is a diagnostic step, not proof the card is healthy. If the attribute returns, writes fail, or another host also sees read-only media, stop treating it as a Windows-only problem.

A controller can protect worn or corrupted flash

Managed flash contains a controller that maps logical addresses to physical NAND and replaces failed blocks with reserved ones. SanDisk documents a protective behavior in which a card may write-protect itself after the number of good blocks falls below a preset threshold. It also describes protection when critical internal copies become corrupted [3].

In that state, refusing new writes is useful: the controller is trying to preserve access to data that can still be read. A registry edit or attribute command cannot replenish physical spare blocks.

Warning signs include:

• read-only state follows the card across readers and operating systems;
• formatting starts but fails, or the old files reappear afterward;
• capacity changes, I/O errors appear, or files become unreadable;
• the card came from a continuous-write camera and has accumulated heavy overwrite cycles.

Recover what you can and retire the card. For the broader failure paths, see why memory cards fail and how to recover data.

Formatting is a test, not a cure-all

After backup, formatting may resolve a damaged filesystem or nonstandard layout. Use the camera's recommended procedure or the official SD Memory Card Formatter for SD media. If a full overwrite format is attempted, remember that it is destructive and writes the user area; it is inappropriate before recovery.

A successful quick format is not enough for qualification. Write and verify the full usable capacity, then retest after safe removal and reinsertion. Our full-capacity verification procedure explains the difference between a directory that looks empty and storage that has actually passed a write/read check.

If protection returns, replace the card. A device that needed repeated “unlocking” is not suitable for a dashcam, drone, security camera or any job where the next write matters.

What resellers should capture on a return

Do not log only “card locked.” Record:

1. card model, capacity, lot and serial/trace code;
2. host device, firmware and recording mode;
3. whether a full-size adapter was used;
4. result in a second known-good reader and host;
5. whether existing data remained readable;
6. whether the read-only state survived power cycle and reinsertion;
7. approximate workload and service time;
8. full-capacity test result, only after customer data is secured.

This separates accessory faults from true media wear and exposes lot-level patterns that a one-line return reason hides.

Bottom line

“Write-protected” does not automatically mean a software lock. Check the full-size SD tab or microSD adapter first, then the reader, host and OS attribute. If the same card remains read-only everywhere, prioritize recovery and replacement: the controller may be preserving the last readable copy of the data rather than asking for another format.