Corrupted External Drive: How to Recover Your Data Safely

You plug in an external drive and Windows says you need to format it before use. Or the drive shows up as RAW, or half the folders are gone. A corrupted external drive looks scary, but in most cases the data is still on the disk and only the file system structures are damaged. The order in which you act decides whether you get the files back, so follow the steps below in sequence.

Stop writing to the drive

Do not copy new files to the drive, do not save anything on it, and do not click Format. Every new write can overwrite the areas where your lost files still live. Treat the drive as read-only evidence until you have copied your data somewhere else.

Logical or physical problem?

Most failures are logical: a damaged file system, a corrupted partition table, or a drive that was unplugged during a write. The typical signs are a “you need to format the disk” prompt, a RAW file system in Disk Management, missing files, or garbled file names. Physical failure looks different. Clicking or grinding noises, a drive that does not spin up, or a drive that was dropped or got wet all point to hardware damage.

If you see any physical symptom, disconnect the drive and skip to the section about recovery labs. Running repair tools on failing hardware makes things worse.

Check the basics first

Many “corrupted” drives turn out to be a cable or port problem. Plug the drive straight into a USB port on the PC, not into a hub, try a different cable, and test it on another computer. If the drive is BitLocker encrypted, Windows will ask for the password or recovery key, which is not corruption at all.

Then look at how Windows sees the drive. Run this in PowerShell:

Get-Disk
Get-Volume

Check that the disk is online, and that the volume has a drive letter and a file system. If the drive letter is missing, you can assign one in Disk Management with Change Drive Letter and Paths. If the drive is listed but shows no usable file system, continue with the next steps.

Scan the drive without repairing it

You can ask Windows to scan the volume without changing anything by using the Repair-Volume cmdlet in scan mode:

Repair-Volume -DriveLetter E -Scan

Replace E with your drive letter. The result tells you whether Windows found file system errors, and it does not attempt a repair. It will not work on a RAW volume, which is itself a useful finding, because it means the file system structures are not readable.

Recover the files before you repair anything

Repair tools change data on the volume, so rescue the files first. The destination must always be a different, healthy drive, never the corrupted one.

Microsoft provides a free command-line tool for this called Windows File Recovery. Install it from the Microsoft Store, open an elevated Command Prompt, and use the syntax winfr source-drive: destination-drive: /mode /switches. According to Microsoft, a corrupted NTFS disk needs extensive mode, and FAT and exFAT drives are also only supported in extensive mode. A typical run looks like this:

winfr E: D: /extensive /n *.docx /n *.xlsx /n *.jpgCode language: JavaScript (javascript)

The tool writes the recovered files into a Recovery folder with a date and time on the destination drive. The source and destination drives must be different, so make sure D has enough free space.

If you prefer a graphical tool, commercial recovery programs exist, and open-source options such as TestDisk and PhotoRec are popular with admins. Whichever you choose, apply the same rules: scan only, preview files before you recover them, and save to another drive. If the drive throws read errors, consider making a full image of it first (for example with GNU ddrescue on Linux) and running the recovery against the image instead of the failing disk.

Repair the corrupted external drive with chkdsk

Once your files are safe, you can try to repair the file system. Open an elevated Command Prompt and run:

chkdsk E: /r

According to the Microsoft chkdsk reference, /r includes the functionality of /f and adds an analysis of physical disk errors, and /x also includes /f. That means the commonly copied command chkdsk E: /f /r /x repeats itself. Use /x only if the volume is in use and Windows needs to dismount it first.

Be aware of two limits. First, chkdsk reads the whole disk when you use /r, which can take hours on a large drive and puts load on weak hardware. Second, chkdsk does not work on a RAW drive and will report that the command is not available for RAW drives. In that case, rely on the recovery step above and then reformat.

Reformat only as the last step

If chkdsk cannot fix the drive and you have confirmed your files are safe on another disk, format it. In Disk Management, right-click the volume, choose Format, and pick a file system. NTFS is the better choice if the drive stays on Windows. exFAT works on Windows and macOS. You can also do it from PowerShell:

Format-Volume -DriveLetter E -FileSystem NTFS -NewFileSystemLabel "Backup"Code language: JavaScript (javascript)

A quick format is enough. Keep in mind that a drive which became corrupt once may have a hardware issue, so do not use it as your only copy of anything important.

When to call a recovery lab

Stop using the drive and contact a professional recovery service if it makes clicking or scraping sounds, does not spin up, was dropped, or was exposed to liquid. These cases can involve damaged heads or platters, and the work belongs in a clean room. Powering the drive on again and again only increases the damage.

How to avoid this next time

Use Safely Remove Hardware before you unplug a drive, because pulling it during a write is a classic cause of file system corruption. Follow the 3-2-1 backup rule: three copies, on two different media, with one copy off site or in the cloud. Also replace old drives before they fail. SMART data can help, but many USB enclosures do not pass it through, so treat a clean result as a hint and not a guarantee.

Read more: How To Classic Right-Click Menu in Windows 11

References

• Microsoft Support: Windows File Recovery
• Microsoft Learn: chkdsk command reference