Xbox Controller Not Working on PC? 10 Fixes

The Xbox controller is supposed to be the one that just works on Windows. It speaks XInput natively, Microsoft writes the driver, and every game supports it, which makes it especially irritating when it does not work, because there is no obvious layer to blame.

Most failures come down to one of four things: the cable, the firmware, a driver that has gone stale, or a conflict with software you forgot you installed. Here are ten fixes in the order worth working through.

Fix 1: Rule out the cable

The single most common cause, and the easiest to dismiss.

Many USB cables carry power but no data. Connect one to an Xbox controller and it charges the battery while Windows never registers a device. Micro USB cables from old phone chargers are the usual suspect, as are cheap USB-C cables bundled with unrelated accessories.

Test with a cable you know carries data, and use a rear motherboard port rather than a front panel one. Front panel USB headers are internally wired and are a recurring source of intermittent connections.

If the Xbox button lights up but nothing appears in Windows, that combination points almost exclusively at a charge-only cable.

Fix 2: Check batteries before anything else

Obvious, and yet. An Xbox controller with weak batteries will connect, work briefly, then drop. The behaviour looks exactly like a driver problem.

Fresh AA batteries or a fully charged play and charge kit. Rechargeable AAs that have been through many cycles hold voltage poorly under load, which produces controllers that work fine on the menu and disconnect during play.

Fix 3: Confirm your controller actually has Bluetooth

Not all Xbox controllers do, and this catches a lot of people buying used.

The original Xbox One controller, model 1537, has no Bluetooth at all. It connects by cable or via the Xbox Wireless Adapter for Windows and nothing else. Bluetooth arrived with the Xbox One S controller, model 1708, and every Series X and S controller has it.

Tell them apart by looking at the plastic around the Xbox button. On Bluetooth models the plastic is part of the same piece as the face of the controller. On the older model the Xbox button sits in a separate glossy section that is part of the bumper moulding.

If your controller has no Bluetooth, no amount of pairing troubleshooting will help. You need a cable or the wireless adapter.

Fix 4: Pair over Bluetooth correctly

Turn the controller on with the Xbox button. Then press and hold the small pairing button on the top edge next to the USB port for about three seconds until the Xbox button flashes rapidly.

On Windows: Settings, Bluetooth and devices, Add device, Bluetooth. Select Xbox Wireless Controller.

Two things that regularly go wrong here. Xbox controllers hold one Bluetooth pairing at a time, so if it is paired to your console or your phone, it will keep trying to reconnect there instead of accepting a new host. And a stale entry in your Windows Bluetooth list will block a fresh pairing, so remove any existing Xbox Wireless Controller entry before trying again.

Bluetooth mode also supports only one controller at a time on Windows. If you need multiple pads wirelessly, you need the Xbox Wireless Adapter, which supports up to eight.

Fix 5: Update the controller firmware

This fixes more problems than people expect, particularly Bluetooth connection drops and controllers that pair but report no input.

Install the Xbox Accessories app from the Microsoft Store, connect the controller by USB cable, and it will prompt if an update is available. It is worth doing even on a controller straight out of the box, since stock has been sitting in warehouses for a while.

The app also lets you remap buttons, adjust stick and trigger sensitivity, and manage Elite controller profiles. Our Xbox controller firmware guide walks through the process, including the cases where the update fails partway.

One caveat: firmware updates over Bluetooth are unreliable. Always use a cable.

Fix 6: Reinstall the driver in Device Manager

Windows ships the Xbox controller driver and usually manages it fine, until it does not.

Open Device Manager. Look for the controller in one of three places: under Xbox Peripherals, under Human Interface Devices as HID-compliant game controller, or under Microsoft Xbox One Controller. With a wireless adapter it will also appear under a separate Xbox Wireless Adapter entry.

Right click the device, choose Uninstall device, then unplug the controller and reboot. Windows reinstalls the driver on reconnection.

If you see the controller listed with a yellow warning triangle, or as Unknown USB Device with a descriptor request failed error, that is a corrupted enumeration. The uninstall and reboot sequence above usually clears it. If it persists across different USB ports, the controller's USB port or cable connection is likely physically damaged.

