Fix ERROR_UNRECOGNIZED_MEDIA (0x000006F9) on a USB or SD card
This error means Windows can't figure out the file system on your drive. The fix is usually driver-related or a quick diskpart cleanup. I'll walk you through it step by step.
What's happening here
Error 0x000006F9 pops up when you plug in a USB stick, SD card, or external hard drive and Windows throws a fit — it can't recognize the media's file system. You'll see it in Disk Management as "No Media" or "Unknown" with 0 bytes. The core issue is the OS can't read the partition table or the disk's internal metadata. This isn't a hardware failure 90% of the time — it's a driver or partition table corruption problem.
I've seen this most often with cheap USB 3.0 flash drives on Windows 10 after a bad eject, or with SD cards pulled from a camera mid-write. Let's fix it.
30-second fix: Reinstall the USB driver
Don't skip this. It's stupidly simple and works more often than you'd expect. The driver stack for USB mass storage gets confused sometimes — especially after a power event or sleep cycle.
- Open Device Manager (Win + X → Device Manager).
- Expand Universal Serial Bus controllers.
- Right-click Generic USB Hub (there might be several) and select Uninstall device.
- Also uninstall USB Root Hub entries — all of them.
- Restart your PC. Windows will reinstall the drivers on boot.
Why this works: Uninstalling the hub forces the OS to rebuild the driver stack from scratch. It clears any stale cached descriptors that might be telling Windows "this disk has no media." The error 0x000006F9 is often a driver-side misinterpretation, not a hardware failure.
If the error's gone, great. If not, move on.
5-minute fix: Diskpart — clean and reformat
If the driver reinstall didn't cut it, the partition table on your drive is likely corrupted. This happens when the drive isn't ejected properly. The safest way to fix it is to wipe the partition table completely and start fresh.
Warning: This deletes all data on the drive. Back up anything you can first — though if you're seeing this error, chances are Windows couldn't read the data anyway.
diskpart
list disk
select disk X (replace X with your USB/SD card number — double-check the size!)
clean
create partition primary
format fs=ntfs quick (or fat32 if it's under 32GB or for a camera)
assign
What's actually happening here: The clean command wipes the master boot record (MBR) and partition table. It doesn't erase the actual data — it just removes the index. Windows then sees a blank disk and can create a fresh, valid partition. The format step writes a new file system header that the OS can read.
After this, your drive should appear in File Explorer with the correct capacity. If it still shows as unreadable, the drive might have physical bad sectors or a failing controller — but try the advanced fix first.
15+ minute fix: Low-level format and firmware check
If diskpart didn't work, we're looking at something deeper. Could be bad sectors, a corrupt controller firmware, or a drive that needs a full zero-fill.
- Zero-fill the drive: Use a tool like HDD LLF Low Level Format Tool (free version works for up to 180GB). This writes zeros to every sector, bypassing the file system layer. It can take 30 minutes to 2 hours depending on drive size. After zero-fill, run diskpart clean again.
- Check the USB controller chip: Some cheap flash drives use counterfeit controllers that report bogus metadata. If the drive was working before and suddenly throws 0x000006F9, the controller firmware may have crashed. You can try flashing the correct firmware — but that's risky and model-specific. I'd recommend just replacing the drive if step 2 fails.
- Test on another machine: Plug the drive into a different PC or a Mac. If it's recognized there, the issue is your Windows USB driver stack — reinstall chipset drivers (Intel/AMD). If it's not recognized on any machine, the drive is dead.
The reason step 2 is last: A zero-fill forces the controller to verify every sector. If the controller fails during the write, the tool will report errors — that's a definitive sign of hardware failure. You don't want to waste time on software fixes for a physically dead drive.
When to give up and buy a new drive
If you've done all three steps and still see 0x000006F9, the NAND flash chips are likely worn out or the controller has failed. A 64GB USB 3.0 drive costs under $15 now. Is your time worth more than that? Usually yes.
One last thing — if this keeps happening with the same type of drive (e.g., generic unbranded sticks from Amazon), stop buying those. They use the lowest-bin flash chips and will fail again. Spend an extra $5 on a Samsung or SanDisk. Your data's worth it.
Was this solution helpful?