External HD not recognized after USB hub disconnect on Windows 10

Cause #1: Lost drive letter assignment (most common)

When a USB hub disconnects unexpectedly — say you bump the cable or the hub's power brick dies — Windows can lose the drive letter it assigned to that external hard drive. The drive itself is fine, still connected, still spinning up. But Windows has no road sign to show it in File Explorer.

How to check and fix:

1. Press Win + X and choose Disk Management.
2. Look for your external drive in the bottom pane. It'll show as a black bar labeled “Healthy (Primary Partition)” but with no drive letter. If you see an empty space labeled “Unallocated” — stop. That's a different problem, covered next.
3. Right-click the black bar and choose Change Drive Letter and Paths.
4. Click Add, assign a letter like E: or F:, and hit OK.

The drive should pop up in File Explorer instantly. No reboot needed. This happens because Windows caches drive letters per USB port/device combination, and a mid-transfer hub drop can corrupt that mapping. The drive's partition table stays intact, but the letter gets orphaned.

Cause #2: Drive went offline (Windows 10 Pro/Enterprise only)

On Pro and Enterprise builds of Windows 10, external drives can be marked as “Offline” in Disk Management after a USB hub disconnect. This is part of the OS's disk protection logic — it flags any disk that saw an unexpected power loss as potentially unsafe.

How to fix:

1. Open Disk Management (Win + X > Disk Management).
2. Find your external drive. Its status bar will say Offline in gray.
3. Right-click the black bar and choose Online.
4. If the drive doesn't get a letter automatically after going online, repeat the steps from Cause #1 to assign one.

I've seen this most often with Seagate and WD Passport drives after a powered USB 3.0 hub loses and regains power. The offline flag is Microsoft's way of saying “hey, this disk might have data in flight” — but in practice, with modern external drives that flush their write cache on power loss, it's usually a false alarm.

Cause #3: USB selective suspend kicking in (driver-level fix)

If neither of the above works, the issue is likely the USB selective suspend setting. Windows 10, by default, tells USB ports to go to sleep after a period of inactivity to save power. When a hub disconnects and reconnects, that sleep signal can get stuck on the external drive's port — even if the hub itself is working.

How to fix:

1. Open Device Manager (Win + X > Device Manager).
2. Expand Universal Serial Bus controllers.
3. Right-click each USB Root Hub entry (you'll see multiple) and choose Properties > Power Management tab.
4. Uncheck Allow the computer to turn off this device to save power.
5. Repeat for all USB Root Hub entries. Click OK each time.
6. Restart your PC.

After the restart, plug the external drive directly into a motherboard-backed USB port (not the hub) and test. If it shows up, the selective suspend was the bottleneck. The reason unchecking all hubs matters: the external drive's port might be behind a different root hub than the one you assume — and Windows can assign ports dynamically across hubs during re-enumeration.

One extra step if the drive still won't appear: Open Command Prompt as Administrator and run sfc /scannow to check for corrupted USB drivers. I've seen a single bad driver file prevent drive enumeration after a hub reset. It's rare, but after the selective suspend fix, it's the next thing to rule out.

Quick-Reference Summary Table

Start with the letter fix. It's the most common and the fastest. If that doesn't work, check the offline status. Then kill selective suspend. In 9 out of 10 cases, one of these three steps brings a hub-disconnected drive back without any data loss or reformatting.