The drive shows up. The letter is assigned. Everything looks fine — until you double-click it. Then File Explorer goes white, says “Not Responding,” and the whole computer feels like it’s wading through mud. Sometimes it recovers after two minutes. Sometimes it never does.
This is one of the more diagnostic symptoms there is. It’s not a software problem, and it’s not ambiguous.
What’s happening
When a hard drive hits a sector it can’t read, it doesn’t fail instantly. It retries — repositioning the head, waiting for another rotation, trying again — often for several seconds per sector before reporting failure to the operating system.
Windows, meanwhile, is patient. The storage stack waits on that request. Explorer waits on the storage stack. And because Explorer runs a lot of the desktop, the whole shell appears frozen while a single struggling sector gets hammered somewhere inside the drive.
A folder that takes thirty seconds to open is a folder whose metadata is spread across several sectors, a few of which are dying.
Why browsing makes it worse
Opening a folder in Explorer isn’t a light operation. It reads directory entries, then generates thumbnail previews — which means opening every image and video file in that folder to render a preview. Point Explorer at a photo folder on a failing drive and it will dutifully read thousands of files across the exact media that can’t handle it.
Windows Search indexing, antivirus scanning, and any backup software watching that volume are all doing the same thing in the background, continuously, whether or not you have a window open.
So the drive isn’t just slow. It’s under sustained load from four directions, and every retry cycle on a weak sector is wear you can’t get back.
What not to do
Don’t keep browsing to “see what’s still there.” Every folder you open is more reads across degrading media. Inventory the drive after it’s imaged, not before.
Don’t run chkdsk /r. It forces a read on every sector on the disk, retrying each bad one. On a drive already taking seconds per sector, that’s a scan measured in days at maximum stress. It’s the most common way this category of drive dies for good. More here.
Don’t defragment. Reads and rewrites nearly the entire volume.
Don’t start a normal file copy and walk away. Explorer’s copy hits the first bad sector, stalls there, retries indefinitely, and stresses the drive while everything past that point stays uncopied. You come back an hour later to a dialog stuck at 4% and a drive in worse shape.
Free evaluation. Firm quote before any work begins.
What to do instead
Power it down, and image it with software built for failing media.
The approach that works reads the drive in large blocks at speed, skips over regions that stall, and comes back for the difficult areas afterward — with the healthy 99% already safely captured. That ordering is the entire difference between recovering most of a drive and recovering the first 4% of it.
Once the image exists, browsing it costs nothing. You can open every folder, generate every thumbnail, and take as long as you like, because you’re reading a healthy copy.
Is this drive worth keeping?
No. A drive taking seconds per read has exhausted its pool of spare sectors, and that condition doesn’t improve. Get the data off, then retire it.
Reformatting won’t help. A format doesn’t repair physical media — it just resets the file system and hides the evidence for a few weeks. This is the same story as the other symptoms in this family: CRC errors, I/O errors, and this one are three faces of the same underlying problem.
The bottom line
Explorer hanging on a drive that mounts fine is bad sectors, and it’s not subtle. The instinct to keep clicking around and find out how bad it is costs you real data. Stop browsing, power it off, and image it before the weak regions spread.
Drive freezing everything it touches? Start a case — mention whether the hang happens on every folder or only certain ones. Localized means a bounded bad patch; everywhere means something broader.