Controller Works in Steam but Not in Game? (2026 Definitive Troubleshooting)

Short answer: When your controller works in Steam menus but not inside the game, the issue is almost always an input hook collision. Steam Input wraps your controller in a virtual translation layer; when a game attempts to poll the hardware directly or runs through secondary launchers (EA App, Ubisoft Connect, Xbox Game Pass), the game either gets blocked by the wrapper or gets confused by seeing both the physical pad and the virtual Steam pad simultaneously. The fastest 60-second fix: right-click the game in your Steam Library > Properties > Controller > toggle Disable Steam Input (or switch to Enable Steam Input). Work through our complete architectural triage below.

Executive Summary and Steam Input Architecture Conflicts

To diagnose why a gamepad responds inside Steam but freezes in-game, you must understand how Steam Input intercepts controller signals. When you connect a controller to Windows, Steam’s input service opens an exclusive or shared HID handle.

Steam Input operates under two distinct states:

• Steam Big Picture & Desktop Mode: Steam translates your physical controller into virtual mouse/keyboard actions or DirectInput commands to navigate menus. This works regardless of the game’s engine state.
• In-Game Hook Mode: When you launch a title, Steam injects its overlay and hooks the game’s input APIs (XInputGetState or SDL2). If the game detects an existing native XInput controller, Steam’s virtual wrapper can cause a collision where the game assigns Player 1 to the wrong device or ignores inputs entirely.

The 60-Second Quick Triage — Steam Input Per-Game Toggling

Before modifying system files or reinstalling drivers, test the per-game Steam Input override switch:

1. Completely close the game and return to your Steam Desktop client.
2. In your Steam Library, right-click the offending game and select Properties…
3. Select the Controller tab on the left sidebar.
4. Look at the dropdown menu under Override for [Game Name]:
   • If currently set to “Use default settings” or “Enable Steam Input”, switch it to Disable Steam Input.
   • Launch the game. Many modern titles (such as EA SPORTS FC, Cyberpunk 2077, and Forza) possess native controller support and malfunction when Steam forces an artificial wrapper.
5. If the game still does not respond, switch the dropdown to Enable Steam Input. Older games or titles without native DualSense support require Steam Input to translate buttons into standard Xbox commands.

Cause 1 — Double Device Registration and Wrong Player Index Assignment

One of the most frequent reasons a controller works in menus but fails in gameplay is the Player 2 ghost bug.

Symptoms include:

• Your controller navigates the title screen (“Press Start to Play”), but once you enter gameplay, your character will not move.
• A second character appears on screen as an unwanted split-screen co-op guest.
• Menu selections skip two spaces with every single tap of the D-pad.

To eliminate this conflict permanently, read our dedicated tutorial on the controller detected as player 2 fix, or install HidHide to hide the physical hardware from the game.

Cause 2 — Overlay Hook Incompatibilities Across EA, Ubisoft, and Epic Launchers

If you launch games that require secondary background clients (such as EA App, Ubisoft Connect, Rockstar Games Launcher, or Epic Games Store), Steam Input’s DLL injection hooks frequently break.

When you click “Play” in Steam:

1. Steam launches the secondary launcher (e.g. EADesktop.exe).
2. Steam attaches its input hook to the launcher window.
3. The launcher spawns the actual game binary (e.g. FC25.exe).
4. Because the game was launched by a child process rather than Steam directly, the Steam Input hook is severed. Steam thinks you are still in a desktop launcher, while the game receives zero controller input.

To fix launcher hook conflicts:

• Disable third-party in-game overlays: In EA App Settings > Application > turn off “In-Game Overlay”. In Ubisoft Connect > Settings > turn off “Enable in-game overlay for supported games”.
• Add the third-party launcher directly to Steam as a “Non-Steam Game”, launch the launcher through Steam Big Picture, and then start your game.

Cause 3 — Sandboxed Windows UWP and Xbox Game Pass Execution Barriers

If you added an Xbox Game Pass for PC or Microsoft Store title to Steam as a non-Steam shortcut, Steam Input will fail almost 100% of the time.

Consequently, Steam cannot inject its virtual controller into Game Pass games. To play Game Pass titles with a non-Xbox controller, do not rely on Steam. Instead, use XOutput or DS4Windows, whose virtual Xbox 360 controller exists at the global kernel driver level outside any UWP sandbox.

Cause 4 — Stale Virtual Controller Ghost Slots in joy.cpl

Over time, installing and uninstalling multiple gamepad utilities (x360ce, DS4Windows, reWASD, XOutput) can leave abandoned virtual devices registered in the Windows registry.

To check for ghost devices:

1. Press Win + R, type joy.cpl, and press Enter.
2. Inspect the “Installed game controllers” list.
3. If you only have one physical controller plugged in, but joy.cpl displays two, three, or four controllers (e.g. multiple “Controller (XBOX 360 For Windows)”), your real controller may be assigned to XInput Slot 3 or 4. Modern PC games only listen to Slot 1!
4. Unplug your physical controller. Any controller that remains listed in joy.cpl is a ghost device.
5. Open Windows Device Manager > expand Xbox 360 Peripherals > right-click orphaned virtual devices > select Uninstall device.

Cause 5 — Anti-Cheat Blocking User-Space Input Hooks

Modern competitive multiplayer titles equipped with aggressive kernel-level anti-cheat (such as VALORANT Vanguard, Apex Legends Easy Anti-Cheat, or Call of Duty Ricochet) actively block third-party DLL hooks in user space.

When anti-cheat detects Steam’s overlay hook attempting to modify input buffers, it may silently drop the hook to prevent automated recoil macros. In these titles, running controllers through Steam Input often results in total dead silence in-game, even though the gamepad navigates the Steam overlay normally. For competitive multiplayer titles, connecting a native XInput controller directly to Windows is the safest and most reliable configuration.

Using HidHide and XOutput to Establish a Clean Virtual Device Layer

When Steam Input continues to fight with your games, the cleanest resolution is establishing an immutable, system-wide virtual controller using XOutput and HidHide.

Follow our comprehensive step-by-step instructions in the XOutput setup guide and ViGEmBus installation walkthrough to configure your universal virtual controller in under five minutes.

Hardware Solutions — When Upgrading to Native XInput Makes Sense

If you are tired of spending hours troubleshooting game launcher overlays, DLL hook crashes, and double-input bugs across mismatched software, upgrading to a modern native XInput controller is the permanent hardware solution.

Native XInput gamepads communicate directly with Microsoft’s built-in Windows USB driver stack (xusb22.sys), completely eliminating the need for Steam Input wrappers or background emulation software:

Frequently Asked Questions

Why does my controller work in Big Picture Mode but nothing happens in game?

Big Picture Mode reads your controller via DirectInput or standard Windows HID drivers. When a 3D game launches, it specifically requests XInput Slot 1. If Steam Input is disabled or conflicting with another virtual device, the game never receives the XInput signal. Toggle Steam Input to “Enable” or “Disable” under the game’s Controller Properties.

How do I stop Steam from overriding my controller in non-Steam games?

Navigate to Steam > Settings > Controller > scroll down to Non-Game Controller Layouts > click Desktop Layout. Click Edit and choose the “Disabled” template. This stops Steam from translating your controller into mouse and keyboard strokes when non-Steam games are running.

Why does my controller only work when connected via USB cable, not Bluetooth?

Certain PC titles only support native XInput over USB. When connecting PlayStation or Switch controllers via standard Bluetooth, Windows exposes them as DirectInput devices. Without Steam Input or XOutput running to translate DirectInput into virtual XInput, the game cannot read the Bluetooth connection.

Can EA App or Ubisoft Connect block Steam Input?

Yes. Secondary launcher overlays frequently intercept input focus, causing Steam’s input hooks to detach from the game executable. Disabling in-game overlays inside EA App and Ubisoft Connect settings typically restores controller functionality.

What should I do if my game assigns my controller to Player 2?

This is caused by double input. The game sees both your physical controller and a virtual controller. Install HidHide to hide the physical controller, leaving only the virtual controller visible. For complete instructions, consult our Player 2 fix guide.