Steam controller double input can make one physical gamepad behave like two controllers, move two players at once or register every button press twice. That problem has been especially relevant in September 2026 because Valve’s September 21 Steam Client Beta notes specifically say the client fixed doubled Xbox-style controllers on Windows.
If the issue started suddenly and Windows still sees only one controller, treat Steam itself as the first suspect rather than immediately removing drivers or changing every game setting. A client-side detection problem can affect several games at once even when the controller is working normally outside Steam.
Steam controller double input: update Steam first
The first fix for Steam controller double input is to install the newest Steam client build and restart the client completely. Valve’s September 21 beta update included a direct fix for Windows systems showing doubled Xbox-style controllers, so an older client can leave you troubleshooting a bug Valve has already addressed.
- Close the game where inputs are doubled.
- Open Steam and install any available client update.
- Choose Steam > Exit rather than only closing the window.
- Reconnect the controller after Steam has fully restarted.
- Open Settings > Controller and check how many devices Steam now shows.

Check whether Steam sees one controller or two
Steam controller double input is easier to diagnose when you separate a Steam detection problem from a game-specific binding problem. Open Steam’s Controller settings with only the affected gamepad connected. If Steam shows two entries for one physical controller, the duplicated device is the important clue.
Disconnect other gamepads, adapters and virtual controller tools while testing. A wheel, HOTAS, Bluetooth controller, remapping utility or virtual gamepad can legitimately create another input device, which is a different problem from Steam displaying the same Xbox-style controller twice.
Use the Steam Client Beta if the stable client still doubles the controller
If Steam controller double input continues on the stable client, the September 21 fix may not yet be present in the build installed on your PC. Steam’s Client Beta is the place where Valve published the fix. You can check Steam’s settings for Client Beta Participation, install the beta build, restart Steam and test the controller again.
Do this as a targeted test rather than changing several things at once. If the controller appears once after the beta update, you have a much stronger indication that the duplicated-device bug was the cause. If it still appears twice, move on to connection and Steam Input checks.
Reconnect the controller and test Steam Input
For Steam controller double input that survives a client update, disconnect the controller, restart Steam and reconnect it after the client is open. For Bluetooth controllers, remove and pair the controller again only if the duplicate entry returns after a clean restart.
Next, open the affected game’s Properties and check its Controller section. If the game supports Steam Input, test the normal Steam Input setting before creating custom layouts. If the problem exists in only one game while Steam itself lists a single controller, reset that game’s controller configuration before changing Windows drivers.
Do not uninstall random drivers for Steam controller double input
One detailed September bug report showed the same physical Xbox controller being opened through two Windows input paths, but that does not mean every Steam controller double input case has the same driver-level cause. Valve’s own beta notes describe a client fix, so updating Steam is safer and more relevant than deleting HID, GameInput or Xbox driver entries without a specific reason.
If Windows itself shows duplicate controllers outside Steam, or the gamepad behaves incorrectly in non-Steam software, the fault is broader than this Steam bug. In that situation, update the controller firmware and Windows first, then troubleshoot the device at operating-system level.
Steam controller double input quick checklist
- Install the newest Steam client update.
- Exit and restart Steam completely.
- Connect only one controller while testing.
- Check whether Steam lists one device or two.
- Try the Steam Client Beta if the stable build does not yet contain the fix.
- Reset the affected game’s controller configuration if Steam sees only one controller.
- Avoid deleting Windows controller drivers unless the problem also exists outside Steam.
- Steam Deck Game Won’t Launch: How to Fix Games That Won’t Start
- Steam Big Picture Keyboard Not Showing: How to Fix It
- Steamwebhelper High CPU Usage: How to Fix Steam CPU Spikes
- How to Clear Steam Download Cache and What It Deletes
- Steam Workshop Items Not Updating: How to Fix Mods
- Is Steam Down? How to Check Steam Server Status
Valve’s fix for Steam controller double input
Valve’s official Steam Client Beta announcements list a September 21, 2026 Steam Input fix for doubled Xbox-style controllers on Windows. If your controller started acting like two devices this month, updating the client should be the first thing you test before moving into deeper driver troubleshooting.

Thank you very much! Beta has solve the issue. The **** coincidence that I have just started to configure and try Moonlight and Shunsine in LG and I tried multiple things related with Steam and Driver options. I have been close to look for an alternative and buy some external device for steam linkm
So glad to hear the beta fixed it! Sounds like you went through quite the troubleshooting rabbit hole before finding the solution! Thanks for coming back to let us know it worked,appreciate it 🙂
Thank you! Sadly none of the ways explained fixed the problems. I use a GameSir G7 Pro 8k pc controller with the 2.4 GHz dongle, and Steam always recognizes it as two controllers. I do not have any ingame problems, because all of my games have native controller support, but in the Steam UI, this problem sucks. I can’t toggle switches or use the “Power off” options in Steam Big Picture mode, because it always makes a double click and goes to sleep mode. Windows also shows only one controller. I installed all Windows updates, driver updates and Steam updates, and it doesn’t work. The only option that works is connecting the controller with a cable, but I hate having a controller connected with a cable. Do you have any other things I should try, or do I just have to live with this problem?
Thanks for coming back with all those details! The fact that your GameSir G7 Pro 8K works normally in games and over USB, but gives you double inputs in Steam when using the 2.4 GHz dongle, is particularly interesting.
I’ve found reports from other GameSir G7 Pro users experiencing the same issue, and there’s one additional fix worth trying.
Open Steam, go to **Settings → Controller → Show Advanced Settings** and look for **Xbox Extended Feature Support Driver**.
If it says Install, install the driver and restart your PC. Then reconnect your controller using the wireless dongle and check Steam Big Picture again.
A few people with this exact controller have reported that installing the driver stopped Steam detecting duplicate inputs.
If you’ve already got that driver installed, let us know. Also, does Steam actually list two controllers in its Controller settings, or does it show one controller that produces two inputs?
I’d be interested to hear whether this works, especially as you shouldn’t have to give up wireless just to use Steam properly!
Hi, thank you very much for this tip. Steam actually showed two controllers in the settings and registered one input per showed controller (though it was only one controller, of course). I istalled the driver when I got the controller (in June/July), so I thought that this can’t be the solution. But I tried uninstall the driver, restart the PC and reinstall it, but when I restarted the PC and reconnected the controller, Steam only recognized one controller. I tried reconnecting it again, but Steam still only shows one controller. I tried the controller in the Steam UI, and everything worked perfectly fine. I think that the driver was the problem. Thank you so much for your help!