Troubleshooting USB controller power states

A drive that ejects itself, a mouse that freezes for a heartbeat, a webcam that blinks out mid-call: random USB disconnects like these rarely come from the device. More often the USB controller is putting ports to sleep too eagerly to save power, then waking them a moment late. Windows calls this selective suspend, and by default it's aggressive. Tuning suspend behavior, fixing per-hub power management, and, if needed, reinstalling the controller usually settles things down. Work through the settings below and confirm the fix by watching the logs while you stress the ports.

1. 1

   Turn off USB selective suspend

   Selective suspend lets Windows power down idle USB ports, and on many systems it drops devices that should stay awake. Open Control Panel, go to Power Options, and click Change plan settings on your active plan, then Change advanced power settings. Expand USB settings, then USB selective suspend setting, and set it to Disabled. On a laptop you'll see separate On battery and Plugged in values, so disable both. Click OK and reconnect the misbehaving device. If the random disconnects stop after this single change, suspend was the cause and you may not need the deeper steps below.

2. 2

   Stop each USB hub from sleeping

   Even with selective suspend off, individual hubs carry their own power setting that can override it. Right-click the Start button and open Device Manager, then expand Universal Serial Bus controllers. For every entry named USB Root Hub or Generic USB Hub, right-click it, choose Properties, and open the Power Management tab. Uncheck Allow the computer to turn off this device to save power, then click OK. Repeat for each hub in the list, since one missed hub can keep dropping the device plugged into it. This per-hub cleanup is the setting most people overlook, and it often finishes what disabling selective suspend started.

3. 3

   Adjust the power plan for stability

   Aggressive power plans reintroduce suspend behavior through the back door. Back in Power Options, if you're troubleshooting on a laptop, avoid the deepest battery-saver plan while testing and use Balanced or a higher-performance plan instead. Battery saver mode itself, found in Settings under System then Power, can tighten USB power limits, so switch it off while you diagnose. The goal is a consistent power environment so a disconnect can be blamed on the right thing. Once the ports are stable, you can return to your preferred plan and watch whether the trouble comes back, which would tell you the plan was involved.

4. 4

   Reinstall the xHCI controller

   If disconnects continue, the controller driver itself may be in a bad state. In Device Manager under Universal Serial Bus controllers, look for the xHCI host controller, often named USB 3 eXtensible Host Controller. Create a restore point first, then right-click it and choose Uninstall device. Restart the PC, and Windows re-detects the controller and reinstalls its driver, rebuilding the port stack cleanly. Be aware that removing the controller drops all USB devices until the reboot completes, so save your work and keep a PS/2 or built-in keyboard handy on a desktop. If problems persist, get the chipset driver from your PC maker's official support page.

5. 5

   Test ports one at a time

   Isolate the fault by testing methodically. Move the problem device to a different port, ideally directly on the PC rather than through a hub, dock, or monitor that adds its own power management. If it behaves on one port but not another, the port or its hub is the weak link, not the device. Also try the device on another computer if you can; steady behavior there confirms the issue is your controller settings, not the hardware. This process of elimination keeps you from reinstalling drivers to fix what is actually an underpowered hub or a loose cable.

6. 6

   Rule out an underpowered hub

   Devices that draw a lot of current, such as external hard drives, bus-powered hubs loaded with peripherals, or fast-charging phones, can exceed what a port supplies and force a disconnect that mimics a power-state bug. Plug high-draw devices into their own powered port or a hub with its own power adapter rather than daisy-chaining them. If the disconnects vanish once the load is spread out, the cause was current, not suspend settings. Knowing this saves you from disabling power features you actually want, when the real fix is simply giving hungry devices a dedicated, adequately powered connection.

7. 7

   Confirm the fix in Event Viewer

   To be sure the disconnects are gone rather than just quiet for now, stress the ports: copy a large file to an external drive, keep a webcam running, and use a USB mouse for a while. Then open Event Viewer, expand Windows Logs, and read the System log. Look for surprise removal or device-reset entries around the times anything hiccupped; a clean log during heavy use means the power-state fix held. If new errors still appear, note which controller or hub they name and revisit that specific device's Power Management tab, since one hub may have slipped through earlier.