Controller Not Detected on PC? 10 Fixes That Work

There is a specific kind of frustrating that is different from a controller that connects but misbehaves. This is the controller that simply does not exist as far as Windows is concerned. No device in Device Manager. Nothing in the Game Controllers panel. No light, no vibration, no acknowledgment that you plugged anything in at all.

This is a detection problem, not a configuration problem, and it has a narrower set of causes than the usual "my controller feels off" complaints. The fixes below are ordered the way a technician would actually work through them: cheapest and most likely first, deeper Windows-level checks in the middle, hardware isolation last. Most people find their answer in the first four.

First, confirm what "not detected" actually means

Two different tools show two different things, and mixing them up wastes time.

Press Windows key + R, type devmgmt.msc, and press Enter. This is Device Manager, and it shows every device Windows has enumerated at the USB or Bluetooth level, whether or not it works properly. Look under Human Interface Devices, Bluetooth, and, if it exists, an Unknown devices or Other devices category with a yellow warning triangle.

Separately, press Windows key + R, type joy.cpl, and press Enter. This is the Game Controllers panel, and it only lists devices that Windows has successfully identified as a game controller. A controller can appear in Device Manager as a generic USB device while never showing up here at all, and that gap is itself diagnostic: it usually means the device enumerated but the driver stack failed to classify it correctly, which points at fixes 4 and 5 below rather than a cable or port problem.

If neither tool shows anything at all, not even an unrecognized device, the problem is happening before Windows sees anything, which points at fixes 1 through 3.

1. Rule out the cable

This causes more "dead" controllers than anything else on this list, because a cable can look completely normal while carrying power but not data.

Many cables bundled with controllers and phone chargers are charge-only, wired for power delivery with the data lines left unconnected. If your controller's light turns on but nothing else happens, that is the exact signature of a charge-only cable. Swap it for one you know carries data, ideally one that came with a mouse, keyboard, or storage device rather than a charger, and check for a response in joy.cpl right after.

2. Try a different USB port, and skip hubs and front panels

Front panel ports on a desktop case are wired back to the motherboard through a header cable that is a common point of poor contact, and they are frequently the least reliable ports on the machine. Try a port on the back of the case directly.

Unpowered USB hubs are the other common culprit, particularly for wireless dongles and controllers with rumble motors, both of which draw more current than a hub's shared power budget expects. If your controller is plugged into a hub, plug it directly into the PC instead. A controller that enumerates fine on a direct port but drops or fails on a hub is a power problem, not a defective controller.

3. Check for a hardware kill switch or dead battery

Wireless controllers frequently have a physical power switch, often on the underside, that gets bumped into the off position in a bag or drawer. Xbox controllers need fresh or charged batteries to power on at all, and a battery that reads as "a little low" on a charge indicator can still be too depleted to complete a Bluetooth handshake even though it briefly lights up. If you have a charging cable, plug the controller in directly by USB and see if it's detected while wired. That single test separates a genuine detection fault from a power problem instantly.

4. Look for a driver failure in Device Manager

If the controller shows up in Device Manager with a yellow warning triangle, right-click it and check Properties, then the device status. Error codes here are specific and useful. Code 10 generally means the device failed to start, often because of a corrupted or incompatible driver. Code 43 means Windows detected a hardware problem, sometimes real and sometimes a false positive triggered by a driver conflict.

Right-click the flagged device and choose Uninstall device, ticking the option to delete the driver software if it's offered. Unplug the controller, restart the PC, then plug it back in. This forces Windows to reinstall the driver from scratch rather than reusing a corrupted one, and it resolves a large share of "shows up as unknown device" cases without needing to find or install anything manually.

5. Update chipset and USB drivers, not just the controller

A controller depends on your motherboard's USB controller drivers as much as its own. If Windows Update has recently installed a new chipset driver, or if you're running old drivers on a system that hasn't been updated in a long time, the USB stack itself can misbehave in ways that look exactly like a bad controller.

