Some folders on my hard drive suddenly became corrupted after a crash, and now I can’t open important files inside them. I’m trying to recover photos, documents, and work files without making the damage worse. What’s the safest way to recover data from corrupted folders on a hard drive?
I had a near-identical mess with an older external hard drive, and the first thing I learned the hard way was this: stop using the drive right away.
When files vanish, they often are not wiped at once. The data usually sits there until new writes land on top of it. So if you keep copying stuff over, downloading files, or moving folders around, you cut your own recovery odds. I did this once. Bad move.
If you have not checked the simple places yet, do that first. Files sometimes look gone when they are sitting somewhere dumb and easy to miss:
- Recycle Bin
- OneDrive or Google Drive sync folders
- File History backups
- External backup drives
- A different user account on the same PC
If none of those turn up anything, then I’d move to recovery software. For regular deletion, accidental format jobs, or a messed up file system, I’d start with Disk Drill. I used it because the layout was easy to follow and it still handled more than basic undelete stuff. It scans deleted partitions, formatted drives, and damaged file systems without forcing you to learn a pile of recovery terms first.
What worked best for me was keeping the process boring and strict:
- Plug in the drive and confirm the system still sees it
- Install the recovery app on a different drive
- Run a full scan, not the quick one
- Preview files before restoring them
- Pull the important stuff first
- Save recovered files to another disk, never back to the same HDD
That last step matters a lot. If you recover onto the same drive, you risk overwriting data you have not pulled yet. People skip this, then wonder why half the folder comes back broken.
One part of Disk Drill I liked was the preview feature. I did not trust file names alone. If a photo opened and a video played in preview, I took that as a decent sign the file had a shot. I usually tested a handful of key files before dumping hundreds of gigs into recovery.
If it comes back thin, try another tool after. Different recovery engines pull different leftovers. PhotoRec is free and pulls off some wild saves, but it is rougher to use and it often strips original file names. R-Studio and UFS Explorer are solid too, though I found them less friendly if you are not used to this sort of thing.
One place I would stop messing around is hardware failure. If the drive is clicking, grinding, dropping connection at random, or vanishing from BIOS, I would not keep scanning it at home. Software helps with logical problems. It does little for a dying drive mechanism.
At that point, a recovery lab is the safer move, esp if the drive holds family photos, work files, tax records, or anything else you cannot replace. It costs a lot. Still, for some cases, there is no cheaper path left.
Stop mounting and browsing it over and over. That part I disagree on a bit with @mikeappsreviewer. A full scan is not always the first move if the folders got corrupted right after a crash. First, make a sector-by-sector image of the drive and work from the copy. ddrescue on Linux is the usual pick. If the disk has weak sectors, repeated scans hit the same bad spots and make things worse.
After you image it, check the file system damage on the clone, not the original. If this is NTFS, tools like DMDE or R-Studio often rebuild folder structure better than raw photo recovery. Raw recovery gets files back, but names and folder paths are often gone. That sucks for work docs.
If the drive is stable and you want the easy route, Disk Drill is fine for scanning the clone and pulling photos, docs, and videos to another disk. Preview matters. Corrupt previews usually mean partial recovery.
I would avoid CHKDSK on the original drive. People love to suggest it. Bad idea at this stage. It repairs by changing metadata, and I’ve seen it turn damaged folders into found.000 junk. You want recovery first, repair later.
For old hard drive file recovery and corrupted folder recovery, this video is worth a look too, watch this hard drive data recovery walkthrough.
Short version:
- Stop using the drive.
- Clone it first.
- Recover from the clone.
- Save output elsewhere.
- Only run repair tools after you get the important stuff.
If the drive clicks, slows to a crawl, or disconnects, stop. At-home stuff starts getting risky fast.
I’m with @waldgeist on one big thing: don’t “repair” first. But I’m gonna push it a little further. If the folders got corrupted after a crash, there’s a decent chance this is a file system metadata issue, not the files themselves being fully dead. That matters, because raw recovery is kind of the caveman approach. It gets files, sure, but often with garbage names and no folder structure. For work stuff, that’s a nightmare.
What I’d do before throwing every scanner at it:
-
Check SMART/health with something read-only like CrystalDiskInfo.
If health is bad, treat the drive like it’s on life support. -
If it’s an external drive, try a different cable/port/enclosure first.
Sounds basic, but I’ve seen “corruption” turn out to be flaky USB connection weirdness. -
Mount the drive read-only if you can.
This avoids Windows “helping” in all the wrong ways. -
Target the damaged folders first instead of scanning the whole disk forever.
A lot of people go straight to a giant full-disk scan. Sometimes that’s overkill and just wastes time if you already know where the damage is.
If the drive is stable, Disk Drill is a reasonable pick because it handles corrupted hard drive folders and lets you preview recovered photos/docs before you save them elsewhere. I don’t love using only one tool though. Disk Drill first for usability, then something like DMDE if folder structure matters more than convenience. Different tools see differnt things.
Also, do not trust recovered Office/PDF files just because they copy out. Open them. Corrupt docs love to pretend they survived.
If you want more general discussion around file recovery software recs, this thread is decent: best Reddit discussion on file recovery software for hard drives
My short version: image if possible, avoid CHKDSK, test recovered files imediately, and don’t keep rebooting and poking at the bad drive like it owes you money.
One extra angle nobody’s hit hard enough yet: check whether the “corrupted folders” are actually just broken directory entries, not destroyed file contents. I partly disagree with the full-disk-first crowd here. If the drive sounds healthy and SMART is clean, sometimes a metadata-focused tool can list orphaned entries faster than a giant carve.
What I’d try on the clone:
- DMDE to inspect the parent folder records
- TestDisk only for partition or boot sector issues, not blind repair
- Hex-check a few key files if previews fail but size looks right
About Disk Drill:
- Pros: easy UI, good previewing, decent for mixed photos/docs, works well when you want quick triage
- Cons: not my first pick for deep NTFS metadata surgery, can return lots of noise, best results often depend on doing the clone first
So yeah, I’d use Disk Drill after imaging if you want a simpler recovery pass, then verify the critical Office and PDF files manually. @waldgeist is right about avoiding CHKDSK early, @byteguru is right that previews matter, and @mikeappsreviewer is right to separate logical corruption from physical failure. If filenames and folder tree matter a lot, lean DMDE or R-Studio before raw recovery.

