Why is my controller connected but not working in games?

This is almost always a software-side conflict, not a hardware fault. Another program—Steam Input or DS4Windows are the most common culprits—may be holding exclusive access to the controller, preventing the game from detecting it properly. Some games also require controller support to be enabled separately from your operating system settings. Testing the controller outside the game first confirms whether the hardware itself is functioning correctly. If the controller works normally in a browser-based tester or another application, the issue is almost certainly related to software configuration, drivers, or the game's controller settings rather than the controller itself.

Why does my controller work in one game but not another?

This usually points to a game-specific configuration or an input API mismatch rather than a broken controller. Some games only support XInput devices and may ignore DirectInput controllers entirely, while others require controller support to be enabled manually in the game's settings. Different games also implement controller compatibility differently, so a controller that works perfectly in one title may require additional configuration in another. If the controller registers correctly in a controller tester and functions properly in other games, the hardware is working as intended.

Does a factory reset fix a controller?

Sometimes. A factory reset can resolve software-related problems such as corrupted Bluetooth pairing information, incorrect configuration data, or temporary firmware glitches that affect controller behavior. However, a reset cannot repair physical hardware problems like stick drift caused by worn potentiometers, damaged thumbsticks, broken buttons, failing trigger mechanisms, or cracked button membranes. If the issue is caused by mechanical wear or internal damage, the controller will require cleaning, repair, or replacement rather than a factory reset.

Can a firmware update fix controller problems?

Yes. Firmware updates released by controller manufacturers often include fixes for Bluetooth connectivity issues, USB communication bugs, input latency, compatibility with newer operating systems, battery performance, and controller stability. Apps such as Xbox Accessories for Xbox controllers or PlayStation's official update tools for DualSense controllers can install these updates. Before assuming your controller has a hardware fault, it is worth checking whether a newer firmware version is available, as many connection and performance issues can be resolved through a firmware update.

Why does my controller work on console but not on PC?

Consoles and PCs use different drivers, communication methods, and controller input standards. A controller that pairs automatically with its native console may require specific drivers, Bluetooth profiles, Steam Input configuration, or third-party software such as DS4Windows to function correctly on Windows. Some controllers also switch between XInput and DirectInput modes depending on the platform. In most cases, this is a compatibility or configuration issue rather than evidence that the controller itself is broken.

Is stick drift covered under warranty?

In many cases, yes. Several controller manufacturers consider stick drift to be a manufacturing defect when it appears during the warranty period, although warranty coverage varies by brand, country, and purchase date. If your controller is still covered, document the drift using a controller testing tool that displays raw analog stick values before contacting customer support. Providing measurable evidence of the problem can help speed up the warranty claim process. Always review your manufacturer's current warranty policy for the exact terms and conditions.

How do I know for certain if it’s the controller or a setting?

The easiest way to determine this is to test the controller independently of any game using a controller tester that reads raw input directly from the browser or operating system. If every button, trigger, thumbstick, D-pad, and analog axis responds correctly during testing, the controller hardware is functioning properly. That means the remaining problem is almost certainly caused by game settings, controller mapping, drivers, software conflicts, or platform compatibility rather than a hardware failure. Independent testing helps separate hardware issues from software configuration problems with confidence.

Why Is My Controller Not Working? A Complete Diagnostic Guide

A controller your device doesn’t recognize at all is almost always a cable, port, or pairing problem, not a broken controller. A controller that is recognized but does nothing in-game is usually a software conflict, like another app holding exclusive access. A controller where only specific buttons or sticks fail is the clearest sign of real hardware wear. Identify which of these three you’re dealing with before trying any fix, or you’ll waste time solving the wrong problem.

Most troubleshooting guides skip straight to “reinstall your drivers” without ever confirming that’s where the fault actually lives. We built this guide the other way around: start by isolating the failure mode, then go straight to the fix that matches it, no reinstalling, no re-pairing, no guessing.

How We Tested This

The failure-mode framework below wasn’t written from theory, it’s based on running dozens of Xbox, PlayStation, Switch Pro, and third-party controllers through our own gamepad tester across Windows, macOS, and Linux, deliberately reproducing each failure type (unplugged data lines, stale Bluetooth pairings, exclusive-access conflicts, worn analog sticks) to confirm which symptoms map to which root cause. Where a fix requires platform-specific steps beyond the scope of this diagnostic (like a full Xbox pairing walkthrough or a full stick-drift repair), we link to our dedicated guides rather than compress those steps here.

If you want to follow along as you read, open the tester in a second tab, every input you press will appear on screen instantly, which is the fastest way to confirm whether your controller’s signal is actually reaching your computer at all.

The Four Failure Modes

Failure mode	What you’ll notice	Most likely cause
Not detected at all	No light, no entry in system settings, nothing happens on button press	Cable, port, pairing, or missing driver
Detected but unresponsive	Shows as connected but nothing registers in-game	Exclusive-access conflict, API mismatch (XInput vs. DirectInput), or a per-game setting
Partially working	Some buttons or sticks work, others don’t	Hardware wear – worn potentiometer, cracked membrane, failing contact
Intermittent	Works, then randomly drops or freezes	Wireless interference, low battery, or a loose connection

If you’re unsure which category applies, connect your controller to the tester and press any button. If inputs light up on screen in real time, the hardware is being read correctly, your problem lives between the OS/browser and the specific game. If nothing appears, you’re in “not detected” territory.

Failure Mode 1: Not Detected At All

This means the computer or console isn’t recognizing the controller exists, a different problem than recognizing it and failing to read its inputs.

Diagnostic steps, in order:

Check the cable first. Many USB-C and micro-USB cables are charge-only and carry no data lines. Swap in a known-good data cable – ideally the one that shipped with the controller.
Try a rear, direct-to-motherboard USB port. Front-panel and hub-connected ports are common sources of insufficient power delivery or flaky data connections.
Rule out the “wake-up” behavior. Browsers and some OS-level tools intentionally won’t display a connected controller until you press a button on it, this is a privacy-driven design choice in the Gamepad API standard, not a fault. Press a button before assuming it’s undetected.
Check Device Manager (Windows) under “Human Interface Devices” or “Other devices” for a yellow warning icon, which points to a driver issue rather than a hardware one.
For Bluetooth controllers: confirm pairing mode is actually engaged (button combinations differ by brand, see the platform table below), and delete any old paired entry before re-pairing. Stale pairings are one of the single most common causes of silent Bluetooth failures.

What we actually found testing this: in the majority of “not detected” cases we reproduced, the controller itself was functioning fine, the fault traced back to a charge-only cable or a stale Bluetooth pairing entry, not the controller. Treat “broken controller” as the last conclusion, not the first assumption.

For a full Xbox-specific pairing walkthrough, see our step-by-step Xbox pairing guide. For general first-time PC setup across controller brands, see our PC controller setup guide.

Failure Mode 2: Detected But Not Working In Games

This is the most confusing failure mode because everything looks fine – the OS reports the controller as connected, yet nothing happens in a game.

Three most common causes:

Exclusive access conflicts. Software like Steam Input or DS4Windows can claim exclusive control of a controller at the driver level, silently blocking your browser or a different game from reading it. Close other controller, managing software before testing.
Input API mismatch. Modern PC games generally expect the XInput standard; older or third-party controllers often speak DirectInput only. Without a translation layer, some games simply won’t read a DirectInput-only pad.
Per-game controller settings. Some games ship with their own controller-detection toggle, independent of your OS-level settings, that can silently disable input.

How to isolate it: close the game entirely and open the tester. If every button and stick registers correctly there, the controller and its connection are both confirmed fine, the fault is specific to how that one application handles input, not the hardware. This single check eliminates an entire category of unnecessary fixes (driver reinstalls, cable swaps, re-pairing).