Also check the Xbox Wireless Adapter itself if you use one. Its driver can go stale independently of the controller's.

Fix 7: Turn off USB power management

Windows will suspend USB devices to save power, and controllers are frequent victims. The symptom is a controller that works, then stops after a few minutes of menu navigation or a cutscene.

In Device Manager, expand Universal Serial Bus controllers. For each USB Root Hub entry, open Properties, go to Power Management, and untick the option that allows the computer to turn off the device to save power. Do the same for the Bluetooth adapter under Bluetooth.

On laptops, also check your power plan. Balanced and power saver plans enable USB selective suspend by default. Change it under Power Options, Change plan settings, Change advanced power settings, USB settings, USB selective suspend setting.

Fix 8: xinput not working, and what that actually means

XInput is the Microsoft API that Xbox controllers use and that most modern PC games call. When people say XInput is not working, they usually mean one of three different things.

The game uses DirectInput instead. Older titles, especially anything from before roughly 2010, predate XInput and only speak DirectInput. Some of these see an Xbox controller with scrambled bindings, since triggers on an Xbox pad share a single axis under DirectInput. A remapping tool like x360ce translates in the other direction for these games.

A missing DirectX runtime. Games that depend on xinput1_3.dll need the legacy DirectX End-User Runtime, which is a separate download from the DirectX version Windows ships with. Installing it resolves the missing DLL errors that look like controller faults.

A translation layer is intercepting. Steam Input, DS4Windows, reWASD and similar tools all create virtual controllers. If one is running when you did not expect it, the game may be reading the virtual device instead of your real one.

To find out which case you are in, confirm Windows itself is receiving input first. Press Windows + R, type joy.cpl, and check the controller appears with status OK. Then run it through an Xbox controller tester to see every input reporting live. If Windows sees everything and the game sees nothing, the problem is the game's input layer, not your hardware.

Triggers are worth a specific check, since they are the input most often mangled by translation layers. A trigger test shows whether they report as independent analog axes or as a shared axis, which tells you immediately which API the chain is using.

Fix 9: sort out Steam Input conflicts

Steam's controller layer is on by default and it does a lot of quiet remapping.

In Steam, Settings, Controller. Xbox Extended Feature Support is worth having installed since it enables rumble and battery reporting. Xbox Configuration Support is the one that causes conflicts.

The classic symptom is double input: menus that skip two entries per press, or duplicate movement. That happens when the game sees both your physical controller and a virtual one Steam created. Turning off Steam Input for that specific title, via the game's Properties, Controller, Disable Steam Input, usually resolves it.

If you also run DS4Windows or reWASD with an Xbox pad attached, disable one of them. Two virtual controller layers stacked on top of each other never end well.

Fix 10: eliminate interference and check the adapter

If the controller works wired and misbehaves wirelessly, the problem is in the radio path.

Both Bluetooth and the Xbox Wireless protocol operate at 2.4GHz, which they share with Wi-Fi, wireless keyboards and, importantly, USB 3.0 devices. USB 3.0 ports and cables emit broadband noise in exactly that band. An Xbox Wireless Adapter plugged in next to an external SSD is a known bad configuration.

Move the adapter to a USB 2.0 port, or use a short extension cable to get it clear of the case and away from other devices. Line of sight to the controller matters more than distance.

Also worth testing on a second PC if you have one. That single test separates a faulty controller from a problematic host, and it takes two minutes.

When the hardware is genuinely faulty

If the controller fails on multiple machines, with multiple cables, after a firmware update and a driver reinstall, it is the controller.

Common physical failures are a worn micro USB or USB-C port, bumper microswitches that stop registering, and stick modules that develop drift. Our Xbox One gamepad repair guide covers the fixable ones.

On warranty: Microsoft's manufacturer warranty is twelve months in the US, Canada and Australia. In the UK and Germany, EU-derived consumer law generally gives you two years against the retailer rather than the manufacturer. Australian Consumer Law does not set a fixed period and instead applies a reasonable expectation test, which has covered controller faults beyond twelve months.

If the problem is specifically that the pad connects to Windows but not to your console, or vice versa, that is a different diagnostic path and our guide on Xbox controllers not syncing with PC goes through it.