Skip to content
SPYLD.Gaming

Controller Not Detected on PC — Diagnosis and Fixes

Detected in Windows but not in the game, or not detected at all. Two different problems with two different fixes.

DODan OkaforCompetitive & Settings Editor· 4 min read·Published · Reviewed by Marcus Reyes

The short answer

A controller that Windows detects but games do not is almost always an API mismatch, where the game expects XInput and the controller is presenting itself as DirectInput — Steam's controller support layer resolves this by translating between them. A controller that Windows does not detect at all is a driver, cable or pairing problem, and testing with a different cable is the fastest way to separate those.

Verified and last updated August 12, 2026.

Time needed
20 min
Difficulty
Beginner
Read time
4 min

Controller problems on PC split cleanly into two categories, and treating them as one problem is why people spend an hour on the wrong fix.

Ask this first

Open Windows game controller settings and see whether the controller appears and responds. If it does, you have an API problem. If it does not, you have a hardware or driver problem. These require completely different fixes.

Step 1: Which failure is it?

Two categories, two fix paths

Step 2: Detected by Windows, ignored by the game

This is the API mismatch, and it is the most common controller problem on PC.

Modern games expect XInput, the standard built around the Xbox controller. Many third-party and PlayStation controllers present as DirectInput, the older general standard. A game built for XInput simply does not see a DirectInput device — not as a broken controller, but as no controller at all.

Enable Steam's controller support 5 min

Steam Settings → Controller. Enable support for your controller type. Steam then presents it to games as a standard XInput device, which resolves the mismatch entirely.

For non-Steam games, add them to Steam 5 min

Add a Non-Steam Game, then launch it through Steam. The same translation layer applies. This is the simplest fix for the common "works in Steam games only" complaint.

Close conflicting software 5 min

Manufacturer utilities and other mapping tools running simultaneously fight over the device, and the symptom is inputs registering twice or not at all. Run one layer, not three.

Step 3: Not detected by Windows at all

Try a different cable 1 min

The most overlooked cause by a wide margin. Many cables are charge-only and carry no data lines, so the controller charges and never appears. Use a cable you know transfers data.

Try a different USB port, directly on the machine 2 min

Front-panel ports and unpowered hubs are less reliable. Use a rear port on a desktop.

Check Device Manager for an unknown device 5 min

If something appears with a warning marker when you plug the controller in, it is being detected but the driver is failing. Uninstall that entry and reconnect to force a fresh driver install.

For wireless, re-pair from scratch 10 min

Remove the existing pairing entirely in Bluetooth settings before pairing again. A stale pairing entry is a common cause of a controller that connects and does nothing.

Random disconnections

Disable USB selective suspend. Windows power settings, USB settings. Windows powers down ports it thinks are idle, and a controller sitting still during a cutscene qualifies. This fixes a surprising number of random wired disconnections.

For wireless, check the environment. A crowded 2.4 GHz environment causes dropouts. Moving the receiver to a front port or using a short extension cable to get it away from the machine's own interference often helps.

Check the battery. Obvious, and it is still the answer more often than any other single cause.

What works

    What doesn't

      Key takeaways

        Frequently asked questions

        What is the difference between XInput and DirectInput?

        They are two different input standards. XInput is the modern one that essentially every current PC game expects, and it was designed around the Xbox controller layout. DirectInput is the older, more general standard that many third-party and PlayStation controllers present themselves as. A game built for XInput simply does not see a DirectInput device, which is why a controller can work perfectly in Windows settings and be invisible in the game.

        Why does my controller work in Steam games but not others?

        Because Steam includes a translation layer that presents almost any controller to games as a standard XInput device. Outside Steam that layer is absent, so a DirectInput controller is invisible again. Adding a non-Steam game to your Steam library and launching it through Steam gives it the same translation, which is the simplest fix for this specific problem.

        Is a bad cable really that common?

        Yes, and it is the most overlooked cause by a wide margin. Many cables supplied with controllers and phones are charge-only and carry no data lines at all, so the controller charges happily and never appears to the computer. Testing with a cable you know transfers data takes thirty seconds and eliminates the single most common cause.

        Should I install manufacturer drivers?

        Usually not. Windows has built-in support for the common controller types and manufacturer software frequently conflicts with it, particularly older utilities. Try the controller with Windows drivers alone first. Install manufacturer software only if you need a specific feature it provides, such as custom button mapping stored on the device.

        Why does my controller disconnect randomly?

        For wireless, usually interference or low battery, and 2.4 GHz interference from a crowded wireless environment is common. For wired, a failing cable or a USB port entering a power-saving state. Disabling USB selective suspend in Windows power settings resolves a surprising number of random wired disconnections and is worth doing on any gaming machine.

        About the author

        DO
        Dan Okafor

        Competitive & Settings Editor

        Dan played CS:GO semi-professionally in a regional ESEA Main roster between 2017 and 2020, and has hit Radiant in VALORANT in three separate acts. He now spends most of his competitive energy on the unglamorous side of the game: input latency, sensitivity consistency and warm-up routines that actually transfer.

        ESEA Main roster (CS:GO), 2017–2020VALORANT Radiant, 3 acts2,400+ hours of tracked aim-training data
        All articles by Dan

        Found something wrong? Games patch and fixes go stale. If a step here no longer works, tell us at hello@spyld.com and we will retest it. Read how we test and our editorial policy.

        Keep reading