Fix checklist:

Close Steam, DS4Windows, and any other background controller software, then relaunch only the game
In Steam, check Settings → Controller → General Controller Settings and toggle Xbox/PlayStation configuration support
Check the game’s own input settings for a controller-enable toggle
Update the controller driver via Device Manager only after the above steps are ruled out

Failure Mode 3: Some Inputs Work, Others Don’t

This is the clearest sign of genuine hardware wear, because a connection or driver problem typically affects the whole controller, not isolated buttons or sticks.

Most modern analog sticks use one of two sensing technologies: traditional potentiometers, which wear down mechanically and are the primary cause of stick drift, or newer Hall effect sensors, which use magnetic sensing and are far more resistant to drift over time. If your controller is a few years old and uses potentiometer-based sticks, drift is a wear pattern, not a defect.

Symptom	Likely hardware cause	Confirm it here
One or two buttons don’t register	Cracked rubber membrane or worn contact	Button Test
Stick moves the camera/character on its own at rest	Worn potentiometer (stick drift)	Stick Drift Test
Stick feels unresponsive near center	Dead zone miscalibration	Joystick Deadzone Test
Trigger doesn’t reach full pull	Worn trigger potentiometer	Trigger Pressure Test
No rumble/haptic feedback	Damaged vibration motor, or OS/browser vibration permissions	Vibration Test
Buttons trigger the wrong action	Mapping/API mismatch – not physical damage	Controller Mapping Test
Inputs feel delayed	Input lag, not necessarily damage	Latency Test

Bumpers (LB/RB, L1/R1) are typically the first buttons to fail on most controllers, due to their plastic hinge mechanism , test them repeatedly rather than once, since intermittent bumper failure is easy to miss on a single press.

If stick drift is confirmed, our full stick drift repair walkthrough covers cleaning, recalibration, and module-replacement options in depth. If it’s a calibration issue rather than physical wear, calibrating your Xbox controller may resolve it without any repair at all.

Failure Mode 4: Works, Then Randomly Stops

Intermittent failures point toward connection stability, not a permanently broken component.

Common causes:

Wireless interference from other 2.4GHz devices (routers, other peripherals, microwaves)
Low battery, many wireless controllers behave erratically before shutting off cleanly, rather than failing all at once
A loose or damaged USB port/cable connection
Bluetooth range or physical obstruction
Outdated controller firmware (Sony’s DualSense and Microsoft’s Xbox controllers both receive periodic firmware updates via their companion apps that can resolve connection bugs)

How to confirm it: run the Connection Stability Test for at least 15–30 seconds while gently moving the controller and cable, and while relocating closer to your device if wireless. A genuine connection issue shows up as dropped signal during the test, not a one-time fluke.

Platform-Specific Quick Reference

Platform	Check first	Controller-specific step
Windows PC	Device Manager for driver warnings	Uninstall the driver, then reconnect to force a clean reinstall
PS5 controller (DualSense) on PC	Whether Bluetooth/USB is actually paired vs. just charging	Enable PlayStation Configuration Support in Steam; try Xbox Configuration Support if PlayStation mode isn’t recognized
Xbox controller on PC	Xbox Wireless Adapter vs. Bluetooth	Xbox controllers have the deepest native Windows support; driver issues are less common but still worth ruling out first
Nintendo Switch Pro / Joy-Con	Sync button held the full 3 seconds	Windows 10/11 includes native drivers, but pairing often needs redoing after extended time unpaired
Any Bluetooth controller	Remove the old paired device entirely before re-pairing	Stale pairings are one of the most common silent failure causes
Linux	Bluetooth support varies by distro and isn’t reliably exposed via the browser Gamepad API	Use a wired USB connection for the most reliable test
macOS	Whether the controller appears under Bluetooth settings as “Connected” (not just “Paired”)	DualSense and Xbox controllers both have native macOS support since recent OS versions

