Controller Not Connecting to PC
Controllers fail to connect to PC at four distinct layers: physical (USB port, cable, Bluetooth adapter), Windows driver (XInput, Bluetooth stack), Steam Input (which can hide controllers from non-Steam games), and per-game settings. Test wired first to isolate the layer, then work through driver state, Steam Input configuration, and game-specific input options.
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.
Gamepad Viewer
Before troubleshooting at the OS or game level, confirm whether the browser sees the controller at all. The gamepad viewer reads from the Gamepad API — if it detects the controller, the connection is fine and the issue is downstream (Steam Input, a specific game, or DirectInput vs XInput mismatch). If the browser doesn't see it, the connection is broken at the OS or driver layer.
Run the gamepad viewer- A USB cable matching your controller (data-capable, not charge-only)
- A second USB port on your PC (preferably USB 2.0, not USB 3.0)
- Administrator access on Windows (for driver updates)
Step by step
Work through these in order. After the last step, run the diagnostic again to confirm the fix held.
- 01
Test wired first to isolate the layer
Connect the controller to the PC with a known-good data cable. If the browser-based gamepad viewer detects it wired but not wirelessly, the issue is Bluetooth — skip to Step 4. If it works neither wired nor wirelessly, the issue is driver-level — continue to Step 2. If wired works but a specific game doesn't detect it, the issue is Steam Input or game-side input settings — skip to Step 5.
- 02
Try a different USB port
USB 3.0 ports (blue inside) emit electromagnetic noise in the 2.4 GHz band that can desensitize nearby Bluetooth receivers. They also have power-delivery quirks that occasionally cause controller detection to fail. If your controller works in a USB 2.0 port (black inside) but not a USB 3.0 port, the issue is USB 3.0 interference. Use USB 2.0 ports for controllers when possible, and keep USB 3.0 hubs and devices away from Bluetooth dongles.
- 03
Update or reinstall Windows controller drivers
Open Device Manager (Win+X → Device Manager), expand 'Human Interface Devices' and 'Bluetooth' if applicable. Find your controller — it may appear as 'Wireless Controller,' 'Xbox Wireless Controller,' or by manufacturer name. Right-click and select 'Update driver,' then 'Search automatically.' If that fails, uninstall the device (do not delete driver software unless instructed), unplug and re-plug the controller, and let Windows redetect it.
CautionOn Windows 11, the Xbox controller driver is bundled with the OS and updates automatically. For PS5 DualSense, DualSense Edge, and most third-party controllers, manufacturer driver installers exist (Xbox Accessories app, PlayStation Accessories for Windows, 8BitDo Ultimate Software). Don't install generic 'XInput drivers' from non-manufacturer sites — they're typically outdated or malware.
- 04
Reset the Bluetooth pairing on PC
Open Windows Settings → Bluetooth & devices. Find your controller, click the three dots, and select Remove. With the controller off, put it back in pairing mode (controller-specific procedure: DualSense holds Create + PS button, Xbox Wireless holds the pair button on top, Switch Pro holds the sync button next to the cable port). On the PC, click 'Add device,' select Bluetooth, and pair fresh. A clean pairing record resolves persistent detection failures.
- 05
Reconfigure Steam Input
Steam intercepts all controller input system-wide when Steam is running, regardless of which game you're playing. Open Steam → Settings → Controller, and check whether 'Steam Input' is enabled for your controller type (PlayStation, Xbox, Generic Gamepad, etc.). For non-Steam games, disable Steam Input or add the game to Steam as a non-Steam shortcut and configure input per-game. For games that need their own controller handling (Forza, racing simulators), disable Steam Input entirely for that controller.
- 06
Check per-game input settings
Some games default to mouse-and-keyboard and ignore connected controllers until manually enabled. Check the game's input or controls menu for 'Enable controller' or 'Use gamepad.' For competitive games with anti-cheat (Valorant, Apex Legends, Call of Duty), restart the game after connecting the controller — anti-cheat services occasionally lock the input device list at game start.
- 07
Try a different host or USB Bluetooth adapter
If steps 1–6 didn't resolve it, the PC's Bluetooth radio or USB controller is the bottleneck. Test the controller on a different PC, phone, or console to confirm the controller itself works. If it does, a USB Bluetooth 5.0 adapter ($10–15) often resolves PC-specific issues — built-in laptop Bluetooth shares its antenna with Wi-Fi, and many desktops ship with low-quality Bluetooth chips mounted inside the case where signal is weak.
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
Consoles ship with built-in driver and input handling for their first-party controllers. PCs require Windows to identify the controller and load the right driver — and if Steam is running, Steam Input adds another layer. Working on console but not PC almost always points to a driver or Steam Input issue, not the controller itself.
It depends on the game. Steam Input adds powerful features (custom configs, gyro aim, native PS5 haptics on PC) but it can interfere with games that handle controllers themselves. Forza, MLB The Show, and most racing simulators work better with Steam Input disabled. Most other games benefit from leaving it on. Toggle per-game in Steam → Properties → Controller.
Windows displays the generic 'Wireless Controller' label when it doesn't recognize the controller's specific manufacturer ID, which happens when the controller is connected over Bluetooth (where it presents as a generic HID device) rather than wired or via a proprietary dongle. Functionality is identical — the label is cosmetic.
On modern Windows, no. Windows 11 detects DualSense and DualSense Edge controllers natively over both USB-C and Bluetooth. DS4Windows and DualSenseX add advanced features (PS-button remapping, custom lighting, audio jack routing) but are not required for basic controller functionality. Try Windows-native first; install third-party tools only if you need their specific features.
Yes for both. macOS 11+ supports DualSense, Xbox Series X|S, and most third-party controllers natively. Linux supports controllers via the kernel's HID driver — most distributions detect them automatically. Steam on Linux uses the same Steam Input system as Windows. Console-proprietary features (DualSense haptics, adaptive triggers) work best through Steam Input on both platforms.
Anti-cheat services like EasyAntiCheat, Vanguard, and BattlEye don't block legitimate controllers, but they do lock the input device list at game start. If you connect a controller after launching the game, restart the game so anti-cheat re-enumerates the input devices. They also block macro-replay devices like the Cronus Zen, which is a separate concern.
Many Bluetooth controllers enter a sleep state after 5–15 minutes of inactivity to save battery. Windows may also turn off the Bluetooth radio for power saving. Check Device Manager → Bluetooth Adapter → Power Management and uncheck 'Allow the computer to turn off this device.' For controllers, simply pressing any button wakes them — disconnection during gameplay is a different issue covered in the broader disconnects guide.
Still seeing the issue?
Re-run the diagnostic to confirm whether the fix held or whether escalation is needed.
Run the test again