After a clean install of Windows 11 in March, my desk setup started falling apart one device at a time. The mouse froze mid-click for about a second, then teleported. My external SSD vanished from File Explorer during a backup and reappeared a few seconds later with the file half-written. A USB headset cut out for half a beat and came back. No loose cables. No dying hardware. Windows was the culprit, and it took me longer than I want to admit to figure that out.
The cause is a default-enabled Windows feature called USB selective suspend. The intent is sensible: on battery, a port that has not seen traffic in a while can be quietly powered down to save energy. In practice, Windows is genuinely bad at guessing what “idle” means, so anything you leave plugged in cycles on and off at unpredictable intervals.
The thing that makes this hard to track down is that none of the symptoms point at power management. A mouse that stutters feels like a loose connector or a flaky receiver. An SSD that disappears mid-transfer looks like a dying cable. A headset that drops for half a second looks like a Bluetooth glitch. The actual cause, a software feature deliberately shutting your ports down, is the last thing anyone would guess.
Why Windows thinks your ports are idle
Selective suspend watches the USB bus, the internal data pathway between your ports and the rest of the system, and powers down any port where nothing has moved recently. The definition of “idle” is roughly “no bytes in the last few minutes,” which sounds reasonable on paper. It is wrong in practice for almost every device people actually plug in.
A USB mouse is not idle until I move it, regardless of what the bus has been doing. An external SSD in the middle of a multi-gigabyte backup is not idle even during the quiet seconds between write bursts. A USB headset sitting on a charging dock is not idle at all, no matter how quiet the bus looks. Microsoft’s working definition is closer to “the port has not blinked in a while” than to “the user is not using this thing,” and the gap between those two ideas is the entire bug.
The feature has been quietly annoying people for over a decade. Microsoft almost certainly tuned it for a thin office laptop with one mouse and one wired keyboard, not for someone with a hub, a webcam, a microphone, two SSDs, and a charging headset all sharing the same machine.
How I narrowed it down without the answer first
I burned through the usual checklist before the real cause surfaced. Replaced the USB cable on the external SSD with a known-good one. Same problem. Plugged the drive straight into the laptop instead of through the hub. Stable for about an hour, then the failures returned. Ran the driver update wizard inside Device Manager (the Windows control panel that lists every piece of hardware on the system). No change. Tried the drive on a different port. Same behavior.
After roughly a week of this, the pattern became obvious. Failures only happened when the laptop had been sitting for ten minutes or more. If I kept the mouse moving or copied files continuously, everything was fine. If I stepped away for coffee, the next interaction had roughly a fifty percent chance of glitching. That timing, not the symptoms, was the giveaway. Power management was the only thing in the stack that could cause time-correlated failures on otherwise-working hardware.
What I tried, in case you want to skip the same dead ends:
- Swapped in a brand-new USB cable for the external drive, no change
- Plugged the drive directly into the laptop, skipping the hub entirely
- Updated the USB drivers through Device Manager, no change
- Tried a different physical port on the same side of the chassis
- Watched the failure pattern over a week to spot the idle-timing clue
Selective suspend was the answer. Once I knew the right phrase to search for, the fix itself was under five minutes.
Two settings to flip
Selective suspend is exposed in two separate places inside Windows, and you have to change both. The reason is that the OS treats per-device power management (set on each USB controller inside Device Manager) and global power-plan behavior (set in the Advanced Power Settings tree) as independent knobs. If you only flip one, the other one quietly re-enables the original behavior the next time you change power states.
For the per-device side, open devmgmt.msc (the Device Manager console, reachable from the start menu) and expand the Universal Serial Bus controllers branch. Inside it you will find several Generic USB Hub and USB Root Hub entries. Each one has a Power Management tab with a checkbox labeled “Allow the computer to turn off this device to save power.” Uncheck that box on every USB hub entry, one at a time. Most laptops have between four and eight of them.
For the global side, navigate to the advanced power options dialog. From the Control Panel, search “power options” and pick “Change plan settings” against your active plan, then “Change advanced power settings.” Drill into the USB settings section. Inside, “USB selective suspend setting” can be flipped to Disabled for both On battery and Plugged in. Skipping either one of those profiles is the single most common reason the symptom comes back a week later.
Reboot after both changes. The fix is immediate. I went from daily glitches to none the same evening, and the symptom has not returned in several weeks of normal use.
Trade-offs
There is a real cost to disabling this setting, and it is worth naming. With selective suspend off, your USB ports sip power continuously rather than only when actively used. On a thin machine with a small battery, that slices somewhere between five and fifteen percent off total runtime in my testing. A bigger laptop with a larger battery barely notices.
A few practical framings:
- Desk-bound and always plugged in, the battery cost is irrelevant and the fix is a no-brainer.
- Frequent traveler watching every battery minute, keep suspend on while on battery and disable it only when plugged in.
- Anyone who has lost real work to a drive or mouse vanishing mid-task will not care about a small battery hit.
One Windows-specific quirk: major feature updates occasionally re-check the power management boxes on the USB Root Hub entries. If disconnects mysteriously return after an update, run the same fix again. It is a five-minute reset that always works.
When this is not the cause
The fix above solves power-management-induced USB dropouts. It does not solve every USB weirdness, and a handful of other things can produce the same surface symptoms.
A worn or underspec cable can drop a high-draw SSD under load, and the failure pattern looks identical to selective suspend firing. Swap in a different cable before assuming the OS is at fault.
Bus-powered hubs, which are hubs that draw their electricity from the laptop’s USB port rather than a wall outlet, cannot always supply enough current for multiple SSDs and accessories at once. The failures cluster around heavy use and vanish when the offending device is plugged in directly. A powered hub is the cheapest, most boring fix in this whole article, and it removes an entire category of weird issues.
After a clean OS install, Windows ships a generic USB driver that is technically functional but not great. The chipset driver from your laptop maker’s support page is almost always more stable, especially for high-bandwidth devices. Worth installing before you blame power management.
Bottom line
If your USB peripherals keep randomly disconnecting on Windows 11, start by killing selective suspend in both Device Manager and your power plan. That fix took me from daily annoyance to zero issues in under five minutes, and it has held up across several reboots and one feature update. The cost is a small slice of battery life. The benefit is never having to wonder why your mouse just teleported again.