This is my own hard drive. Not a borrowed one, not an office drive — mine. And I've formatted it more times than I can count over the years.
So when I plugged it in one day and saw that one specific folder was throwing this error —
"The file or directory is corrupted and unreadable."
— while every other folder opened perfectly fine, I wasn't just confused. I was genuinely concerned. Because that folder had files I actually needed.
The weird part wasn't the error itself. It was that it was only one folder. Everything else on the same drive was accessible. The drive wasn't dead. The other files were fine. Just that one folder — sitting there, refusing to open, like it decided to retire without telling me.
This is what I did about it — and it worked.
Why Does This Happen to Just One Folder?
Good question. A few things can cause a single folder to corrupt while the rest of the drive stays intact:
The folder's file system entry gets damaged — usually from an improper shutdown, a sudden power cut, or the drive being disconnected while Windows was still writing to it. The rest of the drive is fine because the corruption is isolated to that specific directory entry.
It can also happen after multiple format cycles on the same drive — which in my case was definitely a factor. Every format, every reuse, every time files are written and deleted — it adds wear to the drive's file allocation table. Eventually something breaks. In my case it was just that one folder.
The fix is the same command that saves corrupted USB drives — chkdsk — but the context matters. This is a full external HDD, not a flash drive. The scan takes longer and the stakes feel higher because there's usually more data involved.
Before You Run the Fix — Do This First
If the files inside that corrupted folder are important — back up everything else on the drive first. The chkdsk command is safe and designed to repair, not delete. But when dealing with a drive that's been formatted multiple times and is showing file system errors, it's better to be cautious.
Copy whatever accessible files you can to another location before you run anything. Then proceed.
The Fix — Step by Step
This works on Windows 10 and Windows 11.
Step 2 — Open Command Prompt as Administrator. Click the Start button, type CMD in the search bar. When Command Prompt appears, right-click it and select "Run as administrator." This is not optional — the repair command requires admin access to work.
Step 3 — Type the command.
chkdsk /f E:
Replace E: with your actual drive letter. Then press Enter.
Step 4 — Wait for it to finish. Unlike a USB drive which scans quickly, a full external HDD takes longer — anywhere from a few minutes to 20 minutes or more depending on the drive size and how many errors it finds. Let it run completely. Don't close the window.
Step 5 — Check the folder. Once finished, open File Explorer and try accessing that folder again. In most cases the folder becomes accessible and your files are intact.

What If the Folder Is Still Inaccessible After chkdsk?
If chkdsk ran successfully but the folder still won't open, there are a few more things to try.
Try taking ownership of the folder. Sometimes a corrupted folder loses its permission settings. Right-click the folder, go to Properties → Security → Advanced → Change Owner. Set it to your Windows username and apply. This sometimes unlocks a folder that chkdsk couldn't fully repair.
Try Recuva for file recovery. If the folder itself is unrecoverable but you need the files inside, Recuva is a free data recovery tool that can scan your drive and retrieve files even from corrupted directories. It's not 100% guaranteed, but it recovers a surprising amount. Download it from piriform.com — it's free and safe.
Consider the drive's age and format history. If you've been formatting the same drive repeatedly over several years, the drive itself may be developing physical issues beyond what software can fix. A drive that's been reformatted many times and is now showing file system errors is telling you something. Start backing up regularly and consider replacing it before it fails completely.
The Lesson I Learned From This
A hard drive that's been formatted multiple times is not the same as a new hard drive. Every write cycle, every format, every reuse puts wear on the drive — especially traditional spinning HDDs. The file system errors that eventually appear are usually the first sign that the drive is aging.
My fix worked. The folder came back. But after that experience I started taking backup more seriously — because a drive that shows one corrupted folder today can show a completely inaccessible drive tomorrow.
As I mentioned in my USB flash drive repair post, the chkdsk command is your first line of defense for file system errors on any Windows storage device. Same command, same logic — just a bigger drive with more to lose.
Mavs' Final Diagnosis
One corrupted folder on an otherwise working drive is fixable in most cases. Don't panic, don't reformat — run chkdsk first and give Windows a chance to repair it.
But take it as a warning sign too. If your drive has been around for a while and is starting to show these errors — start backing up now, not later. External drives are not forever. Neither is the data on them unless you have it somewhere else.
Did this fix work for you? Or is your situation different — like the whole drive being inaccessible, not just one folder? Drop it in the comments and let's troubleshoot together.
![[SOLVED] One folder on external drive is not accessible (The file or directory is corrupted and unreadable.) [SOLVED] One folder on external drive is not accessible (The file or directory is corrupted and unreadable.)](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhRz0XiyiTLP4lGO2vcQM9BUfODxbMMs5ohv89F3BptD6eFqQqR8asnkOfqcYiBbnpbYFQOb7_ZQ5kdIYCDzkwfgJCq6_gecMdAiUS8kSg1xhPBUzmy99L7dLkMIbtNIIsWEoKOMJjYYm9PH7R56ac2bhyphenhyphenYErOO0LGIjO9Ue9Rso-r8Ll9teVy62gqbfEQ/w640-h336-rw/%5BSOLVED%5D%20One%20folder%20on%20external%20drive%20is%20not%20accessible%20(The%20file%20or%20directory%20is%20corrupted%20and%20unreadable).jpg)

0 Comments