2XKO Controller Not Working | Fix Input Fast

You boot up 2XKO, press a button, and nothing happens. No menu movement. No training mode. It feels random, but it usually comes from one of three causes: the game never detects the controller, the controller is detected but not treated as the active device, or a background app intercepts the input before 2XKO can read it.

This guide walks you through a clean order of tests, starting with fast resets, then removing conflicts, then rebuilding your in-game mapping. It also points to official Riot Help Center pages that list known input conflicts, system notes, and a few current bugs. The goal is simple: get you back to stable inputs with the least trial and error.

What Usually Breaks Controller Input In 2XKO

Before you change settings, make one quick decision: is this a Windows problem or a 2XKO-only problem? If your controller fails in every game, fix Windows first. If it fails only in 2XKO, focus on launch order, input conflicts, and mapping state.

Controller Not Detected At All

If 2XKO shows no controller prompts and nothing responds, the game may not be seeing the device. A loose cable, a flaky USB hub, a low-power port, or a Bluetooth pairing that looks connected but drops data can all lead to a dead pad.

Controller Detected But Not Responding

This one is common in playtests. The controller lights up and appears connected, but 2XKO ignores it. Riot’s own peripheral troubleshooting notes that some optical keyboards and some virtual joystick tools can block other input devices, which can leave controllers non-responsive until the conflict is removed.

Wrong Buttons Or Double Input

If one press triggers two actions, or buttons feel scrambled, you may be running two translation layers. Steam Input, controller remappers, and joystick emulators can all sit between the controller and the game. When two layers are active, you can get double presses, stuck directions, or total silence.

2XKO Controller Not Working On PC And Console

When people say “controller not working,” they can mean a few different failures. Use the table below to name the symptom, then start with the first fix in that row. You’ll move faster and you’ll avoid random setting changes.

Reset The Basics In Five Minutes

Start here if you want the fastest win. These steps clear stale device states and force a clean device scan. Do them in order, and test after each step so you know what fixed it.

1. Fully exit 2XKO — Quit to desktop, then confirm the game process is gone in Task Manager.
2. Fully exit the Riot Client — Close the launcher too, not just the game window, so the next launch re-scans devices.
3. Power cycle the controller — Turn it off, wait ten seconds, then turn it on again so it reconnects cleanly.
4. Swap USB ports — Prefer a rear motherboard port on desktops, and avoid passive hubs while testing.
5. Restart Windows — A reboot clears driver hooks that can survive app restarts and keep input in a bad state.

Windows Checks That Take One Minute

• Test the controller in Windows — Press Windows key, type “joy.cpl,” then confirm buttons and sticks light up in the test view.
• Check Bluetooth power — Low battery can keep a pad paired while dropping inputs under load.
• Try a wired link — USB removes pairing noise and helps you isolate the issue faster.

If the controller does not respond in the Windows test view, stop here and fix the device path first. If it responds in Windows but not in 2XKO, keep going. That usually points to a conflict or a mapping state inside the game.

Fix Conflicts From Steam Input, Remappers, And Virtual Devices

If the controller works in Windows yet fails in 2XKO, the next suspect is a background app that grabs, reshapes, or duplicates input. This is the most common “2xko controller not working” case on PC, since many players install tools for other games and then forget they exist.

Disable Steam Input For The 2XKO Entry

Steam Input can be helpful when a game lacks native mappings, but it can also override a pad that already speaks XInput. Steam’s own instructions for per-game controller settings include disabling Steam Input in a game’s Properties under the Controller section.

1. Open Properties in Steam — Right-click the game or shortcut in your library, then choose Properties.
2. Set the Controller override — In the Controller tab, pick the option that disables Steam Input for that entry.
3. Relaunch cleanly — Exit Steam and the Riot Client, reopen them, then test input again.

Uninstall vJoy And Close Remappers

Riot’s peripheral troubleshooting page lists vJoy Virtual Joystick as a known cause of non-responsive controllers, and uninstalling vJoy is a documented workaround. Close any tool that injects controller events or maps buttons to keys while you test.

• Remove vJoy — Use Windows Apps and Features to uninstall vJoy, then reboot.
• Exit controller tools — Close DS4 tools, JoyToKey, macro suites, and stick configuration apps.
• Turn off overlays — Disable Discord overlay and GPU overlays while troubleshooting.

