Getting your optimal usb hub power management settings right is the difference between instant, reliable peripherals and random disconnects, input lag, or devices that refuse to wake. For gaming, you should prioritize stability and low latency over marginal power savings. Windows is aggressive about suspending USB ports to save power, which is great for a laptop battery but terrible for a mouse, keyboard, DAC, or external drive connected through a hub. The goal is to keep the hub and its ports fully powered when you need them, while still allowing safe sleep behavior when the system is idle.
For most desktop gamers, the best approach is to disable selective suspend on powered hubs, prevent Windows from turning off the hub to save power, and use a powered hub with its own AC adapter. Laptop users can be slightly more conservative, but should still disable power management for any hub that handles input devices or audio.
As an Amazon Associate we earn from qualifying purchases at no extra cost to you.
Our Top Picks
SABRENT 10-Port 60W Powered USB 3.0 Hub10-Port - 10 USB 3.07.4 x 3.7 x 3.3 inches0.1 poundsCheck on Amazon
Top 3 picks at a glance
Quick Recommended Settings
| Setting | Recommended value | Why |
|---|---|---|
| USB selective suspend setting | Disabled | Prevents Windows from suspending idle ports, eliminating wake delay and polling drops |
| Allow the computer to turn off this device to save power (Hub) | Unchecked | Stops Device Manager power management from cutting power to the entire hub |
| USB Hub Power Management in Device Manager | Apply to Generic USB Hub and USB Root Hub (USB 3.0) | Ensures both logical hub and root controller stay powered |
| Power Plan: USB settings | High Performance or Custom plan with USB suspend disabled | Keeps settings persistent across reboots and plan switches |
| Advanced Power: PCI Express Link State Power Management | Off (Desktop) / Moderate (Laptop) | Prevents PCIe-linked USB controllers from downclocking and causing stutter |
| Windows Device Manager: USB xHCI Host Controller Power Management | Unchecked | Avoids controller-level sleep that disconnects all downstream hub ports at once |
| BIOS/UEFI: ErP Ready / Deep Sleep | Disabled | Keeps USB power active for wake from keyboard/mouse |
| BIOS/UEFI: USB Legacy Support and XHCI Hand-off | Enabled | Ensures proper handoff to Windows and prevents initialization failures after sleep |
| Hub Type | Powered hub with 12V/3A or 5V/4A AC adapter, USB 3.2 Gen 1 minimum | Guarantees 900mA per port delivery without voltage sag under load |
Setting-by-Setting
1. USB Selective Suspend Setting – Set to Disabled
What causes it: Windows Power Options includes a per-plan setting that suspends individual USB ports after a few seconds of inactivity to save power. Hubs compound this because one suspended upstream port can idle all downstream devices.
How to check: Press Win + R, type powercfg.cpl and press Enter. Click Change plan settings next to your active plan, then Change advanced power settings. Expand USB settings, then USB selective suspend setting. Note whether it says Enabled or Disabled for On battery and Plugged in.
What to do: Set both On battery and Plugged in to Disabled. Click Apply, then OK. To apply via command line, open Command Prompt as administrator and run: powercfg /SETACVALUEINDEX SCHEME_CURRENT 2a737441-1930-4402-8d77-b2bebba308a3 48e6b7a6-50f5-4782-a5d4-53bb8fcc74df 0 and then powercfg /SETDCVALUEINDEX SCHEME_CURRENT 2a737441-1930-4402-8d77-b2bebba308a3 48e6b7a6-50f5-4782-a5d4-53bb8fcc74df 0 followed by powercfg /S SCHEME_CURRENT to activate.
How to undo: Return to the same menu and set USB selective suspend setting back to Enabled for both states, or run the same commands with a final value of 1 instead of 0.
Trade-off: Disabled uses 1-3 watts more at idle but removes 50-200ms wake latency and fixes micro-stutters on polling peripherals like 1000Hz mice and USB microphones. Enabled saves power on laptops but risks missed first keystrokes and audio pops.
2. Allow the Computer to Turn Off This Device to Save Power – Uncheck for Every Hub
What causes it: Each USB hub exposes a Power Management tab in Device Manager that lets Windows cut power to the device. This is enabled by default and will override your global power plan.
How to check: Press Win + X and select Device Manager. Expand Universal Serial Bus controllers. Right-click Generic USB Hub, USB Root Hub (USB 3.0), and Generic SuperSpeed USB Hub one by one, select Properties, then the Power Management tab. See if Allow the computer to turn off this device to save power is checked.
What to do: Uncheck Allow the computer to turn off this device to save power on every instance of Generic USB Hub, USB Root Hub (USB 3.0), and USB Composite Device that represents your hub. Click OK. Repeat for Intel(R) USB 3.0 eXtensible Host Controller or AMD USB 3.10 eXtensible Host Controller entries. Restart after changing all entries.
How to undo: Re-open each device, re-check Allow the computer to turn off this device to save power, and click OK.
Trade-off: Unchecked guarantees the hub stays powered during gaming and prevents disconnect/reconnect sounds. Checked lets Windows aggressively idle ports, which can save battery but causes controllers to drop during cutscenes or loading screens.
3. PCI Express Link State Power Management – Set to Off on Desktops
What causes it: Modern USB 3.0/3.1 controllers connect via PCIe lanes. When Link State Power Management throttles the link to save power, the controller can lag in delivering USB interrupts, which manifests as hub-wide stutter.
How to check: In the same Advanced Power Settings window (powercfg.cpl, Change advanced power settings), expand PCI Express, then Link State Power Management.
What to do: For a desktop, set Setting to Off for both On battery and Plugged in. For a laptop that needs battery life, use Moderate power savings or Off when Plugged in and Moderate when On battery. Click Apply. Command line alternative: powercfg /SETACVALUEINDEX SCHEME_CURRENT 501a4d13-42af-4429-9fd1-a8218c268e20 ee12f906-d06b-4df0-8f28-5b2252765a31 0
How to undo: Set Link State Power Management back to Maximum power savings or Moderate power savings.
Trade-off: Off delivers the most consistent polling and avoids hub timeout errors (Code 43) after resume. Maximum power savings can extend battery life slightly but introduces variable latency on external NVMe enclosures and VR sensors through a hub.
4. USB Root Hub and xHCI Host Controller Properties – Disable Power Saving in Device Manager
What causes it: The xHCI host controller governs all USB 3.x ports. If its own power management is enabled, it can suspend even when the hub’s setting is disabled.
How to check: In Device Manager, expand Universal Serial Bus controllers. Right-click USB xHCI Compliant Host Controller, choose Properties, look for a Power Management tab. If present, check its state. Also check the Power tab to see total power requested vs available.
What to do: On the Power Management tab of the xHCI controller, uncheck Allow the computer to turn off this device to save power. On the Advanced tab where some Intel controllers show USB 3 Power Management or U1/U2 states, uncheck or disable them. File location for driver rollback if needed: C:\Windows\System32\drivers\USBXHCI.SYS.
How to undo: Re-check the power management box on the controller and re-enable U1/U2 states if you disabled them.
Trade-off: Keeping the controller always on prevents the whole hub tree from vanishing after sleep. Allowing U1/U2 low-power states can reduce idle power and heat but adds 2-10ms latency when a device exits low-power mode.
5. Windows Modern Standby and USB Wake Support – Configure Correctly
What causes it: Systems using Modern Standby (S0 Low Power Idle) handle USB power differently than classic S3 sleep. Hub wake can fail if selective suspend and wake permissions conflict.
How to check: Open Command Prompt as administrator, run powercfg /a to see which sleep states are available. If it reports Standby (S0 Low Power Idle), you are on Modern Standby. Then in Device Manager, right-click your hub, Properties, Power Management tab, see if Allow this device to wake the computer is available.
What to do: If you want keyboard/mouse on the hub to wake the PC, check Allow this device to wake the computer and leave Allow the computer to turn off this device unchecked. Path: Device Manager, Universal Serial Bus controllers, Generic USB Hub, Properties, Power Management. Also go to Control Panel, Hardware and Sound, Power Options, Choose what the power buttons do, click Change settings that are currently unavailable, and uncheck Turn on fast startup if you experience hubs not enumerating after shutdown.
How to undo: Uncheck Allow this device to wake the computer and re-enable Turn on fast startup.
Trade-off: Enabling wake is convenient for desktop use but can cause accidental wake from desk vibration or RGB controllers. Disabling wake saves power and prevents night-time wake but requires power button use.
6. BIOS/UEFI USB Power Delivery – ErP, Deep Sleep, and Always-On USB
What causes it: Motherboard firmware can cut 5V standby power to USB ports when ErP Lot 6 or Deep Sleep is enabled, which starves a hub even if Windows wants it powered.
How to check: Restart and press Del or F2 during POST to enter BIOS/UEFI. Navigate to Advanced, then APM Configuration (ASUS), Power Management (MSI/Gigabyte), or Advanced, then ACPI Configuration (ASRock). Look for ErP Ready, Deep Sleep, and USB Power Delivery in Soft Off State (S5).
What to do: Set ErP Ready to Disabled, Deep Sleep to Disabled, and USB Standby Power or Always On USB to Enabled. For Lenovo/Dell prebuilts, this is often under Configuration, then Always On USB. Set XHCI Hand-off to Enabled and Legacy USB Support to Enabled. Press F10 to Save and Exit.
How to undo: Return to BIOS and set ErP Ready back to Enabled (S4+S5) and Always On USB to Disabled.
Trade-off: Disabled ErP keeps hub LEDs and charging active and ensures instant wake, at the cost of 0.5-1.5 watts higher standby draw. Enabled ErP meets strict energy regulations but will make hub-attached wake unreliable.
By Hardware Tier
Low Tier: Unpowered / Bus-Powered Hubs (4-port, no AC adapter, laptop use)
Use conservative settings that still protect input devices. Disable selective suspend only for the specific hub that holds your mouse and keyboard, but leave it enabled globally if battery life is critical. In Device Manager, uncheck Allow the computer to turn off this device to save power only for the Generic USB Hub that shows your mouse under its Power tab. Keep PCI Express Link State at Moderate power savings. Plug the hub directly into a USB 3.2 port on the laptop, not daisy-chained, and do not attach drives or webcams that draw more than 900mA total. If you see Power Exceeded warnings under Device Manager, move high-draw devices to a direct motherboard port. This tier is best for temporary expansion; for stable gaming, upgrade to a powered hub when you add more than two low-power devices.
Mid Tier: Powered Hubs 7-10 Ports with 5V/4A or 12V/2A Adapter (Most Gaming Desktops)
This is the sweet spot for as we head through 2026 and the recommended baseline for gaming. Apply all optimal settings: USB selective suspend Disabled, all hub and xHCI power management boxes unchecked, PCI Express Link State Off, and BIOS ErP Disabled. Connect the hub to a rear motherboard USB 3.2 Gen 1 (5 Gbps) or Gen 2 (10 Gbps) port, not a front-panel header that shares bandwidth. Use the included adapter, rated at least 36 watts total, to ensure 7.5 watts per port for charging and to prevent voltage droop that causes disconnects. Enable Allow this device to wake the computer for the hub that holds your keyboard so you can wake from sleep with a key press (Win + X, Device Manager, Properties, Power Management). Keep cable length under 1 meter for the upstream cable to reduce signal degradation.
High Tier: Powered Hubs with Per-Port Power Switches, External SSDs, VR, and Audio Interfaces
For setups with VR headsets, USB DACs, capture cards, and external NVMe enclosures sharing a hub tree, isolate bandwidth and power domains. Use two powered hubs if possible: Hub A for low-latency inputs (mouse at 1000Hz, keyboard) with all power saving disabled, Hub B for high-bandwidth devices (SSD, webcam, capture). In Power Options, set USB selective suspend to Disabled and PCI Express Link State to Off. In Device Manager, disable power management for both hubs and their host controllers, and in controller Advanced tabs disable U1/U2 link power states if present (common on ASMedia ASM3142 and VIA VL817 controllers). In BIOS, set XHCI Hand-off Enabled and set USB power to Always On. Consider a hub with a 12V/3A (36W) or 12V/5A (60W) adapter and individual port overcurrent protection. If you use an external drive for games, do not let the drive sleep: in Power Options expand Hard disk, Turn off hard disk after, set to Never for Plugged in, or use the drive vendor tool to disable APM sleep.
Common Mistakes
Mistake 1: Only changing one hub entry. Windows creates multiple Generic USB Hub and USB Root Hub entries. Users uncheck one and miss the others, so the problem persists. Fix by expanding Universal Serial Bus controllers fully and changing every hub and host controller instance.
Mistake 2: Using a bus-powered hub for high-draw gear. A bus-powered hub can only deliver 500mA (USB 2.0) or 900mA (USB 3.0) total from the upstream port. Plugging in an external HDD, RGB keyboard, and DAC will brown out and reset. Always use a powered hub and verify its adapter rating printed on the brick.
Mistake 3: Leaving Fast Startup enabled with hubs. Fast Startup (Control Panel, Power Options, Choose what the power buttons do) hibernates the kernel, which can leave hubs in a suspended state after shutdown. If your hub needs replugging after cold boot, disable Fast Startup.
Mistake 4: Daisy-chaining hubs. Plugging a hub into another hub adds latency and halves power reliability. Connect each hub directly to the motherboard’s rear I/O. If you must chain, keep it to two levels max and never chain bus-powered hubs.
Mistake 5: Updating BIOS without re-checking ErP settings. BIOS updates often reset ErP Ready to Enabled by default, silently breaking wake and hub power. After any BIOS update, re-enter BIOS and confirm ErP remains Disabled and XHCI Hand-off remains Enabled.
Mistake 6: Relying on Device Manager alone. Some users toggle Device Manager but forget Power Options still has selective suspend Enabled, which re-enables suspension at the OS level. Both locations must be set to disabled for full effect.
FAQ
Will disabling USB power saving increase my power bill or hurt my hardware?
No. Disabling selective suspend and hub power management keeps 5V rail active and prevents controllers from entering U1/U2 sleep. The increase is typically 1-4 watts at idle for a desktop, negligible for component wear. Heat on a quality powered hub stays within spec because its adapter is rated for continuous load. The only downside is slightly higher idle draw and LEDs staying on during sleep. Re-enable the settings if you need maximum battery life on a laptop.
Why does my hub still disconnect after I disabled all the settings?
Check three additional causes. First, verify you unchecked every entry under Universal Serial Bus controllers, including hidden devices (in Device Manager click View, Show hidden devices). Second, inspect the physical layer: try a different upstream cable under 1 meter, avoid front-panel headers, and test a rear motherboard port. Third, check driver power policy overrides at registry location HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_XXXX&PID_XXXX\Device Parameters\SelectiveSuspendEnabled set to 0, or reinstall the host controller driver from your motherboard vendor support page. If Code 43 appears, unplug the hub’s AC power for 30 seconds to reset its internal controller.
Should I use USB 2.0 or USB 3.0 ports for my hub on a gaming PC?
Use USB 3.2 Gen 1 (blue port, 5 Gbps) or Gen 2 (red port, 10 Gbps) for the upstream connection, even for 2.0 devices, because 3.x ports provide 900mA versus 500mA and have stricter power delivery. For peripherals sensitive to polling stability, like competitive mice, a USB 2.0 hub on a USB 2.0 port can sometimes offer slightly more consistent latency due to simpler transaction translation, but for mixed loads with audio and storage, USB 3.x is superior. Avoid USB 3.0 hubs that use a single transaction translator for all 2.0 devices; a hub with multiple TTs, listed in specs as Multi-TT, handles mixed-speed devices better.
How do I keep my external drive from sleeping when it is behind a hub?
Two layers control drive sleep. In Windows, go to powercfg.cpl, Change advanced power settings, expand Hard disk, Turn off hard disk after, set to Never for Plugged in and 15 Minutes or higher for On battery. For the drive itself, disable APM if supported: for Western Digital use WD Drive Utilities, for Seagate use SeaTools, set Sleep Timer to Never. Also in Device Manager, under Disk drives, right-click the external drive, Properties, Policies tab, ensure Better performance is selected for drives with write cache, and uncheck Turn off to save power under its USB bridge entry in Universal Serial Bus controllers. To revert, set Turn off hard disk after back to 20 Minutes and re-enable the bridge power saving.
