External Drive Not Recognized? Fix RAW, Corrupted & Dead Drives

Published: May 25, 2026 · Updated: May 30, 2026 · By: James Mercer · 12 min read

Disclosure: I only recommend tools I’ve personally tested. Some links are affiliate links — at no extra cost to you, I may earn a small commission.

📑 Table of Contents

1. Why Does Windows Say Not Recognized?
2. Scenario 1: Fixing a RAW Drive
3. Scenario 2: Corrupted Drive Recovery
4. Scenario 3: Resurrecting a Dead Drive
5. Tool Comparison
6. RAW vs Corrupted vs Dead
7. Community Controversies
8. Common Pitfalls
9. FAQ
10. Prevention Tips
11. My Take

It was a Thursday night, around 11 PM. I was exporting a wedding photoshoot — 480 GB of RAW files — when my 4 TB WD My Passport let out a faint click… click… click. Then nothing. Drive letter gone. Windows popped up that dreaded “USB device not recognized” bubble, and my stomach dropped. I’d been there before, and it never gets easier.

If you’re reading this, you’re probably staring at the same error. Maybe your drive shows as RAW in Disk Management. Maybe it’s visible but throws “parameter is incorrect.” Or it just won’t spin up. I’ve dealt with all three — RAW, corrupted, and dead — and I’ll walk you through what actually works. (If you’re looking for backup strategies to avoid this in the future, I cover the full 3-2-1 strategy in a separate guide.)

🖥️ Test Setup (May 2026):
• OS: Windows 11 Pro 24H2 & macOS Sequoia 15.6
• Primary: WD My Passport 4TB (WDBBKD0040BBK)
• Secondary: Seagate Backup Plus 5TB, SanDisk Extreme Pro 1TB
• Tools: DMDE 4.0, R-Studio 9.5, TestDisk 7.2, DiskGenius 5.7, DDRescue
• Tested: May 2026

📌 TL;DR:
RAW drive: Use DMDE or TestDisk to rebuild the partition table. Never format.
Corrupted drive: Create a forensic disk image first, then extract from the image.
Dead drive: Check the USB bridge board — roughly half of dead drives are just a failed bridge.
Golden rule: Recover first, repair second.

Why Does Windows Say External Drive Not Recognized?

An external drive has three layers: the physical media, the controller board, and the USB bridge. Problems at any layer trigger the error. According to Microsoft’s Disk Management docs, a RAW status means the file system signature is missing — not that data is gone.

• RAW drives — Partition table damaged. Data is usually intact underneath.
• Corrupted drives — File system errors, bad sectors, or directory damage.
• Dead drives — No power, no spin, clicking. Usually a hardware failure.

Hot take: most dead external drives I’ve recovered weren’t actually dead. The USB bridge board fails far more often than people realize. I swapped a $12 SATA-to-USB adapter and a “dead” 2TB Seagate sprang back to life with all data intact. Don’t write off a drive until you’ve checked the cheap fixes.Disk Management — Local Disk (D:) — RAWDisk 1RAW (931.51 GB)Basic MBR Healthy (Primary Partition)File System: RAW Status: Failed⚠ You need to format the disk in drive D: before you can use it.Do you want to format it? [Cancel] [Format Disk]Fig 1: Disk Management showing a RAW drive — DO NOT click Format Disk.

Scenario 1: Fixing a RAW External Drive

A RAW drive is the most common failure I see. Windows can’t read the file system signature, but the file data is still there. Tom’s Hardware covers this — and the first warning is always: don’t format.

Step 1: Don’t Panic — and Don’t Format

Formatting wipes the file system metadata that recovery tools need. Always recover first.

Step 2: Identify the Original File System

1. Open Disk Management — note partition size and position
2. Use DMDE to scan the boot sector — it detects NTFS or exFAT

Step 3: Recover the Partition Table

DMDE (preferred): Select physical drive, right-click RAW partition, Open Volume, browse and recover files to a different drive.

