Your controller works fine on the desktop or in other launchers, but the moment you open a game through Steam, nothing happens. The icon never appears in the controller overlay, Big Picture mode shows no input, or the game flat-out ignores every button press. Sometimes Steam detects the device but only half of it works — the thumbsticks move but triggers are dead, or gyro is missing entirely.
The good news: this is almost never a broken controller. In the overwhelming majority of cases the problem is a Steam input setting, a driver conflict, or another program grabbing the device first. Most of the fixes below take under five minutes, and you can work through them from easiest to hardest without reinstalling anything. Set aside 20–30 minutes and you should be back in the game.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| Steam Input is disabled or misconfigured for your controller type | Steam → Settings → Controller shows “Not Detected” or the wrong device type; game properties have generic/gamepad config instead of your controller layout | Easy |
| Steam’s controller service crashed or didn’t start | SteamInput service missing from Task Manager’s Services tab; controller works after a full Steam restart | Easy |
| Another program has exclusive access to the device | Controller works in Notepad/gamepad tester but not Steam; apps like DS4Windows, JoyToKey, or G HUB are running in the system tray | Easy |
| Outdated or broken USB/Bluetooth drivers | Device Manager shows a warning icon under “Human Interface Devices” or “Xbox Peripherals” | Medium |
| Cable, port, or pairing issue | Controller works on another PC or with another cable; drops out intermittently | Easy |
| Corrupted Steam configuration files | The problem started after a Steam update or a crash; settings reset on their own | Hard |
Fix 1: Restart Steam Completely
What causes it
Steam’s controller handling runs through a background service (SteamInput) that can hang after a Windows sleep cycle, a driver hiccup, or a Steam update. When it hangs, Steam stops polling connected gamepads entirely even though Windows still sees them.
How to check
If your controller works in Windows (press the Windows key and navigate with the D-pad, or open joy.cpl from the Run dialog and see input register), but not in Steam, the service is a likely culprit. If a simple in-Steam toggle doesn’t help, that points further toward a hung process.
What to do
Don’t just click the X — Steam often keeps running in the tray. Open Steam, click Steam in the top-left menu, and choose Exit. Then open Task Manager (Ctrl+Shift+Esc), find any remaining “Steam Client Bootstrapper” or “steamwebhelper” processes, and end them. Relaunch Steam from the Start menu and reconnect your controller.
How to undo it
Nothing to undo — a restart changes no settings.
Fix 2: Reconnect the Controller (Cable, Port, or Re-Pair)
What causes it
Loose USB connections, flaky front-panel ports, underpowered USB hubs, and stale Bluetooth pairings are extremely common. Windows may have silently dropped the device, and Steam never saw it in the first place.
How to check
Press Win+R, type joy.cpl, and hit Enter. If your controller doesn’t appear in the Game Controllers list, this is a Windows-level connection problem, not a Steam problem. Try a different USB port — ideally a rear motherboard port on a desktop — and skip hubs entirely.
What to do
For wired controllers, swap to a known-good data cable (many cheap cables are charge-only). For Bluetooth, remove the device: Settings → Bluetooth & devices, click the three dots next to your controller, choose Remove device, then re-pair by holding the pairing button until the light blinks rapidly. Xbox controllers can also be re-paired with the Wireless Adapter by holding its pair button for a few seconds.
How to undo it
Reconnect through your original port or re-add the old Bluetooth pairing if you preferred it.
Fix 3: Check Steam’s Controller Settings and Enable Steam Input
What causes it
Steam Input is Steam’s translation layer that converts controller input into a format every game understands. If it’s turned off for your controller type, or if the wrong device type is selected, games will ignore the pad even though Steam sees it. Recent Steam versions also let you override settings per-game, and an old override can block detection in one title only.
How to check
In Steam, go to Steam → Settings → Controller. Confirm your controller is listed and recognized under the correct type. Then right-click the affected game in your library, choose Properties → Controller, and check the “Override” dropdown.
What to do
In Settings → Controller, make sure your controller’s Steam Input toggle is On (for example, “Xbox Controller Support” or “PlayStation Controller Support”). In the game’s Properties → Controller override, set it to “Enable Steam Input” if the game uses an unusual input API, or “Disable Steam Input” if the game has native support and behaves worse with the layer on — toggling between the two resolves a surprising number of cases. After changing it, fully restart the game.
How to undo it
Set the override dropdown back to “Use Default Settings” and toggle your controller support switch back to its previous state.
Fix 4: Close Conflicting Input Software
What causes it
Programs like DS4Windows, reWASD, JoyToKey, Xpadder, Logitech G HUB, Razer Synapse, and Nvidia GeForce Experience’s controller features create virtual controllers or hook raw input. If one of them grabs your physical pad first, Steam either sees a phantom duplicate controller or sees nothing at all.
How to check
Open joy.cpl again. If you see two entries for one controller, or an entry named something like “vXbox” or “Virtual Gamepad,” a remapping tool is active. Check the system tray for running utilities you may have forgotten about.
What to do
Close every input utility — right-click the tray icon and Quit, not just minimize. If DS4Windows is installed but unused, uninstall it and delete its virtual driver: run ScpToolkit’s driver installer/uninstaller or use the “Remove” option in DS4Windows’ driver menu. Then unplug and replug the controller so Windows rebuilds a clean device entry.
How to undo it
Relaunch the utility you closed; its settings are untouched. Reinstalling a removed virtual driver just requires running the tool’s installer again.
Fix 5: Update or Reinstall the Controller Driver
What causes it
A bad Windows update, an interrupted driver install, or a chipset driver mismatch can leave the controller’s driver corrupted. Steam can’t enumerate a device Windows itself can’t initialize properly.
How to check
Open Device Manager (right-click Start → Device Manager). Look under “Human Interface Devices,” “Xbox Peripherals,” or “Universal Serial Bus controllers” for any device with a yellow warning triangle. Note the exact device name first.
What to do
Right-click the controller entry and choose Uninstall device, then check “Attempt to remove the driver for this device” if offered. Unplug the controller, restart Windows, and plug it back in — Windows will rebuild the driver. If warnings persist, update your motherboard’s USB chipset drivers from the manufacturer’s support page, and for Bluetooth controllers update the Bluetooth radio driver the same way. Avoid third-party driver-updater tools; manual installs from the hardware vendor are safer.
How to undo it
In Device Manager, right-click the device → Properties → Driver tab → Roll Back Driver, if the option is available, or reinstall the previous driver version you noted.
Fix 6: Disable Steam Input Per-Game or Switch Beta Participation
What causes it
Occasionally a Steam client update ships a Steam Input change that breaks a specific controller or a specific game’s input API. These regressions are usually fixed quickly, but the beta channel can either introduce or resolve them depending on the current build.
How to check
If the problem began immediately after a Steam client update, and other controllers or other games still work fine, you’re likely looking at a client-side regression rather than a local misconfiguration.
What to do
First try the opposite Steam Input setting for the affected game (Fix 3 covers the path). If that fails, switch client builds: Steam → Settings → Interface, find the “Client Beta Participation” dropdown, and select a different channel (or “Steam Beta Update” if you’re currently on stable). Restart Steam when prompted. Builds change periodically, so test whichever channel you’re not currently on.
How to undo it
Return the Client Beta Participation dropdown to its original setting and re-enable your preferred Steam Input override.
Fix 7: Reset Steam’s Controller Configuration Files
What causes it
Steam caches per-controller layouts and calibration data in local configuration files. A crash mid-write or a botched update can corrupt these, and Steam will then fail to initialize the device every launch until the cache is cleared.
How to check
This is the right fix if the problem survives a Steam restart, affects all games, and started abruptly without any hardware change. There’s no direct confirmation — it’s the last software-side step before reinstalling.
What to do
Fully exit Steam (Fix 1). Open the folder C:\Program Files (x86)\Steam\config and rename config.vdf to config.vdf.bak. In your Documents folder, also check My Games for controller-related caches if your launcher uses them. Relaunch Steam — it regenerates a fresh config.vdf. You’ll lose custom Steam Input layouts, but you can restore them by renaming the backup file back.
How to undo it
Close Steam, delete the newly generated config.vdf, rename config.vdf.bak back to config.vdf, and restart Steam.
If Nothing Works
At this point the issue is almost certainly hardware. Test the controller on another PC or a console: if it fails there too, the controller itself is faulty, and for wired pads a replacement cable is a cheap first test. If it works elsewhere, the problem is your PC — try a full reinstall of Steam (your games and saves stay intact; uninstalling doesn’t touch library folders), test in a clean Windows user account to rule out profile-level software, and as a last resort check your motherboard vendor’s site for a BIOS update, since USB controller firmware bugs do occasionally cause exactly this symptom. If the controller is a PlayStation or Xbox official pad, the manufacturer’s firmware updater — Xbox Accessories app for Microsoft pads, the DualSense updater via a Windows PC — is worth running before you declare it dead.
FAQ
Why does my controller work in Big Picture mode but not in games?
That usually means Steam Input is enabled globally but disabled for that specific game. Open the game’s Properties → Controller and check the override setting; set it to “Enable Steam Input” unless the game has native support that conflicts with it.
Does Steam support all controllers natively?
Steam has built-in support for Xbox, PlayStation, Nintendo Switch Pro, and Steam Controllers, plus generic XInput and DirectInput pads. Exotic or older DirectInput-only controllers often need Steam Input enabled to be translated into XInput, which is why toggling it fixes so many detection problems.
Can a wireless controller cause input lag or detection drops?
Yes. 2.4 GHz wireless adapters and Bluetooth compete with Wi-Fi on crowded channels. If the controller disconnects intermittently, move the dongle to a front USB port or a short extension cable, keep it away from USB 3.0 ports, and reduce the number of active Bluetooth devices nearby.
Should I leave Steam Input on all the time?
For most modern games with native controller support, disabling Steam Input gives slightly more direct, lower-latency input. For older games, emulated titles, or games with poor gamepad menus, Steam Input adds gyro support, touch menus, and per-game layouts. Enable it per-game based on how each title behaves rather than forcing one global setting.
