Controller Keeps Disconnecting on PC
A controller that keeps dropping connection on PC is usually one of three culprits: Windows USB Selective Suspend cutting power to the port mid-game, USB 3.0 radio interference for wireless dongles, or a failing cable or connector. The connection stability test measures your drop rate directly so you can confirm the fix worked.
Diagnose before you fix
Confirm the symptom and measure its severity first. The test result tells you whether to clean, recalibrate, or replace — different severities call for different fixes.
Connection Stability
The connection stability test measures your controller's real-world drop rate and packet consistency over time — exactly the metric that matters here. Run it for several minutes both before and after each fix below. If disconnects drop from once every 10 minutes to zero, the fix worked. If the number doesn't change, that fix wasn't the cause and you move to the next one.
Run the connection stabilityButton Test
The button test also stays open during a disconnect — you'll see the moment inputs stop registering, which pins down when in the session the drops happen. Consistent drops after 5–10 minutes of inactivity point at USB Selective Suspend; random drops during active play point at cable/dongle/interference.
Run the button test- Windows admin access (for USB power settings)
- A USB 2.0 port or USB extension cable (for dongle relocation)
- A known-good USB data cable
Step by step
Work through these in order. After the last step, run the diagnostic again to confirm the fix held.
- 01
Measure the drop pattern first
Open the connection stability test and let it run for at least 10 minutes while occasionally moving the controller. Note when disconnects happen: after periods of inactivity (Windows power management), during active use with no clear trigger (interference or cable), or immediately on connect and then repeatedly (driver issue). The pattern narrows down which fix below is likely to work before you touch anything.
- 02
Disable USB Selective Suspend
Windows aggressively sleeps USB ports to save power, and mid-game controller disconnects after a few minutes of light input are the classic signature. Open Control Panel → Power Options → Change plan settings → Change advanced power settings → USB settings → USB selective suspend setting. Set it to Disabled on both battery and plugged-in. Apply and reboot. This single change resolves the majority of Windows USB controller disconnects, wired or dongle.
- 03
Move 2.4GHz dongles away from USB 3.0
USB 3.0 ports leak RF noise directly into the 2.4GHz band used by wireless controller dongles — this is a well-documented Intel white-paper issue, not folklore. If your controller uses a dongle (8BitDo, GameSir, GuliKit, Xbox Wireless Adapter, etc.), move it to a USB 2.0 port, or connect via a short USB extension cable that distances the dongle from USB 3.0 ports and any USB 3.0 external drives. Re-run the stability test to confirm the drop rate fell.
- 04
Prevent the controller from powering down
In Device Manager, expand Universal Serial Bus controllers, right-click each USB Root Hub → Properties → Power Management, and uncheck 'Allow the computer to turn off this device to save power.' Do the same for the specific HID device your controller registers as. This is redundant with USB Selective Suspend for many setups but catches edge cases where Windows still aggressively power-manages individual devices.
- 05
Swap the cable and try different ports
A partially failing USB cable — bent connector, damaged internal wires, worn shielding — produces disconnects that look like driver or interference issues but are purely physical. Try a known-good data cable in a different USB port (prefer USB 2.0 for controllers). If disconnects stop, the original cable or port was the cause. Charge-only cables also produce this pattern when they degrade to the point their charge circuit intermittently fails.
- 06
Update or reinstall the controller driver
In Device Manager, find your controller under Human Interface Devices or Xbox Peripherals, right-click → Uninstall device (tick 'Delete driver software' if offered), then reboot. Windows reinstalls a fresh driver on next connect. For Xbox controllers, use the Xbox Accessories app to check for firmware updates as well. For DualSense, DS4Windows has its own driver refresh option. Corrupted driver state causes disconnects that persist across cable swaps.
- 07
Rule out battery-related wireless dropouts
Wireless controllers below roughly 20% battery transmit at reduced power, which causes drop-prone connections that look identical to interference. If your controller is wireless and drops correlate with long sessions or lower battery, charge to full and retest. Persistent drops at full battery confirm the issue is elsewhere; drops that vanish at full charge mean the battery is degrading and worth checking with the battery health check.
Where to go next
Persistent symptoms usually mean hardware wear that cleaning and recalibration can't reach. These resources cover repair, replacement, and warranty paths.
Other tests for the same controller
A symptom rarely arrives alone. Worn sticks often coincide with deadzone creep and reduced circularity — run the related diagnostics while the controller is already in your hands.
Variants of this symptom
The same underlying issue presents differently across controllers. These device-specific guides cover the variations.
connection questions
Almost certainly Windows USB Selective Suspend, which sleeps USB ports to save power when they're idle. When you resume input, the port sometimes fails to wake cleanly and the controller drops. Disabling USB Selective Suspend in Power Options, plus unchecking 'Allow the computer to turn off this device' on the USB Root Hubs in Device Manager, resolves this in most cases.
Yes — USB 3.0 emits RF noise directly in the 2.4GHz band used by wireless controller dongles. This is documented in Intel's own USB 3.0 radio interference white paper. Moving your dongle to a USB 2.0 port, or using a short USB extension to distance the dongle from USB 3.0 ports and external drives, resolves it. This is a physics problem, not a driver problem — no software fix will work.
Possibly, and easy to test. Try a different known-good USB data cable in a different port. If disconnects stop, the original cable was intermittently failing — a common late-life failure mode where the cable still charges but drops data mid-session. Rule out the cable before spending time on driver or setting fixes.
Run the connection stability test wired versus over Bluetooth. If wired shows no drops but Bluetooth drops frequently, the wireless path is the problem — treat it as interference (see the Bluetooth-specific page). If wired ALSO drops, it's not wireless at all; the issue is USB power management, the cable, or the driver. This is the fastest way to localize which family of fixes to apply.
Two common causes: wireless controllers dropping to below 20% battery start transmitting at reduced power, which produces intermittent disconnects that resolve after charging. Second, thermal issues in some USB dongles cause degraded signal after sustained use — moving the dongle to better airflow (or a USB extension) resolves the heat-driven pattern. The stability test's timestamp shows which pattern you have.
For controller-connected gaming, yes, if you experience disconnects. USB Selective Suspend saves a trivial amount of power on desktops (irrelevant) and modestly extends laptop battery (marginal). Disabling it costs almost nothing and eliminates one of the most common causes of mid-game controller drops on Windows. Most competitive-gaming setup guides recommend it.
Rarely, but yes. Steam Input's controller polling can conflict with Windows' native handling, particularly if both are trying to manage the same wireless controller simultaneously. If disconnects happen only in Steam games and stop when Steam is closed, adjust which controller types Steam Input handles (Settings → Controller) or set a per-game override to disable Steam Input for the affected title.
Still seeing the issue?
Re-run the diagnostic to confirm whether the fix held or whether escalation is needed.
Run the test again