You connect an external SSD or hard drive through a USB-C hub.
Windows detects it.
The drive appears in This PC.
Then you double-click it.
File Explorer stops responding.
The address bar may keep loading, the green progress bar may crawl across the top of the window, or Explorer may remain frozen for 20 or 30 seconds before the drive finally opens.
That does not automatically mean File Explorer itself is broken.
If File Explorer freezes only when it accesses one external drive, Explorer may be waiting for a storage I/O request that has not completed.
The delay can originate from the file system, external drive, enclosure, cable, USB-C hub path, power delivery, or storage hardware.
The safest approach is to identify where the wait begins before running repair commands.
Capture the “Freeze Fingerprint”
Do not begin by formatting the drive or reinstalling USB drivers.
First record exactly what causes the freeze.
| Freeze Pattern | First Area to Investigate |
|---|---|
| Explorer freezes as soon as you open the drive | Storage I/O / drive / connection |
| Drive opens but one folder freezes | File or folder metadata |
| Freeze begins when thumbnails load | Preview / thumbnail generation |
| Freeze happens during large transfers | Sustained I/O / cable / power |
| Drive freezes through hub but works directly | USB-C connection path |
| Direct and hub connections both freeze | Drive / enclosure / file system |
| Drive disappears after freezing | USB reset / power / hardware |
| Disk Management also becomes slow | Lower-level storage problem |
The important question is not simply:
“Is File Explorer frozen?”
It is:
“What was Explorer trying to read when it froze?”
Protect Important Data Before Repairing Anything
If the drive contains important files, do not immediately run:
chkdsk /f
or:
chkdsk /r
A repair operation creates additional disk activity.
If the external drive is already:
- disconnecting;
- disappearing;
- resetting;
- clicking;
- repeatedly freezing;
stabilize the connection first.
If the drive remains readable, copy irreplaceable files before lengthy testing.
If the symptom changes from a temporary freeze into RAW, 0 Bytes, or a format prompt, stop normal troubleshooting and follow the external drive RAW or 0-byte recovery workflow instead. LENTION's separate guide treats that situation as a data-preservation problem rather than an ordinary performance issue.
Evidence #1: Does Disk Management Respond Normally?
Suppose File Explorer freezes when you click:
*E:*
Do not keep double-clicking the drive.
Instead, open:
Disk Management
with:
diskmgmt.msc
Find the external disk and check:
- physical capacity;
- partitions;
- drive letter;
- file system;
- whether the disk remains continuously visible.
Explorer Freezes, but Disk Management Is Responsive
This suggests Windows can still communicate with the physical storage device.
Pay more attention to:
- a particular folder;
- file metadata;
- thumbnail generation;
- Preview pane;
- file-system behavior.
Disk Management Also Becomes Slow
That is more significant.
The delay may be occurring lower in the path:
External Drive
→ Enclosure / USB Bridge
→ Cable
→ USB-C Hub
→ Host Controller
Windows may be waiting for the drive itself rather than File Explorer simply struggling to display a folder.
The Drive Appears and Disappears
Now the problem has moved beyond a normal Explorer freeze.
If the SSD disappears entirely, use the external SSD detection troubleshooting guide to investigate data ports, power, cables, and the drive itself.
Evidence #2: Check Windows for an I/O Timeout
A 30-second freeze becomes much more meaningful if Windows records a storage error at the same time.
Open:
Event Viewer → Windows Logs → System
Look around the exact timestamp when Explorer froze.
Useful events may include:
Event ID 129
Event ID 153
and sometimes:
Event ID 157
Microsoft's storage and disk error troubleshooting guidance explains that storage events can record timed-out requests, retried I/O operations, resets, or surprise removal behavior.
Conceptually, the sequence can look like:
Explorer requests data
→ Storage does not respond quickly enough
→ Windows waits or retries
→ Explorer appears frozen
→ Request succeeds or the storage path resets
The important distinction is:
An I/O timeout is evidence of a storage-path problem, but it does not by itself prove the USB-C hub is defective.
The drive, enclosure, cable, hub, or host connection can all still be variables.
Evidence #3: Does the Freeze Follow the Drive or the Hub?
This is one of the most useful comparisons you can make.
Keep the same drive and storage cable whenever possible.
Connection A
External Drive → USB-C Hub → Laptop
Open the folder or file that normally causes Explorer to freeze.
Connection B
External Drive → Laptop Direct
Repeat the exact same action.
Direct Connection Works Normally
If the drive:
- opens quickly;
- transfers files normally;
- remains mounted;
when connected directly, but repeatedly freezes through the hub, shift your attention toward the USB-C path.
Investigate:
hub data port
host cable
available power
other connected peripherals
USB-C port on the laptop
Direct Connection Also Freezes
The hub becomes much less convincing as the primary cause.
Investigate:
drive
enclosure
storage cable
file system
drive health
The rule is simple:
If the freeze follows the drive, investigate the drive path. If it follows only the hub connection, investigate the USB-C path.
Evidence #4: Remove the Other Devices
If the external drive is stable when connected directly, rebuild the hub setup with only one device.
Use:
Laptop → USB-C Hub → External Drive
Temporarily disconnect:
- second SSDs;
- HDDs;
- webcams;
- phones;
- capture cards;
- audio interfaces;
- card readers.
Open the same folder again.
The Freeze Disappears
Add devices back one by one.
Do not immediately conclude:
“The hub cannot handle many devices.”
Instead, ask what changed when the problem returned:
Power demand?
Shared storage activity?
Another bus-powered device?
Continuous USB traffic?
If the hub supports Power Delivery, test it with the appropriate charger connected.
This is especially relevant when external storage freezes only after other bus-powered peripherals become active.
When a Storage-Focused Hub Layout Makes Sense
A new USB-C hub cannot repair:
- a damaged file system;
- a failing SSD;
- a faulty enclosure;
- corrupted data.
But hardware becomes relevant when your evidence shows:
Direct connection = stable
while:
current hub path = repeated freezes or resets
For workflows centered on several USB-C SSDs, using a USB-C hub with four dedicated 10Gbps USB-C data ports and up to 100W Power Delivery can provide a cleaner storage-oriented connection path.
The LENTION CE31s provides four USB 3.2 Gen 2 USB-C data ports rated up to 10Gbps, while its separate PD input supports up to 100W power pass-through. The individual data ports are for data rather than video or device charging.
That makes this type of configuration particularly relevant when the workstation contains:
USB-C SSD 1
USB-C SSD 2
another high-speed USB-C peripheral
rather than repeatedly converting those devices through USB-A adapters.
However, higher port speed is not itself a fix for an I/O timeout. The drive, enclosure, host connection, and total workload must still be stable.
For mixed storage workflows involving USB-A external HDDs or SSDs plus SD and microSD media, a USB-C hub with three USB 3.0 ports, SD/Micro SD readers, and up to 100W PD pass-through provides a different type of storage layout.
The LENTION CB-C36B combines three USB 3.0 ports rated up to 5Gbps with simultaneous SD/Micro SD reading, HDMI, and Power Delivery. Its product specification also notes that PD power can provide additional power to attached hard disks and accessories while charging the host.
This makes it more naturally suited to workflows such as:
Camera SD Card → Laptop
while:
External HDD/SSD → USB 3.0
and:
Laptop → PD Charger
all remain connected.
Again, neither configuration should be presented as repairing a failing disk.
Their role begins only when troubleshooting shows that the connection layout, data-port type, or available power is part of the problem.
Evidence #5: Does Only One Folder Freeze?
Suppose:
E:\ opens normally
but:
E:\Photos\2026\Project
freezes every time.
That points in a different direction.
Test another folder on the same drive.
If most folders open instantly but one folder hangs, Windows may be struggling with:
- image thumbnails;
- video metadata;
- damaged media;
- a very large directory;
- problematic file-system metadata.
Temporarily disable the Preview pane.
You can also switch from large thumbnails to a simple list or details view.
If that folder now opens normally, preview or metadata generation may be contributing to the freeze.
By contrast:
Drive root itself freezes
Disk Management slows
Windows logs storage timeouts
is much stronger evidence of a lower-level I/O issue.
Mechanical HDD? Listen to the Drive Too
External hard drives require another clue:
sound.
If Explorer freezes at the same moment you hear:
click → spin down → spin up
or the drive LED restarts, stop treating this as only a File Explorer problem.
That pattern may involve:
- insufficient power;
- USB reset;
- cable instability;
- enclosure problems;
- the hard drive itself.
Use the dedicated external hard drive clicking and spin-down troubleshooting guide to distinguish occasional drive noise from a repeated restart pattern.
If loud abnormal clicking continues even when the HDD is directly connected, prioritize your files over additional hub testing.
Inspect the File System Only After the Connection Is Stable
Once the drive:
- stays continuously connected;
- reports the correct capacity;
- no longer resets;
you can inspect the file system.
For a drive using the letter E::
chkdsk E:
Microsoft's CHKDSK documentation states that running CHKDSK without repair parameters displays the volume's status but does not fix errors. Parameters such as /f or /r perform repairs or additional recovery operations.
That difference matters.
Start With Inspection
chkdsk E:
Move to Repair Deliberately
Do not jump directly to:
chkdsk E: /f
on an unstable drive containing important files simply because Explorer froze.
First make sure:
the storage connection is stable
and:
important data is protected
before modifying the file system.
Restarting Explorer Fixes the Window, Not the Storage Path
If File Explorer stays frozen after an I/O request eventually fails, you can use:
Task Manager → Windows Explorer → Restart
This can restore:
- File Explorer;
- desktop;
- taskbar;
- Windows shell responsiveness.
But restarting Explorer does not repair:
a failing drive
an unstable USB connection
an enclosure problem
or:
file-system damage
If Explorer freezes again as soon as you reopen the same drive, the underlying storage issue is still present.
Know When to Stop Testing
Do not repeatedly stress an important drive if the symptoms are getting worse.
| What You See | Priority |
|---|---|
| One folder freezes | Investigate folder / metadata |
| Hub freezes, direct works | Investigate USB-C path |
| Hub and direct both freeze | Drive / enclosure / file system |
| Event 129/153 repeatedly appears | Investigate I/O timeout path |
| Drive disappears | Stabilize storage connection |
| RAW / 0 Bytes | Protect data first |
| HDD clicks and disappears | Stop repeated stress testing |
If the problem changes categories, change the troubleshooting strategy with it.
Quick Answers
Why does File Explorer freeze when I open my external drive?
Explorer may be waiting for a storage I/O request that is delayed or not completing. The cause can be the drive, file system, enclosure, cable, USB-C hub path, or another storage component.
Does File Explorer freezing mean my SSD is failing?
Not necessarily. Compare direct versus hub connections, check Disk Management, and review Windows storage events before blaming the SSD.
What do Event ID 129 and 153 suggest?
They can indicate storage requests that timed out, were reset, or had to be retried. They support an I/O-timeout diagnosis but do not identify the failed component by themselves.
Should I immediately run CHKDSK /f?
No. If the storage connection is unstable or important files have not been protected, stabilize and inspect the drive first.
Why does only one folder freeze?
Thumbnail generation, damaged media, metadata, or file-system problems in that directory may be responsible.
Why does the drive work directly but freeze through the USB-C hub?
That result shifts suspicion toward the hub data path, host connection, power availability, attached peripheral load, or another part of the USB-C connection.
Final Takeaway
When File Explorer freezes while opening an external drive through a USB-C hub, do not diagnose the problem from the frozen window alone.
Capture the freeze fingerprint.
Ask:
What action triggers the freeze?
Does Disk Management also slow down?
Did Windows record an I/O timeout?
Does the drive work when connected directly?
Does removing other USB devices change the result?
Then follow the evidence.
If File Explorer freezes only when it accesses one external drive, Explorer may simply be waiting on storage I/O rather than being the component that actually failed.
And when important files are involved:
Stabilize the storage path before attempting file-system repair.
That distinction helps you decide whether the real problem belongs to:
File Explorer
File System
USB-C Connection
Drive Enclosure
or:
External Drive
without turning a temporary storage timeout into a more serious data problem.