USB Flash Drive Repair: Recover Files From a Dead or Corrupted Drive (2026)

You plug in your USB flash drive and nothing happens. Or Windows pops up "You need to format the disk in drive E: before you can use it." Or the stick shows up but reports 0 bytes. Before you click anything, understand this: in most cases the files are still physically on the NAND chip. What's broken is the path to them — and a wrong move in the next few minutes is what actually loses data, not the original fault.

This guide separates the two things people lump together as "repair": getting your files back, and getting the drive working again. Always do them in that order.

First, the only rule that matters: stop writing

A USB flash drive stores your files in flash memory cells, indexed by a filesystem (usually FAT32 or exFAT) and a controller chip that translates between USB and the raw NAND. When the index breaks, the cells still hold your data — until something writes over them. So before anything else:

• Do not accept Windows' offer to format the drive.
• Do not run chkdsk /f yet (it writes to the drive).
• Do not copy new files onto it "to test."

Get the data off first. Repair second.

The four ways a USB flash drive fails

Knowing which failure you have decides whether this is a five-minute fix or a lab job.

Logical / filesystem corruption is by far the most common and the most recoverable. The drive is detected, but Windows can't read it: it shows as RAW, asks to be formatted, or opens to "the file or directory is corrupted." Cause is almost always unsafe removal — pulling the stick mid-write, or before the OS flushed its cache. The NAND is fine; the filesystem index is scrambled. Recovery software reads the cells directly and reconstructs the files.

Write protection / read-only mode. The drive mounts and you can read it, but you can't delete, copy to, or format it. Two sources: a physical lock switch on the side of some sticks, or a software/firmware flag. The firmware version is sometimes a self-protection state the controller enters when it detects worn-out memory — a warning that the drive is near end of life.

Controller / firmware failure. The little chip that runs the drive dies or loses its firmware. Symptoms: the drive isn't detected at all, shows 0 bytes, reports a wrong capacity, or appears as a generic device that can't be opened. The NAND may be perfectly intact, but software on your PC can't reach it because the controller won't talk. This is where consumer recovery stops and specialist tools (or a lab) begin.

Physical damage. A snapped connector, a cracked PCB, water, or heat. If the metal USB plug is bent or wobbly, the solder joints on the board may be cracked — sometimes a re-seat or re-solder by a repair shop restores contact. If the NAND chip itself is damaged, only a chip-off recovery in a lab can help.

Step 1 — Rule out the cheap causes (2 minutes)

Before assuming the drive is dead, eliminate everything around it:

• Try a different USB port — ideally a port directly on the motherboard's rear panel, not a front-panel header or an unpowered hub.
• Try a different computer. A drive that's invisible on one machine and fine on another is a port/driver problem, not a drive problem.
• Inspect the connector under a light. Bent pins, lint packed into the plug, or a connector that wiggles loosely all cause "not detected."

If the drive now works, copy your files off immediately and stop trusting it for anything important.

Step 2 — Check Disk Management, not just File Explorer

File Explorer hides drives it can't mount, which makes a recoverable drive look dead. Press Win+X → Disk Management and look for your stick:

• Shows as RAW or "Unknown," or has no drive letter: the filesystem is corrupted. Your data is there. Go to Step 3 — do not format.
• Shows the right size with a healthy partition but no letter: right-click → Change Drive Letter and Paths → assign a letter. Sometimes that alone fixes a drive letter conflict.
• Shows 0 bytes / "No Media" / wrong capacity: controller or firmware failure. Software recovery may still work (try Step 3); if not, you're into specialist territory.
• Doesn't appear at all, on any PC: the controller is almost certainly dead. Skip to "When it's a lab job."

Step 3 — Recover the files before any repair

This is the step that actually saves your data. Recovery software scans the flash memory at the sector level, ignoring the broken filesystem, and rebuilds your files by their signatures. The cardinal rule: install it on your PC, never on the USB drive you're recovering, and restore to a different drive.

EaseUS Data Recovery Wizard is the tool we point most readers to for USB sticks: it scans FAT32/exFAT flash media reliably, previews files before you pay, and lets you filter by type so you can grab your photos or documents without waiting for the full scan. Run the quick scan first; if your files aren't listed, run the deep scan, which analyzes every sector for known file headers.

If the quick scan finds your files, preview a few to confirm they open, then restore everything to your internal drive or another USB stick. If even the deep scan finds nothing and Disk Management showed 0 bytes, the controller is blocking access — software can't get past it.

For a wider comparison of tools and when a free one is enough, see our guide to the best data recovery software of 2026 and the free options worth trying first.

Step 4 — Fix write protection

If the drive is read-only:

1. Look for a tiny lock switch on the side of the stick and slide it off.
2. If there's no switch, clear the software flag. Open Command Prompt as Administrator and run:

diskpart
list disk
select disk N        (N = your USB drive — check the size carefully)
attributes disk clear readonly
exit

Picking the wrong disk number here can target your system drive, so confirm the capacity matches your USB stick before select. If the read-only state returns immediately after clearing it, the controller has locked the drive permanently because the NAND is worn out — copy your data off and replace the stick.

Step 5 — Repair the drive for reuse

Only after your files are safe:

• Quick format from Disk Management or File Explorer rebuilds a clean FAT32/exFAT filesystem. This is enough for a logical fault.
• If errors persist after a format, run chkdsk E: /f (now that your data is backed up) to repair filesystem structures, or do a full format (uncheck "quick") to test every sector.
• A drive that keeps corrupting after a clean format is failing at the hardware level. Stop using it for anything you care about.

When it's a lab job — and when to let go

If Disk Management shows nothing on any computer, or the drive reports 0 bytes and recovery software can't see a partition, you've reached the limit of DIY repair. The realistic options:

• Manufacturer mass-production / firmware tools exist for specific controller chips, but they're controller-exact, poorly documented, and they typically erase the drive in the process — useful for reviving a dead stick for reuse, not for recovering data.
• Chip-off recovery in a professional lab desolders the NAND chip and reads it directly. It works even on snapped or controller-dead drives, but it's expensive and only worth it for genuinely irreplaceable data.

For most people, a $10 flash drive is not worth a lab fee — the lesson is the backup, not the repair. If the data on it mattered, set up an automatic backup so this never costs you again, and treat USB sticks as transfer media, never as the only copy.

The honest limitation

Flash memory has a finite number of write cycles, and cheap USB sticks have minimal wear-leveling and no real error correction. A drive that has started corrupting files, returning, or flipping to read-only is telling you it's near the end — no repair makes a worn-out stick trustworthy again. Recover what's on it, then retire it.