Decision Framework: Repair, Replace, or Neither?

Situation	Recommended action
Not detected, but tests fine on a different cable/port	No repair needed, it was a connection issue
Detected, tests clean in the tester, but fails in one specific game	Software/game-side fix, not a hardware problem
One or two buttons/sticks fail consistently in the tester	Repairable – replacement stick modules and button membranes are inexpensive and widely available
Widespread failure across many inputs, or the controller is several years old	Consider replacement, especially if repair-part cost approaches the price of a new unit
Recently purchased and already showing hardware faults	Contact the manufacturer or retailer directly, this is very likely covered under warranty

Common Mistakes to Avoid

Reinstalling drivers before confirming detection. If the controller isn’t recognized at all, a driver reinstall does nothing until the cable/port/pairing issue is resolved.
Testing only once. Intermittent issues, loose connections, early-stage drift, wireless interference, often won’t show up in a five-second check. Run tests for at least 15–30 seconds, both at rest and in motion.
Assuming “connected” means “working.” As shown in Failure Mode 2, a controller can be fully recognized by the OS and still fail every input inside a specific game.
Cleaning contacts with the wrong materials. If you suspect a dirty contact rather than a worn part, use isopropyl alcohol (90%+) and a soft brush, never household cleaners, which can leave residue that makes the problem worse.
Skipping a documented test before a warranty claim. A repeatable, exported test result is far more useful to a manufacturer’s support team than a verbal description of “it doesn’t work sometimes.”

Key Takeaways

Identify the failure mode first, not detected, detected-but-unresponsive, partially working, or intermittent, before attempting any fix
“Connected” and “working” are not the same thing; confirm which one applies to your situation
Isolated input failures point to hardware wear; total failure across every input usually points to connection or driver issues
Testing outside of any specific game is the fastest way to separate a controller problem from a software problem
A documented, repeatable test result is more useful for warranty claims and used-controller purchases than a one-time observation

Test Your Controller Now

The fastest way to move from guessing to knowing is to run your controller through a live diagnostic. Open the free gamepad tester, connect via USB or Bluetooth, and press any button to begin, every input appears on screen in real time, with no installation required.

Frequently Asked Questions (FAQs)

This is almost always a software-side conflict, not a hardware fault. Another program – Steam Input or DS4Windows are the most common culprits – may be holding exclusive access to the controller, or the game itself may need its controller support toggled on separately from your OS settings. Testing the controller outside the game first confirms whether the hardware itself is fine.

This points to a per-game setting or an input-API mismatch rather than a broken controller. Some games only support XInput and will silently ignore a DirectInput-only pad; others have their own controller toggle buried in settings. If the same controller works fine in other games and in the tester, the hardware isn’t the issue.

Sometimes, for software-level glitches – a reset can clear a corrupted pairing profile or a stuck firmware state. It will not fix physical wear like stick drift or a cracked button membrane, since those are mechanical issues a reset can’t touch.

Yes, in some cases. Manufacturer companion apps (the Xbox Accessories app, the PS5 companion app) occasionally ship firmware updates that resolve connection drops or input lag. It’s worth checking before assuming a connection issue is a hardware fault.

Different platforms use different drivers and input standards. A controller that pairs natively on a console may need a specific Bluetooth mode, a driver, or third-party software (like DS4Windows) to be read correctly on PC – this is a compatibility gap, not a broken controller.

Often yes, particularly within the first year, since many manufacturers treat drift as a defect claim rather than normal wear during the warranty period. Check your specific manufacturer’s policy, and keep a documented test result showing the drift on hand if you file a claim.

Test the controller independently of any game, using a tool that reads raw input data directly rather than relying on a game’s own input display. If every button, stick, and trigger registers correctly there, the hardware is confirmed fine and the issue is specific to how a particular game or app is handling input.