TestDisk (free): Run testdisk, select drive, Analyse, Quick Search, press P to preview, Write to restore.

Note: TestDisk struggles with exFAT. Use DMDE or R-Studio for exFAT RAW drives.

Step 4: Rebuild the Boot Sector

• NTFS: chkdsk /f X: can rebuild from backup — but only after files are recovered. Microsoft’s chkdsk reference confirms this. (For a deeper dive into NTFS recovery, I wrote a separate guide on NTFS partition recovery since the process has some specific nuances.)
• exFAT: Never use chkdsk. Use DMDE’s Boot Sector Repair instead.

My rule: NTFS = chkdsk is okay after files are safe. exFAT = never touch chkdsk. I wish more guides made this distinction.DMDE 4.0 — Partition Recovery — WD My Passport 4TB✔ NTFS foundPartition 1: 3,814,726 MBBoot sector: damagedBackup boot: intact→ [ Restore backup BS ][Volume preview] → D:\Photos\Wedding\DSC_4821.ARW 42.1 MB ✓DSC_4822.ARW 38.7 MB ✓DSC_4823.ARW 41.3 MB ✓… 1,247 files foundFig 2: DMDE detects an intact NTFS backup boot sector.

Scenario 2: Recovering Data from a Corrupted Drive

A corrupted drive is a spectrum: directories throw “corrupted and unreadable,” or files copy halfway and fail with CRC errors.

Step 1: Diagnose the Level

• Mild: Windows prompts “Scan and fix.”
• Moderate: Specific files show CRC errors.
• Severe: Explorer freezes when accessing the drive.

Step 2: Image the Drive First

1. Use DMDE or R-Studio: Tools, Copy Sectors, enable Skip bad sectors. (I walk through forensic disk imaging step-by-step here — including how to handle bad sector maps.)
2. Save image to a healthy drive (6-12 hours for 2TB). Use an external SSD or NAS as the target — never save to the same physical drive.
3. Work exclusively on the image file. Mount it as a virtual disk in R-Studio or DMDE.

Real-World Case from Reddit

A user on r/datarecovery shared: “Plugged it in the next day and Windows kept asking to format. Tried chkdsk and it got stuck at 11% for hours.” — This is why you image before you repair.

Step 3: Recover from the Image

1. Open the image in R-Studio or DMDE
2. Scan — both support raw file carving if the directory is too damaged
3. Preview files, recover to another healthy drive

Deep Dive: Raw File Carving in R-Studio

When the file system directory is beyond repair, raw file carving is your only shot. R-Studio’s “Full Scan” mode inspects every sector for known file signatures — everything from JPEG headers (FF D8 FF E0) to ZIP local file headers (PK 03 04). Here’s the process I use:

1. Mount the image in R-Studio by clicking Drive → Open Image File. Select your DDRescue or DMDE image.
2. Select the partition — if unreadable, scan the entire image. Right-click and choose “Scan for Known File Types.”
3. Configure carving parameters: Enable all known signatures, set minimum file size to 1KB (anything smaller is probably false positives). R-Studio lets you add custom signatures if you know the exact file type you’re after — useful for specialized formats like .psd or .dwg.
4. Let it run — expect 2-6 hours per TB. R-Studio’s extended scan checks 4,000+ file signatures. I’ve recovered SQL database files (.mdf) that no other tool could find using this method.
5. Filter results by type and status. Green indicators = complete file. Yellow = partial (file is fragmented). Red = insufficient data for recovery. For critical files, even yellow partials can yield usable data — try opening them and see.
6. Recover to a separate drive — never write recovered files back to the same image. I use a scratch SSD for this.

DMDE’s “Full Scan” works similarly but is noticeably faster on NTFS drives. Trade-off: it identifies fewer file signatures than R-Studio (~2,000 vs ~4,000). TestDisk doesn’t do file carving at all — it’s purely for partition structure recovery.

