---
title: "RetroArch doesn't detect my controller — no input in games"
canonical_url: https://emudesk.com/issues/retroarch-controller-not-detected-fix
content_locale: en
source_locale: en
entity_type: issue
index_status: index
published_at: 2026-08-31T18:22:23.000Z
updated_at: 2026-09-01T00:45:02.615Z
freshness_status: fresh
---

# RetroArch doesn't detect my controller — no input in games

If RetroArch won't detect your controller, it's almost always the input layer — not a broken pad: the wrong input driver, a missing autoconfig profile, another app such as Steam Input claiming the controller, or a pad that's bound in the menu but never assigned to a player port. Fix those in order and the gamepad comes back — the steps below cover each cause.

You plug a controller into RetroArch and nothing happens: the gamepad isn't listed, you can't navigate the menu with it, or — the confusing one — the menu responds but the actual game gets no input. Sometimes it works after a reboot and then stops; sometimes only player 1 is recognised and a second pad is dead.

Cause: RetroArch doesn't read your controller directly. It relies on an input driver (the layer that talks to Windows/Linux) plus a controller autoconfig profile (a small file that maps your specific pad's buttons to RetroArch's virtual layout). When a pad isn't detected it's almost always one of: the wrong input driver for your OS, a missing or mismatched autoconfig profile, the pad being claimed by Steam Input or another remapper, or the controller being bound in the menu but not assigned to a player port for the core.

None of this is a broken install — the same RetroArch that fails to see your pad will work perfectly once the driver and profile line up. The fixes below go in order of how often they're the culprit.