Controller not detected on PC: fixes

Updated October 2026 · TapTest guides

A controller that the PC refuses to see is frustrating precisely because it gives you so little to go on. There is no error to read, just a pad that does nothing. The upside is that the causes fall into a short list, and if you work through them in order you will usually have it recognised within a few minutes. This guide goes from the quickest checks to the deeper ones so you spend the least effort for the most likely fix.

Throughout, the controller tester is your reference point. The moment the pad shows any sign of life there, you know the connection is good and the problem, if any remains, lies in your game rather than the hardware. So after each step below, plug or pair the pad and glance at the tester before moving on.

Start with the cable and the port

For a wired controller, the cable is the most common villain by a wide margin. Many USB-C cables that come with phones and accessories are built only to charge, with no data wires inside, so the controller lights up and charges while remaining completely invisible to the PC. Swap in a cable you know carries data, ideally the one that came with the controller or a known good charging-and-sync cable.

Then try a different port. Front-panel ports and unpowered hubs are less reliable than the ports directly on the back of a desktop, which connect straight to the motherboard. If you are on a laptop, try every port you have. This one combination of a good cable in a good port resolves a large share of not-detected cases on its own.

For wireless: pairing and power

If your pad is wireless, confirm it has charge, because a flat or nearly flat battery can stop it connecting without any obvious warning. Then check how it is meant to connect. A controller that uses its own USB dongle should have that dongle plugged directly into the PC, not through a hub, and should be put into its pairing mode if the link has been lost. A Bluetooth controller needs to be removed and re-paired cleanly if it is behaving oddly, since a stale or half-finished pairing is a frequent cause of a pad that shows as connected but does nothing. Remove it from your Bluetooth device list, put the pad back into pairing mode, and add it fresh.

Let Windows reinstall the device

Sometimes Windows has the controller half-installed in a bad state. Open Device Manager, look under the controller or human interface device categories, and find your pad, which may show with a warning icon. Right click it and choose to uninstall the device, then unplug and replug, or re-pair, so Windows installs it cleanly from scratch. This clears a lot of cases where the pad was detected once, then stopped working after an update or a driver hiccup.

Check the Windows game controller panel

Press the Windows key, type joy.cpl and press Enter. This opens the built-in game controller list. If your pad appears here, the PC can see it at the system level and your problem is almost certainly inside a game or a launcher, not the hardware. If it does not appear here even with a known good cable and port, the issue is still at the connection or driver level and the earlier steps are where the fix lies.

Steam Input and launcher conflicts

Steam adds its own controller layer called Steam Input, and while it is helpful it can also get in the way. If the pad is detected by Windows and by the tester but a specific game ignores it, open Steam, go to Settings and then Controller, and check how your pad is being handled. Try toggling Steam Input on or off for the troublesome game in its properties. Other launchers and background utilities, including software for a different brand of controller, can also grab the device and block the one you want, so close anything that might be competing for it and test again.

The right standard for the game

PCs understand two main controller standards, a modern Xbox-style one and an older generic one. Most current games expect the Xbox style, so a pad presenting itself as the older type can be seen by Windows yet ignored by the game. Many third-party controllers have a switch or a button combination to change which mode they present, and setting them to the Xbox-compatible mode solves games that stubbornly refuse an otherwise working pad. If your controller came with its own software, that is often where this mode is chosen.

A quick order of attack

Swap to a data-capable cable and a rear or direct USB port.
For wireless, charge it, then re-pair cleanly or plug its dongle in directly.
Check the tester for any sign of life after each change.
Uninstall the device in Device Manager and let Windows reinstall it.
Confirm it shows in joy.cpl, which separates a hardware problem from a game problem.
Toggle Steam Input and close competing software.
Switch the controller to Xbox-compatible mode if it has one.

Common questions

It charges but the PC never sees it. Why? Almost always a charge-only cable with no data wires. Swap the cable before anything else.

It works in one game but not another. That points to game-level controller support or Steam Input rather than the hardware, since a pad that works in one game is clearly being detected by the PC.

Windows sees it but it does nothing in games. Check Steam Input, close competing controller software, and make sure the pad is in the Xbox-compatible mode that most modern games expect.

Do I need to install drivers? Most mainstream pads work on plug-in. Older or niche controllers are the usual exception and may need the manufacturer's driver or app.