Unplug Optical Keyboards And Extra Input Gear

Riot also flags some optical keyboards as a source of controller non-response in 2XKO. If you use an optical keyboard or a specialty input device, unplug it and test again with only one controller connected. If that restores input, the next step is driver cleanup for the keyboard, or keeping it unplugged while you play.

Rebuild Your In-Game Mapping So Buttons Register

Once the controller is detected and conflicts are gone, mapping is the next place input can break. A half-saved profile, a swapped device slot, or a mode toggle can make it feel like the controller is dead even though the game can see it.

Reset To Default, Then Test Menus

1. Open Settings — Use the keyboard if the controller cannot move the cursor.
2. Go to Controller Mapping — Find the mapping screen and choose the reset option.
3. Save and restart — Exit the game and client, relaunch, then test menu navigation.

If menu navigation works after the reset, jump into training and test the full set of actions. Movement, light and heavy buttons, assists, and supers should all respond. If only one or two actions fail, you can remap those without changing everything else.

Pick One Input Mode And Stick To It

Some controllers and sticks can present more than one input path. If both paths are active, the game can bind to one while your hands are on the other. If you see options tied to XInput or raw device selection, change only one setting at a time and test right away.

• Change one toggle — Flip one advanced input option, then retest in training.
• Keep one device connected — Unplug extra pads so the game cannot hop to the wrong device slot.
• Save a clean profile — Once it works, save the mapping and avoid further changes mid-session.

Fix Double Input After Conflicts Are Off

If you still get double presses with Steam Input and remappers turned off, Windows may still hold ghost controller entries. Cleaning them up can stop duplicate signals from stale device profiles.

1. Show hidden devices — Open Device Manager, choose View, then turn on Show hidden devices.
2. Remove stale controller entries — Uninstall greyed-out game controller items tied to old pads.
3. Reconnect after reboot — Restart Windows, connect the controller, and test again.

Handle Known Bugs And Launcher Permission Problems

At times the controller is fine, but a current bug creates a false alarm. Riot’s Known Errors page lists a menu control bug tied to unplugging controllers in the post-match lobby. If you unplug pads while sitting on the rematch or main menu screen, the menu can stop responding.

Recover From The Post-Match Lobby Unplug Bug

1. Count the unplugged pads — Note how many controllers were pulled out during the lobby.
2. Plug back the same number — Connect the same count of controllers before trying to leave the screen.
3. Exit to the main menu — Once control returns, leave the lobby and avoid unplugging during that phase.

Another edge case comes from mixed permission states. Riot’s PC troubleshooting guidance includes running the Riot Client as administrator. If the client runs as admin while the game does not, or the other way around, you can get strange behavior that looks like a device failure.

Keep The Client And Game On The Same Permission Level

1. Set Riot Client to run as admin — Right-click the shortcut, open Properties, then enable Run as administrator.
2. Launch 2XKO through the client — Start the game from the client after you change the setting.
3. Test input right away — Check menu movement before you change any other options.

If your input works on the first boot after these steps, keep the setup stable for a few sessions. Rapid changes in connected devices and background apps are what bring the problem back.

Last Checks Before You Swap Hardware

If you have reached this point, you’ve already covered the fixes that solve most cases. These last checks target the rare problems tied to firmware, USB stability, and controller-specific quirks that can still make it feel like “2xko controller not working” is a permanent issue.

• Try a wired session — Bluetooth can stay paired while dropping packets; USB removes that variable.
• Update controller firmware — Xbox and PlayStation pads sometimes need firmware updates for stable PC behavior.
• Update chipset drivers — Chipset updates can improve USB stability, especially on newer boards.
• Test another cable — A data cable that charges but drops data is more common than it sounds.
• Test a second controller — If one controller works and one does not, focus on the failing device path.

Test once more.

If it fails again, repeat the reset steps before tweaks.

Official Riot Help Center pages worth checking include “2XKO Supported Devices & Peripheral Troubleshooting,” “2XKO Known Errors/Solutions,” and “2XKO System Requirements.” Search those titles to read the latest notes.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback