USB hub not working — devices connected through it show nothing in Windows, show with errors, or intermittently disconnect — has a surprisingly structured set of causes that are worth working through in order rather than randomly. If you want the full context, see our Complete Guide to Fixing Windows, Browser, and Software Errors.
Before anything else: test the hub itself. Connect only one device to the hub (something simple, like a USB flash drive). Does it appear? If a single device connected directly to the hub works but multiple don’t: power is the issue — the hub can’t supply enough current for all devices simultaneously. If nothing works at all through the hub: either the hub itself is faulty or the port it’s connected to has a problem.
Also: try the hub in a different USB port on the computer. This takes 30 seconds and rules out the specific port being faulty before any software investigation.
Powered vs unpowered hubs
This is the most important distinction for troubleshooting USB hubs. Unpowered (bus-powered) hubs draw all power from the USB port they’re connected to — typically 500mA for USB 2.0 ports, 900mA for USB 3.0. External hard drives, charging devices, and some USB peripherals require more power than an unpowered hub can supply when multiple devices are connected simultaneously.
If devices disconnect under load, don’t charge when connected through the hub, or work individually but not together: power is the bottleneck. A powered hub (with its own AC adapter) delivers 500mA or more per port regardless of how many devices are connected. For setups with more than 2–3 USB peripherals: a powered hub is the correct solution, not a driver fix.
USB selective suspend — Windows cutting power
Windows power management can cut power to USB hubs to save energy. Devices connected through the hub then appear to disconnect and may not reconnect correctly. This is the most common software cause of intermittent hub disconnections.
Device Manager → Universal Serial Bus controllers → right-click each USB Root Hub → Properties → Power Management → uncheck “Allow the computer to turn off this device to save power.” Do this for every Root Hub entry. Also:
- Control Panel → Power Options → Change plan settings → Change advanced power settings → USB settings → USB selective suspend setting → Disabled
Apply both changes. After restarting, the hub should maintain consistent power without Windows cutting it during idle periods.
USB controller driver
Device Manager → Universal Serial Bus controllers → look for any entries with yellow warning triangles. Also look for “Unknown Device” entries without triangles — these represent connected devices the system can’t identify, often because the USB controller driver is outdated or corrupted.
Right-click each USB Host Controller → Update driver. For laptops: the USB controller driver from the manufacturer’s support page for the specific model is more reliable than Windows Update’s version. After updating drivers, reconnect the hub and test.
Bandwidth limitations on USB 3.0
USB 3.0 supports 5 Gbps of total bandwidth shared among all devices connected through a hub on the same controller. When multiple high-bandwidth devices (external SSDs, USB 3.0 cameras, capture cards) are all connected through one hub simultaneously: they compete for that shared bandwidth. Performance degrades and intermittent disconnections can occur as devices compete for throughput.
Check: Device Manager → Universal Serial Bus controllers → look at how many devices share each root hub. Devices on the same root hub share bandwidth. Distributing high-bandwidth devices across different physical USB ports (which may connect to different root hubs) reduces contention. Running devmgmt.msc → View → Devices by connection shows the device tree and which devices share each hub.
USB 3.0 and 2.4 GHz interference
USB 3.0 ports emit electromagnetic interference in the 2.4 GHz frequency range. Wireless devices connected through or near a USB 3.0 hub — particularly USB wireless receivers (keyboard and mouse dongles, wireless headphones) — experience significant interference from the USB 3.0 signal. Devices appear unreliable, lag, or disconnect intermittently.
Move the USB hub away from the wireless receiver using a USB extension cable. Or connect wireless receivers directly to a USB 2.0 port (blue ports are USB 3.0; black ports are 2.0 on most machines) rather than through the hub. The physical separation resolves the interference immediately.
Hub with its own driver requirements
Some USB hubs — particularly those with charging ports, data passthrough, and DisplayPort/HDMI — require manufacturer drivers beyond what Windows provides automatically. If a hub worked immediately out of the box but certain features don’t work (specific ports, video output, charging while transferring data): the manufacturer’s full driver package enables these features.
Check the hub’s packaging or the manufacturer’s website for driver downloads. CalDigit, OWC, Anker, and other hub manufacturers often provide Windows drivers that enable full hub functionality beyond basic USB passthrough.
Registry cleanup for orphaned USB entries
Windows tracks connected USB devices in the registry (HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumUSB). After many devices are connected and disconnected over years, orphaned entries from removed devices can sometimes conflict with new devices connecting to the same port or hub position. Device Manager → View → Show hidden devices → scroll through the USB entries for greyed-out (historical) devices. Right-click → Uninstall for any orphaned devices from hardware you no longer use. This cleans up the USB device registry and occasionally resolves detection issues with current hubs.
For the USB port-level power and driver issues that affect hubs and direct USB devices equally, our USB device not recognized guide covers the host controller and port reset approach. If the hub is a USB-C or Thunderbolt hub specifically, our USB-C troubleshooting guide covers the Thunderbolt device approval and driver specifics. Microsoft’s USB hub troubleshooting documentation covers the USBView tool (from Windows Driver Kit) that provides a complete tree view of all USB connections and their current status, useful for diagnosing which device is causing hub-level detection failures.
Hub connected to another hub (daisy-chaining)
USB specifications technically allow daisy-chaining up to 5 hubs (7 tiers total including the root hub and end device), but in practice, reliability degrades significantly beyond one or two levels of hub nesting. Power delivery becomes insufficient, and timing issues in the USB protocol cause intermittent detection failures. A device connected through Hub A → Hub B → Computer may work intermittently while the same device connected directly to a single hub works reliably.
If you’ve daisy-chained hubs: simplify to a single hub level. One larger powered hub directly connected to the computer is more reliable than two smaller hubs chained together. If the device count requires more ports than one hub provides: use a powered hub with more ports rather than chaining unpowered hubs.
Cable quality and length
USB cable quality affects reliability at hub distances. USB 2.0 cables have a maximum effective length of 5 metres; USB 3.0 is 3 metres. Beyond these limits, signal integrity degrades and devices connected through the hub appear intermittently or show as “Unknown Device.” If the hub uses a long cable to connect to the computer, cable length is worth testing — shorten it or replace with a higher-quality cable designed for the specific USB version.
For longer distances: USB active extension cables (with built-in signal repeaters) maintain signal integrity beyond passive cable limits. Passive cheap cables at long distances are a reliable source of “it works sometimes” USB hub behaviour that looks like a software problem but is entirely physical.
Windows 11 fast startup and USB enumeration
Windows Fast Startup saves part of the kernel state during shutdown. USB device enumeration — the process of Windows discovering and configuring all connected devices — is partially skipped during Fast Startup resume. Devices connected through a hub during the Fast Startup period may not be fully enumerated, appearing absent or unreliable until the machine performs a full restart (rather than shutdown + power on).
Test: use Restart → boot from restart → check hub devices. If they’re reliable after restart but not after a normal shutdown + power on: Fast Startup is causing the incomplete enumeration. Fix: Control Panel → Power Options → Choose what the power buttons do → uncheck “Turn on fast startup.” Shutdowns now perform full USB enumeration on the next boot.
BIOS USB settings
BIOS/UEFI has its own USB configuration. On some systems, settings like “USB Legacy Support,” “XHCI Pre-Boot Mode,” or “USB Charging and Wake Support” affect how the USB controller is initialised before Windows loads. If the hub works during BIOS/POST but not in Windows (or vice versa), a BIOS USB setting may be relevant.
Enter BIOS → Advanced → USB Configuration → look for these settings. “USB Legacy Support” should be Enabled for broad compatibility. “XHCI Hand-off” should be Enabled on most systems. These settings rarely need adjustment but are worth checking after a BIOS update or BIOS settings reset changed them from working defaults.
Device compatibility and over-current protection
USB hubs and root ports include over-current protection that shuts down a port when a device draws more current than allowed. When the protection triggers, the port — and sometimes the entire hub — goes offline. Windows may or may not report this with a notification.
Signs of over-current triggered shutdown: hub works fine, a specific device is connected, and the hub suddenly goes offline along with all other connected devices. That specific device is drawing too much current. Event Viewer → System → look for “USB” warnings about over-current. Remove the high-current device → reconnect the hub (or restart) → other devices should work normally. The high-current device needs its own USB port (direct to computer, not through the hub) or a powered hub with higher per-port current rating.
Waking from sleep and hub re-enumeration
After the computer wakes from sleep, USB hubs re-enumerate their connected devices. When this re-enumeration fails — because the hub’s wake timing is off, or because a device on the hub isn’t responding to the enumeration request quickly enough — some or all hub devices appear missing until the hub is physically unplugged and replugged.
Device Manager → right-click the USB hub device entry → Properties → Power Management → uncheck “Allow the computer to turn off this device to save power.” The hub stays in active state during sleep rather than fully powering down, reducing the re-enumeration requirement on wake. Also update the hub’s specific driver if available — wake-from-sleep USB re-enumeration issues are commonly addressed in hub driver updates.
VIA, ASMedia, and Fresco Logic hub controllers
Third-party USB hub controllers — made by VIA, ASMedia, or Fresco Logic — sometimes have Windows 11 compatibility issues. If the hub contains one of these controllers (visible in Device Manager → USB hubs → Properties → Details tab → Hardware IDs), manufacturer-specific drivers for that controller chip are worth checking.
Searching for the controller’s hardware ID (e.g., “VIA USB Hub” or “ASMedia USB Hub”) along with “Windows 11 driver” often leads to the manufacturer’s driver update page. These controller-specific drivers sometimes resolve detection issues that Windows’ generic hub driver can’t handle for that specific chip’s quirks.
A practical testing sequence when a USB hub is intermittently misbehaving: (1) test with one device at a time to isolate which device (or combination) causes the problem. (2) test the hub in a different USB port and with a different cable. (3) test with the hub powered (if it has its own power adapter, ensure it’s connected). (4) restart the computer with the hub already connected rather than connecting after startup. These four steps, done methodically, usually identify whether the problem is power, a specific device, a specific port, or the enumeration timing — each pointing at a different fix from the options above.
One more situation that catches people out: connecting a USB hub to another USB hub that’s connected through a USB-C dock. Thunderbolt/USB4 docks have their own internal hub logic, and adding external hubs to their ports creates a multi-level hub configuration that often hits the USB protocol’s hub nesting limits. If this describes your setup and the hub is unreliable: connect the hub directly to the computer rather than through the dock, and connect the dock’s devices directly to the dock’s ports. The dock is itself a hub — treating it as the hub and connecting devices directly to it without an additional hub layer simplifies the USB tree and eliminates the nesting issues. Our guide on Touchscreen Not Working on Windows 11 covers an adjacent issue.
For hubs that worked previously and stopped after nothing obvious changed: check Windows Update history from the date the hub problems started. USB controller driver updates pushed through Windows Update are a consistent source of hub regression — the new driver handles some devices better and others worse. If the date of hub problems correlates with an update date: Device Manager → USB Host Controller → Properties → Driver → Roll Back Driver as a first step before any other investigation. Rolling back a driver takes two minutes and immediately confirms or rules out the driver update as the cause. See also USB Device Keeps Disconnecting for a related case.
