Gamepad Not Detected on PC
A gamepad your PC won't detect is almost always a driver, XInput registration, or hidden-device issue — not a pairing failure. The controller may be fully paired and powered while remaining invisible to Windows Game Controllers, games, or the browser. The button test triages instantly: if it appears there, Windows sees the controller.
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.
Button Test
The button test reads directly from the browser's controller interface — the same enumeration layer Windows exposes to games. If the button test detects the controller, Windows sees it and the failure is downstream (a specific game, Steam Input, DS4Windows, or a driver-profile conflict). If the button test sees nothing, the controller isn't being enumerated at the OS level and the fix is at the driver layer.
Run the button test- A USB data cable (to test both wired and wireless independently)
- A Chrome or Edge browser
- Windows admin access (for device-manager driver operations)
Step by step
Work through these in order. After the last step, run the diagnostic again to confirm the fix held.
- 01
Confirm what Windows actually sees
Open the button test in a browser and connect the controller. If buttons register as you press them, Windows sees the controller correctly and the problem is a specific game or launcher filtering it — skip to the software-layer steps. If nothing registers, open the Windows Game Controllers panel (Run → joy.cpl); a missing entry there confirms the controller isn't being enumerated at all and the fix is driver-level.
- 02
Try a wired connection first
Bluetooth and 2.4GHz dongles have their own separate enumeration paths, and wireless-only failures often trace to a Bluetooth driver bug rather than the controller itself. Connect a USB data cable (not a charge-only cable) and check the button test. If wired detection works and wireless doesn't, the fault is in the Bluetooth pairing or dongle enumeration, not the controller — and you've localized the problem to the wireless path.
- 03
Show hidden devices in Device Manager
Windows keeps ghost entries for controllers that have been paired before but aren't currently active, and these can block re-enumeration. Open Device Manager → View → Show hidden devices. Under 'Human Interface Devices' and 'Xbox Peripherals' look for greyed-out controller entries. Right-click each greyed-out entry → Uninstall device. Unplug, restart, and re-pair. Ghost devices are one of the most common causes of controllers that used to work but now aren't detected.
- 04
Reinstall the controller driver
In Device Manager, find your controller under 'Human Interface Devices' or 'Xbox Peripherals.' If it shows a warning icon, right-click → Uninstall device → tick 'Delete driver software' if offered → reboot. Windows will reinstall a fresh driver on next connect. For Xbox controllers specifically, the Xbox Accessories app can also perform a firmware-and-driver refresh. For DualSense, DS4Windows uses its own virtual driver that can be reinstalled from the DS4Windows app.
- 05
Check XInput vs DirectInput compatibility
Some games only support XInput (Xbox controller standard), others only DirectInput (older, generic), and third-party controllers vary in which they present as. If your controller is detected in the button test and Steam but a specific game can't see it, the game likely only speaks XInput and your controller is presenting as DirectInput. Tools like x360ce (for DirectInput→XInput translation) or the controller's own mode switch (many third-party controllers have an XInput/DirectInput toggle) resolve this. DS4Windows is the equivalent for DualSense.
- 06
Rule out Steam Input hijack
Steam Input intercepts controllers even outside Steam games if Steam is running and configured to. A controller that games can't see may be getting captured exclusively by Steam. Fully quit Steam (right-click tray icon → Exit, not close), and retest — if the game now sees the controller, the cause was Steam Input. In Steam → Settings → Controller, adjust which controller types Steam Input handles, or disable it globally for non-Steam games.
- 07
Retest USB ports and cables
If wired detection still fails, try a different USB port (prefer USB 2.0 for controllers — USB 3.0 ports have caused enumeration flakiness with some controllers historically), and confirm the cable carries data by using it to transfer files from another device. USB 3.0 RF interference in the 2.4GHz band is also a documented cause of dongle detection issues; move a 2.4GHz dongle to a USB 2.0 port away from any USB 3.0 ports or external drives.
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.
Key definitions
Plain-language definitions for the terms used on this page. Each links to the full glossary entry with thresholds, mechanism, and FAQs.
connection questions
The pairing (Bluetooth or USB link) and the enumeration (Windows registering the device as a usable controller) are separate systems. Your controller can be fully paired at the radio level while Windows still doesn't expose it to games, usually because of a driver problem, a stale ghost device entry from a previous session, or an XInput/DirectInput mode mismatch. The button test tells you which layer is actually broken.
Xbox controllers and Xbox-compatible third-party controllers are XInput. Older PC controllers, some fighting sticks, and DualSense in native mode present as DirectInput. Many third-party controllers have a mode toggle to switch. Games generally state which they support in their controller settings — if the game only offers Xbox-style prompts, it's XInput-only, and a DirectInput controller needs x360ce or DS4Windows to translate.
Two common causes: an XInput driver has failed to load (uninstall the controller in Device Manager with 'Delete driver software' checked, then reboot to force a fresh install), or Steam Input is intercepting the controller and preventing games from seeing it directly. Quit Steam fully and retest — if the controller works in games with Steam closed, Steam Input is the cause and its settings need adjusting.
Yes — one of the most common overlooked causes. Windows keeps hidden ghost device entries for controllers previously connected, and these can prevent proper enumeration of a new controller. Device Manager → View → Show hidden devices, then uninstall any greyed-out controller entries under HID and Xbox Peripherals, reboot, and re-pair.
Steam Input translates your controller into a virtual controller that only Steam games see. Outside Steam, only the raw controller matters — and if it's presenting as DirectInput while your game only supports XInput, the game genuinely can't see it. DS4Windows (for DualSense) or x360ce (for DirectInput controllers) bridge this by exposing the controller as a virtual Xbox pad to non-Steam games too.
They can. USB 3.0 ports leak RF noise in the 2.4GHz band, which interferes with 2.4GHz dongles for wireless controllers plugged into or near them — showing up as enumeration flakiness, intermittent disconnects, or wireless detection failure. Moving a dongle to a USB 2.0 port, or using a short USB extension cable to distance the dongle from USB 3.0 ports and external drives, resolves this cleanly.
Intermittent detection points at a physical or connection layer problem rather than a driver one. Check the USB cable is a data cable and connectors are seated firmly. For wireless, low battery reduces signal strength enough to cause dropouts that read as detection failure. The connection stability test measures the actual link quality — persistent flakiness there confirms the wireless path is the issue rather than the controller itself.
Still seeing the issue?
Re-run the diagnostic to confirm whether the fix held or whether escalation is needed.
Run the test again