Your USB-C hub works — the monitor connected through it hums along, maybe your mouse and keyboard respond — but the SD card slot is dead. You slide in a card and Windows plays nothing, macOS shows nothing in Finder, and the card never appears in File Explorer or Disk Utility. Sometimes the slot worked last week and quit after a driver update; sometimes it never worked on this particular machine at all. Occasionally the card mounts for ten seconds, then vanishes mid-transfer, which is worse than not mounting at all because it puts your files at risk.
The good news: this is one of the least urgent hardware problems you can have, and one of the most fixable. The card itself is almost never damaged by a flaky hub slot — the failure is nearly always in enumeration, drivers, or power delivery, all of which are software- or connection-level issues you can resolve in twenty minutes without buying anything. Only a small fraction of cases end with a genuinely dead reader or hub. Work through the fixes below in order; each one is ordered from fastest to most involved, and most people find their problem in the first four.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| Hub not enumerating the reader with enough power | Reader works when the hub is plugged directly into the laptop, fails when daisy-chained or unpowered | Easy |
| Stale or corrupted USB controller drivers | Device Manager shows the reader under “Other devices” with a yellow warning, or “Unknown USB Device (Device Descriptor Request Failed)” | Easy |
| Card format not supported (exFAT disabled, or Linux/WindowsAPFS card) | Disk Management shows the card as “RAW” or “Unallocated” while other cards mount fine | Easy |
| Windows Fast Startup holding a stale drive letter | Card appears in Disk Management with no drive letter assigned | Easy |
| USB power management suspending the hub | Reader fails only after sleep/hibernate; Device Manager shows “USB selective suspend” enabled | Moderate |
| Physically damaged card slot or worn contacts | Card inserts loosely, clicks oddly, or the same reader fails on multiple known-good cards and multiple computers | Moderate to Hard |
Fix 1: Reseat and Isolate the Connection
What causes it
USB-C connectors are reversible but not infinitely tolerant. A hub that sits at the end of a long extension cable, through a dock adapter, or daisy-chained off another hub often drops below the power threshold the card reader needs — readers pull 200–500 mA briefly on insertion, more than a keyboard. Partial insertion or a worn cable also causes intermittent enumeration failures that look exactly like a dead reader.
How to check
Unplug the hub from any extension cables, adapters, or downstream hubs and plug it directly into a USB-C port on the computer itself. If you have a second USB-C port, try it. Also try a different SD card that you know works elsewhere — a camera, another laptop, anything. This two-minute test rules out the three most common non-software culprits at once.
What to do
Connect the hub straight to a native USB-C port on the host computer, avoiding adapters and pass-through chains. Insert the SD card firmly until you feel the spring-loaded click (if your hub has a push-to-eject slot) or until it bottoms out. Blow out the slot with a can of compressed air held upright — dust and pocket lint on the contact pins is extremely common in hubs that live in laptop bags.
How to undo it
Nothing to undo — reconnect your normal setup if the problem persists after this test, since you’ve only confirmed or ruled out the physical layer.
Fix 2: Restart with a Full Power Drain
What causes it
Windows Fast Startup (and macOS’s similar sleep caching) keeps the USB controller’s driver state in a hibernation file. If the hub was enumerated in a bad state before shutdown, the computer resumes with the reader still half-initialized. This is the single most common reason a reader that “suddenly died” comes back instantly.
How to check
If you’ve only used Restart or Sleep since the problem began, you haven’t actually cleared the controller. On Windows, check whether Fast Startup is on: Control Panel > Hardware and Sound > Power Options > “Choose what the power buttons do.” If “Turn on fast startup (recommended)” is checked, a normal shutdown doesn’t fully reinitialize USB.
What to do
On Windows, shut down completely while holding Shift, or open an elevated Command Prompt and run shutdown /s /f /t 0. Then unplug the hub, remove the SD card, unplug the laptop’s charger, hold the power button for 15 seconds to drain residual power from the USB rails, reconnect everything, and boot. On macOS, do a full shutdown, wait 30 seconds with all peripherals disconnected, then boot and reconnect the hub.
How to undo it
No change is persistent — the system returns to normal behavior on the next boot. If you want Fast Startup permanently off, return to the Power Options screen and uncheck it, which trades a few seconds of boot time for fewer USB quirks.
Fix 3: Reinstall the Card Reader Driver in Device Manager
What causes it
A Windows update, a hub firmware change, or an interrupted sleep cycle can leave the reader’s driver in a corrupted state. Windows then loads a generic or broken driver on every boot, so the failure repeats itself. Deleting the device entry forces Windows to re-enumerate the reader from scratch and pull the correct driver.
How to check
Press Win+X and open Device Manager. Expand “Disk drives,” “Universal Serial Bus controllers,” and “Other devices.” Look for your hub’s reader (often listed as “USB Card Reader,” “Generic USB SD Card Reader,” or the hub brand name) or for “Unknown USB Device (Device Descriptor Request Failed).” A yellow triangle confirms a driver-level problem rather than dead hardware.
What to do
Right-click the problem entry and choose “Uninstall device.” If presented with a checkbox, also check “Attempt to remove the driver for this device.” Do NOT uninstall your system’s USB host controller entries — only the reader itself. Then unplug the hub, wait 10 seconds, and plug it back into a different USB-C port. Windows will re-detect the reader and reinstall the driver automatically within 15–30 seconds. If it doesn’t appear at all, check Device Manager for a new device under “Other devices” and run “Update driver” > “Search automatically for drivers.”
How to undo it
Windows rollback handles this automatically; the reinstalled driver replaces the old one. If the new generic driver misbehaves, download the driver package from your hub manufacturer’s support page and install it over the top — that’s the correct “revert” path, not re-deleting anything.
Fix 4: Disable USB Selective Suspend
What causes it
Windows aggressively suspends idle USB devices to save power. Card readers are exactly the kind of low-traffic device that gets suspended, and cheap hub chipsets sometimes fail to wake cleanly — so the reader appears dead after any period of idleness or after waking from sleep, but works immediately after a reboot.
How to check
Does the reader work right after a fresh boot but fail after the laptop wakes from sleep, or after the card has sat idle for ten minutes? That pattern points squarely at selective suspend. To confirm the setting: Control Panel > Power Options > “Change plan settings” next to your active plan > “Change advanced power settings” > USB settings > USB selective suspend setting. If both “On battery” and “Plugged in” say “Enabled,” this is likely your issue.
What to do
Set both values to “Disabled,” click Apply, then OK. Also worth doing: Device Manager > Universal Serial Bus controllers > double-click each “USB Root Hub” and “Generic USB Hub” > Power Management tab > uncheck “Allow the computer to turn off this device to save power.” Reboot once after making these changes so the policy takes effect cleanly.
How to undo it
Return to the same Power Options dialog and set USB selective suspend back to “Enabled,” and re-check the Power Management boxes in Device Manager. Expect slightly higher idle battery drain (typically negligible on modern laptops, on the order of a few percent over a full day).
Fix 5: Assign a Drive Letter Manually
What causes it
Windows sometimes enumerates the card but fails to mount it visibly because no drive letter is assigned — often after a Fast Startup resume or a conflict with a network drive that claimed the letter (commonly E: or F:). The card is fine; Explorer just has nothing to show you.
How to check
Right-click Start > Disk Management (or press Win+X and pick “Disk Management”). Look for a removable disk of the correct size (32 GB, 128 GB, whatever your card is) with a healthy partition but no drive letter, or one marked “RAW.” If the card appears with a letter and correct file system, this fix isn’t your problem.
What to do
In Disk Management, right-click the card’s partition and choose “Change Drive Letter and Paths” > “Add” > pick an unused letter like M: or S: > OK. The card should mount immediately. If it shows as “RAW” instead, do not format yet — first try reading the card on another computer or with a dedicated card reader to recover your files before considering any reformat.
How to undo it
Return to “Change Drive Letter and Paths” and click “Remove” to release the letter. Windows will assign one automatically next time if it can. There’s no data risk in changing letters.
Fix 6: Test the Card and File System Independently
What causes it
The hub may be entirely innocent. Cards formatted in cameras with exotic partition schemes, cards encrypted with BitLocker To Go, or cards formatted APFS on a Mac won’t mount on a machine that doesn’t support that file system — and it’s easy to blame the hub slot when the real problem is format compatibility.
How to check
Put the same card in a different reader (a laptop’s built-in slot, a camera connected by USB, a different hub). Put a different, known-good card in the problem hub. If the hub reads one card but not another, the problem is the card, not the hub. Check the card’s file system: on Windows it appears in Disk Management; on macOS open Disk Utility and look at the volume’s Format field — expect exFAT, FAT32, or NTFS on Windows-readable cards; APFS will not mount on Windows.
What to do
If the card is APFS or Linux EXT4 and you need it readable on Windows, back up the files on a machine that can read it, then reformat to exFAT (right-click the card in File Explorer > Format > exFAT > Default allocation size > Start). If the card is BitLocker-encrypted, unlock it via Control Panel > BitLocker Drive Encryption using the recovery key before it will mount. If the same card fails everywhere but other cards work in your hub, the card is failing — copy everything off it immediately and retire it.
How to undo it
Reformatting is destructive and cannot be undone, which is why the backup step is non-negotiable. BitLocker unlocking and drive-letter changes are reversible at any time.
Fix 7: Update or Roll Back the Hub’s Firmware and Chipset Drivers
What causes it
Many USB-C hubs contain firmware that the manufacturer updates to fix enumeration bugs, and Windows chipset drivers (Intel Chipset Device Software, AMD Chipset Drivers) control how the USB-C controller negotiates with the hub. A mismatch — new Windows build with old chipset drivers, or vice versa — is a classic cause of readers that worked until an update.
How to check
Check your laptop vendor’s support page for your exact model and look for “Chipset” and “USB” or “Thunderbolt” driver packages dated after your last Windows update. For the hub, visit the manufacturer’s support page and look for a firmware utility (common for brands like Anker, CalDigit, and Plugable). If the reader broke immediately after a specific Windows update, roll back that update first: Settings > Windows Update > Update history > Uninstall updates.
What to do
Install the latest chipset and Thunderbolt/USB controller drivers from your laptop manufacturer (not just via Windows Update — vendor packages are more complete). If the hub has a firmware updater, run it with nothing else plugged into the hub, following the on-screen steps; do not unplug mid-flash. If you suspect a recent Windows update instead, uninstall it, reboot, and disable updates for that specific KB via “Pause updates” for up to five weeks while you wait for a corrected patch.
How to undo it
Driver installations can be rolled back in Device Manager > the device’s Properties > Driver tab > “Roll Back Driver” if the option is active. Windows updates can be reinstalled from Windows Update > “Check for updates.” Hub firmware generally cannot be downgraded — so only flash it if you’re confident it addresses your symptom.
Fix 8: Rule Out Dead Hardware
What causes it
Sometimes the reader chip, the slot’s contact pins, or the hub’s USB-C input has genuinely failed — from a power surge, a yanked cable, or simple wear after thousands of insertion cycles. No software fix recovers this.
How to check
Run through the full isolation matrix: (1) hub + known-good card on this computer, (2) hub + known-good card on a different computer, (3) a different USB device in the same hub to confirm the hub itself enumerates, (4) the same card in a different reader. If the hub’s other ports work but the reader fails on two different computers with two known-good cards, the reader section of the hub is dead. If the entire hub fails to enumerate anything, the hub is dead. If the card fails in multiple readers but other cards work, the card is dead.
What to do
Replace the failing component. For hubs, check warranty first — most reputable brands carry 18-month to 2-year coverage, and reader failures inside the warranty period are routinely replaced. For cards still under their own warranty (SanDisk, Samsung, and Kingston typically offer 5-year to lifetime limited warranties on higher-end lines), an RMA is often cheaper than a replacement. Before discarding any card, attempt recovery with a dedicated reader on a machine it previously worked with, since partial contact can sometimes still pull data off.
How to undo it
Not applicable — hardware replacement is terminal. But keep the dead hub around for parts or as a powered USB-A-only backup if only the reader section failed.
If Nothing Works
At this point you’ve eliminated power, drivers, file system, mount state, and firmware, so the fault is almost certainly physical. Your fastest path forward is a separate USB-C card reader dongle (widely available for $10–25) or a built-in card slot if your machine has one — these bypass the hub entirely and sidestep every issue above. If you need the hub’s other ports and only the reader failed, keep using the hub for peripherals and add the standalone reader. If the hub is under warranty, contact the manufacturer with a short description of the Device Manager error you saw in Fix 3; that detail typically speeds up the replacement. Finally, if data on a stubborn card matters, stop plugging it in repeatedly — repeated failed mount attempts on a degrading card reduce the odds of clean recovery, and professional recovery services exist for cases where the contents justify the cost.
FAQ
Why does my SD card work in my camera but not in the hub?
Most often it’s a file system or partition-scheme mismatch (see Fix 6) rather than a broken reader. Cameras can also lock cards with in-camera encryption or write-protect settings. Copy the files off via the camera’s USB connection if the hub won’t cooperate, and check whether the card’s format is exFAT or FAT32 — those mount nearly everywhere.
Can a USB-C hub damage my SD card?
Almost never. A reader that fails to enumerate simply doesn’t talk to the card; it doesn’t push harmful voltages. The realistic risk is interrupting a write mid-transfer (by unplugging during a copy), which corrupts the file being written, not the card itself. Pull the card only after ejecting it safely.
Why does the card show up for a few seconds and then disappear?
That pattern points to power issues (Fix 1) or selective suspend (Fix 4). The reader briefly enumerates, draws more current than the hub can sustain or gets suspended as idle, then drops. Moving the hub to a direct port and disabling selective suspend resolves this in the majority of cases.
Do I need a powered hub for an SD card reader?
Usually not — a card reader’s draw is modest. But if your hub also drives a monitor or an external SSD from a laptop port, a powered hub (with its own wall adapter delivering at least 30–60 W passthrough) removes power contention as a variable entirely. If your hub has no power input and you’re seeing intermittent reader behavior, try unplugging the hub’s other devices while reading cards.