Check Device Manager under Universal Serial Bus controllers for any entries with warning icons, and check your motherboard or laptop manufacturer's support page for a current chipset driver package. This step gets skipped constantly because it doesn't feel related to a controller problem, but USB host controller drivers sit underneath everything else on this list.

6. For Bluetooth controllers, re-pair from scratch rather than reconnecting

Bluetooth pairing failures are the single most common form of "not detected" for wireless controllers, and the fix is almost always to remove the old pairing entirely rather than trying to reconnect it.

Go to Settings, then Bluetooth & devices, find the controller in the list even if it shows as disconnected, and remove it completely. Then put the controller into actual pairing mode, which is a different button sequence from simply turning it on: most controllers need a specific button held for several seconds until the light flashes in a distinct pattern, not just powers on solid. Pair it again as a new device.

Two things cause repeated Bluetooth failures worth knowing about. First, a controller can only hold one active Bluetooth pairing at a time on most systems, so if it was last paired to a phone or console, it needs to be put back into pairing mode before your PC can claim it. Second, cheap third-party Bluetooth adapters and some laptop Bluetooth chipsets use their own driver stack instead of the standard Microsoft one, and that non-standard stack is a documented source of pairing failures that a first-party or well-supported adapter doesn't have.

7. Check USB selective suspend and power management

Windows can power down individual USB ports to save energy, and a misconfigured power plan can cause a controller to disconnect intermittently or fail to be redetected after your PC wakes from sleep.

In Device Manager, find your USB Root Hub entries under Universal Serial Bus controllers, open Properties for each, go to the Power Management tab, and uncheck "Allow the computer to turn off this device to save power." Separately, in your active power plan's advanced settings, set USB selective suspend to disabled. This is a especially common cause of a controller that worked fine yesterday and is suddenly invisible today with nothing else having changed.

8. Close software that creates a competing virtual controller

If you have Steam running with controller support enabled, or DS4Windows, reWASD, or a similar translation layer installed, these tools can claim exclusive access to the physical device or intercept it before other software sees it. The result can look exactly like the controller isn't detected, when what's actually happening is that only the translation layer's virtual device is visible, or nothing is visible because two pieces of software are fighting over the same hardware.

Close Steam entirely, close any DS4Windows-style software, and test with just Windows itself using joy.cpl. If the controller appears once that software is closed, you've found the cause, and the fix is picking one layer rather than running several at once. Our guide on XInput versus DirectInput covers why these translation layers exist in the first place and when you actually need one.

9. Update the controller's own firmware

Less common as a cause of total non-detection than the fixes above, but real, particularly after a controller has sat unused for a long time or after a manufacturer pushes a significant update. A firmware checker can tell you what version your controller is currently running and whether it's meaningfully behind, which is useful information even before you go looking for an update path, since the correct update method differs by manufacturer and sometimes requires the controller to be connected to its native console first.

10. Isolate whether it's the controller or the PC

If nothing above has worked, the last step is figuring out which side of the connection is actually at fault. Plug the controller into a different PC, a phone with USB-C or Bluetooth, or its native console if it has one. If it's detected there, the problem is specific to your PC's ports, drivers, or Windows installation, and it's worth trying a different user account or, as a last resort, a different Windows installation entirely to rule out a corrupted system-level driver store.

If it fails everywhere you try it, including its native platform, the controller itself has likely failed, whether that's a dead internal battery that won't hold charge, a failed charging port, or a genuine internal fault. At that point a joystick tester on a machine where the controller does connect can at least confirm whether the rest of the hardware still works, which matters if you're deciding between a repair and a replacement.

When it's a different problem entirely

Worth being clear about what this guide does not cover. If your controller shows up fine in Device Manager and joy.cpl, lights up, and responds to input tests, but a specific game doesn't react to it, that's not a detection problem. Our guide on controllers that are detected but not working in a specific game covers that separate and much more common situation. Likewise, if the controller worked fine until a recent Windows Update and then stopped, our dedicated guide on controllers that broke after a Windows Update walks through the update-specific rollback and driver steps that apply there.