Critical: If your drive has bad sectors, do not run chkdsk /r on the original. It hammers each sector and can push a failing drive past recovery.

Scenario 3: Resurrecting a Dead Drive

A drive that doesn’t spin is terrifying. But dead doesn’t always mean the platters are damaged.

Check the Low-Hanging Fruit

1. USB Bridge Board (~50% of dead drives): Open the enclosure. If there’s a standard SATA port, remove the drive and connect directly. If it spins up, replace the enclosure for $10-15. (I’ve tested and compared enclosures here — not all USB bridge boards are replaceable.)

Pro Tip: WD My Passport (2021+) has USB soldered directly — no SATA. You’ll need an HRM-202 adapter. Seagate Backup Plus (pre-2023) still uses standard SATA.

How to Tell If the Bridge Board Is the Culprit

Not every dead drive has a failed bridge. Here’s my decision tree from hundreds of repairs:

• Drive detected in BIOS/Device Manager but not Explorer: Strongly suspect the bridge board. The drive is communicating externally but the translation layer (USB-to-SATA) fails during file system access. Try direct SATA first.
• Drive spins up but USB LED stays off: The bridge board is getting power but the data channel is broken. Swap the board or enclosure.
• Drive detected with a different model string (e.g., “Marvell Bridge” instead of “WD My Passport”): The USB bridge is returning its own identity instead of passing through the drive’s identity. Clear sign of a failed board.
• No detection at all — no spin, no LED: Likely a power issue. Test another cable and port before blaming the drive. If still dead on direct SATA power, the drive’s PCB or motor is gone.
• Drive makes a brief spin-up then stops: Stiction — the heads are stuck to the platter. This is not a bridge problem. Professional recovery required.

I keep a drawer of old USB enclosures specifically for testing bridge boards. If a drive doesn’t work in one enclosure but works in another, the bridge was the culprit 100% of the time.

2. Power Supply: Test the adapter. Try a different USB cable. Avoid USB hubs.

The Clicking Drive

Spiceworks recommends stopping power immediately for clicking drives. A Tom’s Hardware Forums user recently shared a case where their 4TB WD Elements started clicking after a power surge: “The drive was detected in BIOS but Windows couldn’t read it. I assumed the drive was dead.” In their case, swapping the USB bridge board brought it back. Here’s my process:

1. Stop powering it — every click risks head damage
2. If you must try: connect via direct SATA
3. If it still clicks: professional lab ($500-$3,000+)
4. For dead SSDs: the controller chip usually fails, not the NAND

I’ve sent exactly two drives to a recovery lab in five years. One was a 4TB WD with a head crash — you could hear the platter scraping. The other was a Samsung T7 with a cracked controller from a drop. Both cost over $1,000. Was it worth it? One had three years of architectural blueprints. The other had a PhD dissertation. In both cases, the clients cried when they got their data back. But for most people? Clicking = replace and restore from backup.🔌 USB Bridge Board(JMicron JMS578)✔ SATA connector here✘ USB port (likely failed)SATA cable→ to PCFig 3: The USB bridge board — the most common failure point in dead drives.

Which Data Recovery Tool Should You Use?

My recommendation priority by use case: If you’re a home user with a single failed drive, start with TestDisk (free, fast partition repair) → DMDE Free (file extraction up to 4,000 files) → only then consider paying for DMDE Full ($48). For professionals or multiple drives, R-Studio ($79.99) pays for itself quickly — the raw file carving alone recovers files nothing else can find. For imaging failing drives, DDRescue is mandatory regardless of what you use for recovery — always image first, recover second. DiskGenius sits in the middle: good interface, decent features, but not best-in-class at anything. I only recommend it for beginners who find R-Studio intimidating.

RAW vs Corrupted vs Dead — At a Glance

⚡ Data Recovery Decision FlowDrive not recognizedCheck Disk MgmtRAW? → DMDECorrupted?Image + RecoverDead / No spin?Check bridge board⬆ Always: Recover first → Repair second. Never write to the failing drive.Fig 4: Quick decision flow — identify the failure before choosing your tool.

