Controller Not Working or Detected on PC? Fixes
A controller that won't show up on PC — dead in-game, or invisible to a browser tester even though it's plugged in — is almost always a software handshake, not a broken pad. The most common single reason a web tester shows nothing is that browsers hide the controller until you press a button with the page focused; plugging in is never enough. Work these fixes in order of how often they're the actual cause, and use the tester to prove the pad is alive before you touch a single game setting.
Press a button first — plugging in is never enough
If a browser-based tester says "no controller" while the pad is clearly connected, this is almost always why. By the Gamepad API spec, navigator.getGamepads() returns an empty list until the browser sees a "gamepad user gesture" — a button press or a stick movement while the page has focus. No connection event fires on plug-in or pairing alone. It's a deliberate anti-fingerprinting privacy measure, not a fault in the site or your pad.
So the fix is literally: click the page to focus it, then press any button or nudge a stick. The controller appears the instant you do. This is also exactly how our gamepad testeris meant to be used — connect, click, press, and every input lights up.
Prove the pad is alive first: open the gamepad tester, click anywhere on the page, and press a face button. If it registers here, your hardware and drivers are fine — the problem is a game or a setting, and the sections below apply. If it stays blank even after a button press, check the cable next.
Two things still block it even after a press: a charge-only USB cable with no data lines (swap for a known data cable), and another app holding exclusive HID access — a game running in the background, or Steam capturing the device — which can stop the browser seeing raw input. Close those and try again.
Isolate it: try wired USB first
Before you troubleshoot wireless, rule it out. A wired USB connection is the lowest-friction, lowest-latency, most reliable path for both DualSense and Xbox pads. If the controller works wired but not wirelessly, you have a Bluetooth or dongle problem and can skip straight to that section. If it fails even wired, it's a driver, cable, or software-conflict issue, not a radio one.
Steam Input is intercepting your controller
When Steam Input is active, Steam creates a virtual controller and feeds games its processed input instead of the raw device. That's great inside Steam and confusing everywhere else: a non-Steam game or a second remap layer may not expect the virtual pad, giving "not detected" or "detected but unresponsive" — or, when both the real and virtual devices are visible, double inputs(a menu skipping two items, a doubled jump).
- Toggle it per game. Right-click the game in your Steam library →
Properties → Controller→ set Steam Input to Enabled, Disabled, or Forced-Off for that title. In Big Picture, the same override lives under Controller Options. - Kill double inputs with HidHide. HidHide is a free, open-source, kernel-level Windows driver that hides selected physical controllers from every app except a whitelist. Run the HidHide Configuration Client as Administrator, open the Devices tab, check the physical (duplicate) controller, make sure device hiding is enabled, then whitelist the app that should use it (Steam.exe, DS4Windows). Settings persist across reboots.
Why HidHide rather than a Steam toggle? Modern Steam's "New Big Picture" removed the old "Hide Device" option, so a dedicated hider became the reliable way to stop the OS exposing a duplicate.
Bluetooth vs USB vs the Xbox Wireless Adapter
Wireless is where "detected but flaky" lives. The three paths aren't equal:
- Wired USB — the reliable default. Use it to isolate every other problem.
- Bluetooth — convenient, but higher and less consistent latency, and it has a known Windows 11 quirk with the DualSense specifically: Windows sometimes won't even list the pad. Documented workarounds are to remove and re-pair from scratch, run the Bluetooth troubleshooter, and — reported by users — roll the Bluetooth driver back below version
23.40.0.2. That last one is a lead to try, not a universal cure. - Xbox Wireless Adapter (about $24.99) — a proprietary 2.4GHz dongle, not Bluetooth. It gives near-wired latency, connects up to eight controllers at once, and carries headset audio and chat that Bluetooth doesn't. If Bluetooth stays unreliable, this is the fix worth buying.
Getting into pairing mode
On a DualSense, first hold the PS button to turn the pad off and unplug any cable, then hold Create + PS together for a few seconds until the light bar blinks rapidly — that's pairing mode. On an Xbox pad, hold the Pair button on the top edge until the Xbox logo flashes quickly, then select it in Windows Bluetooth settings.
XInput vs DirectInput (and why DS4Windows still matters)
A game written for one input API simply won't see a controller that only speaks the other. XInput(2005, built for Xbox 360 pads) is the modern, auto-detected standard with rumble support — but it's hard-capped at four controllers and a fixed button/axis layout. DirectInput(1995) is older and more flexible — up to 128 buttons, more axes, POV hats, wheel force feedback — but needs manual configuration and doesn't natively do Xbox-pad rumble.
PlayStation controllers present as generic HID / DirectInput-style devices, not XInput, which is precisely why translation tools exist for them on PC. In 2026, DS4Windows (still actively maintained) and DualSenseX remain useful: Windows 11 covers basic DualSense input natively, but full haptics and adaptive-trigger resistance still need one of those bridges or native in-game support. If a game insists on an "Xbox controller," running a PlayStation pad through DS4Windows presents it as an XInput device the game will accept.
Multiple controllers fighting over player slots
Local co-op setups hit a specific bug: Windows hands each Xbox-type pad one of four hidden XInput slots, and if a process keeps a slot's handle open, that slot gets "stuck." New controllers then land on unexpected player numbers, or every pad keeps grabbing the same slot regardless of the order you plug them in.
- Unplug all controllers, then reconnect them one at a time in the player order you want.
- Disable Xbox Game Bar (
Settings → Gaming → Xbox Game Bar) — it can claim exclusive controller access in some modes. - Remember the ceiling: XInput itself tops out at four pads. A five-plus-player local setup needs a DirectInput or translation-layer route; more Xbox controllers alone won't do it.
What doesn't work
- "Plugging it in should make a browser tester detect it instantly." No — the spec requires a button press or stick move first, by design. A blank tester on plug-in is expected behavior.
- "DS4Windows and DualSenseX are obsolete now that Windows 11 supports PlayStation pads." Only half true. Basic input is native; adaptive triggers and full haptics still need a bridge tool or native game support.
- "Bluetooth is just as good as a cable or the Xbox adapter." Not for timing. Bluetooth latency runs materially higher and less steady than a USB cable or the 2.4GHz adapter.
- "More than four Xbox pads just works." XInput is hard-capped at four simultaneous controllers — no amount of plugging in gets you a fifth through XInput alone.
Frequently asked questions
Why does my gamepad tester say no controller connected even though it's plugged in?
Because the browser deliberately hides the controller until you press a button or move a stick with the page focused. The Gamepad API returns an empty list until that first input — it's a privacy measure against fingerprinting, not a bug on the site. Click the page, then press any button, and the pad appears instantly. A charge-only USB cable with no data lines will never register no matter what you press.
How do I stop Steam from double-inputting my controller?
Double inputs happen when a remap tool creates a virtual pad while Windows still exposes the original physical one, so the game sees both. The clean fix is HidHide-style device hiding: install HidHide, hide the physical controller from all apps, and whitelist only the app that should use it (Steam.exe or DS4Windows). You can also set Steam Input to Forced-Off per game under Properties → Controller.
Do I need DS4Windows for a PS5 controller on PC in 2026?
Only for the fancy features. Windows 11 handles basic DualSense button and stick input natively, so most games just work over USB or Bluetooth. But adaptive-trigger resistance and fine-grained haptics still need either native in-game DualSense support or a bridge tool — DS4Windows (actively maintained into 2026) or DualSenseX. For plain input, skip it; for full haptics, keep it.
Is Bluetooth or the Xbox Wireless Adapter better?
The Xbox Wireless Adapter wins for play. It's a proprietary 2.4GHz dongle (around $24.99) giving near-wired latency, support for up to eight controllers at once, and stereo headset audio that Bluetooth can't carry. Bluetooth's only advantage is needing no extra hardware — its latency is higher and less consistent, so for anything timing-sensitive, use the adapter or a USB cable.
Why does my second controller register as player 3 instead of player 2?
Windows assigns each Xbox-type pad to one of four hidden XInput slots, and a process holding a slot open can leave it "stuck," pushing new pads to unexpected player numbers. Unplug every controller, then reconnect them one at a time in the order you want. Disabling Xbox Game Bar (Settings → Gaming → Xbox Game Bar) also helps, since it can claim controller access.