Community Controversies

The data recovery community is divided on key points.

#1: Should You Ever Run chkdsk on a RAW Drive?

Half say never, half say only on NTFS. I’m in the second camp — but only after data is recovered. Beginners don’t know their original FS. If you run chkdsk on exFAT, you destroy the backup boot sector. This r/datarecovery thread captures the debate.

#2: Should You Freeze a Failing Drive?

This old trick refuses to die. The professional consensus: don’t do it. Condensation causes more damage. It might have helped pre-2010 drives with seized spindles. On modern fluid dynamic bearings? You’ll destroy it.

#3: Free vs Paid Software

Free tools like TestDisk are incredibly capable but require technical comfort. In my experience: for NTFS, free tools match paid 95% of the time. For exFAT and fragmented drives, paid tools pull ahead.

Common Pitfalls to Avoid

• ❌ Formatting a RAW drive immediately — Erases partition metadata. Recover first.
• ❌ Running chkdsk /r on bad sectors — Can kill a salvageable drive. Image first.
• ❌ Continuing to power a clicking drive — Every second risks permanent head damage.
• ❌ Writing recovered files back to the same drive — Use a separate drive.
• ❌ Using free recovery software from shady ads — Most install malware.
• ❌ Opening a dead drive to see what’s wrong — Dust scratches platters.

Frequently Asked Questions

Can I recover data from a drive that won’t spin?How is RAW different from corrupted?Is chkdsk safe for external drives?Best free recovery tool?Can I fix a clicking drive myself?Does formatting fix a RAW drive?Drive in Device Manager but not Explorer?Professional recovery cost in 2026?Water-damaged drives recoverable?FAT32 vs exFAT vs NTFS?Recovery software on bad sectors?

How to Prevent This

The best recovery is the one you never need. Most external drive failures I’ve seen are preventable with three habits: keep a second copy of your data, don’t fill drives past 80%, and replace your drives every 3-4 years before they fail. Here’s what I actually do after recovering data from hundreds of drives — plus I compiled everything into a full maintenance checklist you can follow.

• 3-2-1 made simple: Keep on PC (1), external backup (2), cloud for critical (3). Backblaze $99/year.
• Don’t fill past 80%. Drives above 90% fail more often.
• Always safely eject. Sudden disconnects are the #1 cause of corruption.
• Replace every 3-4 years. A $100 drive is cheap insurance.
• Listen to your drive. Unusual noises = warning. Copy data off immediately.

📥 Download the Quick Reference Card
One-page PDF with the three-scenario decision flow.
Download Free PDF →
Join 5,000+ subscribers: Subscribe →

⚖️ Testing Independence: All tools purchased with personal funds. No manufacturer provided free licenses or sponsored content.

My Take / Personal Experience

After a decade of recovery work, I’ve learned that recovery is 80% patience and 20% tools. I once ran chkdsk on a client’s dying 3TB drive because I was in a hurry — it turned a salvageable situation into a $2,000 lab recovery. That lesson stuck.

The hardest part isn’t the technical work — it’s managing expectations. People bring me a drive that’s been in a drawer for two years expecting a miracle. What I know: if you stop using the drive the moment you notice a problem, your chances of full recovery are 90%+. Every write operation reduces those odds.

My honest advice: buy an external drive for backups, not primary storage. Set up automated cloud backup for irreplaceable files. And if your drive fails? Take a deep breath, put it aside, and follow the steps above.

About the Author

James Mercer is a data recovery specialist with over 12 years in digital forensics. He has recovered data from over 2,000 failed drives and holds GCFE and SNIA SCSE certifications. He has contributed to Tom’s Hardware and Spiceworks since 2016.

🔗 Full bio · LinkedIn · YouTube

Disclosure: Some links are affiliate links. Originally published May 25, 2026. Last updated May 30, 2026.