If you have just bought an Xbox controller for PC and Windows refuses to see it, the cause is almost always one of three things. None of them needs a 30-minute forum dive. This guide walks the five-minute fix path that resolves the bulk of "not detected" reports we see in our own diagnostic logs, then tells you when the controller is genuinely dead.
Key takeaways
- Most "not detected" cases are a cable or pairing problem, not a broken controller.
- A 30-second browser test isolates hardware from software before you change anything.
- Power-only USB cables are the single most common cause on PC.
- Xbox One controllers made before August 2017 need a one-time USB firmware update.
- Steam Input often intercepts the controller before your game ever sees it.
Why is my Xbox controller not detected on PC?
Your Xbox controller is not detected on PC because the USB cable carries power but not data, the Bluetooth pairing has gone stale, or the controller's firmware predates Microsoft's August 2017 Bluetooth update[2]. Less common causes include exclusive-mode capture by Steam, a corrupt XInput driver, or a battery so low the controller can power its light but not enumerate.
The fastest way to isolate which one you have is to run a browser test first.
Open the JoyCheck 30-second test, plug the controller in over USB-C, and press the A button. If the live input diagram appears within five seconds, the hardware is healthy and the problem sits between the controller and your game. If JoyCheck never sees it, the connection layer itself is the issue.
This single check saves the hour most readers lose to reinstalling drivers that were never the problem.
"Across years of hardware-diagnostic work on PC peripherals and game controllers, the cable test alone resolves roughly a third of cases. Most people own at least one charging cable that strips the data pins to save copper."
- Taimoor Bamazai, Founder, Elites Algorithm Limited
Swapping to a known-good USB-C cable, ideally the one that shipped with the controller, is the cheapest fix you will ever try.
How do I know if my Xbox controller is broken or just unpaired?
You know your Xbox controller is broken rather than unpaired when JoyCheck fails to see it on any USB port across at least two different PCs. A controller that pairs on USB but not Bluetooth has a Bluetooth chip fault. A controller that fails everywhere, including the official Xbox Wireless Adapter, has either a dead battery or end-of-life internals.
Run the same test on a friend's machine before concluding the controller is dead.
If JoyCheck sees the controller anywhere, the pads, sticks, triggers, and main board are still working. The fault is in one specific connection path, which is repairable or replaceable independently of the rest of the controller.
For stick-specific symptoms such as drift or stuck axes, the stick drift diagnosis guide covers the 30-second test for analog faults. For PS-side comparisons, the DualSense calibration walkthrough and the PS4 controller calibration guide cover the same diagnostic logic on Sony pads.
What does "controller not recognised" actually mean in Windows?
"Controller not recognised" in Windows means the USB or Bluetooth stack received the device's hardware ID but could not load the matching driver, usually XInput or the generic HID profile. The yellow warning triangle in Device Manager is the visible signal. The cause is missing driver, third-party tool corruption, or a power-only USB cable.
Windows does not say "not recognised" when the controller is working over USB but suppressed by Steam Input. That is a different failure mode.
If your controller appears as "Unknown USB device" in Device Manager, the cable is the most likely culprit. If it appears as "Xbox Wireless Controller" but with the yellow triangle, the driver is corrupt and needs a clean reinstall. If it does not appear at all, the USB-C port on the controller or the cable's data pins have failed.
Across hundreds of controller diagnostic sessions in our own field logs, driver corruption from tools such as DS4Windows, ReWASD, and old Steam Input builds accounts for almost every "two phantom controllers appear at once" report we see.
Which fixes should I try first?
Try the fixes in cost order: hard reset and cable swap first, then re-pair Bluetooth, then driver reset, and only then buy a Microsoft Xbox Wireless Adapter. Stop at the first option that brings the controller back into JoyCheck's live input view. Each option treats a different failure mode, so the order matters.
Worth trying first because it costs nothing and resolves roughly a third of "not detected" reports.
Bluetooth pairings get stale. Sometimes Windows remembers a paired controller but can't actually reconnect to it.
When the controller appears in Device Manager but with a yellow warning triangle, the XInput driver is corrupt. The fix is a clean reinstall.
If Bluetooth pairing keeps failing across multiple PCs, the controller's BT firmware is mismatched with your hardware. The official Microsoft Xbox Wireless Adapter uses a proprietary 2.4 GHz proto…
Fix 1: Hard reset and cable swap. Hold the Xbox button for 10 seconds until the controller fully powers off, then plug in a known-good USB-C cable. This resolves roughly a third of "not detected" reports we see. Total cost: zero, total time: 60 seconds.
Fix 2: Re-pair Bluetooth. Open Windows Settings, go to Bluetooth and devices, find the controller in the paired list, and remove it. Hold the controller's small pair button for three to five seconds until the Xbox button flashes rapidly, then run "Add device" in Windows. Stale pairings are the most common Bluetooth-specific failure.
Fix 3: Driver reset. Open Device Manager, find the controller under "Xbox Peripherals" or "Other devices", right-click, and choose "Uninstall device". Unplug the controller, restart Windows, and replug. Windows reinstalls a fresh XInput driver from the system image.
If you have DS4Windows, ReWASD, or vJoy installed, uninstall those before retrying. They can leave the input stack in a stuck state even after they are closed.
Fix 4: Xbox Wireless Adapter. The official Microsoft 2.4 GHz dongle bypasses your PC's Bluetooth stack entirely. It costs roughly £25 to £30 and is the right answer when Bluetooth pairing fails repeatedly across multiple PCs. Pre-August-2017 Xbox One controllers need this adapter because they cannot speak standard Bluetooth at all[2].
How does Xbox controller detection differ across operating systems?
Xbox controller detection differs significantly across operating systems because each one ships its own driver layer for the input stack. Windows ships native XInput, while macOS supports Xbox Series controllers natively from macOS 11.3 onwards[2]. Linux uses xpad over USB and xpadneo over Bluetooth, both in the mainline kernel since Ubuntu 22.04[3].
Older platforms usually need a one-off driver install before pairing works.
Browser support is the most consistent layer, because every modern browser implements the W3C Gamepad API[1].
Windows 10 and 11. Plug-and-play for Xbox Series X|S and Xbox One controllers via USB. Bluetooth works for any controller with August 2017 firmware or newer. The most common gotcha is Steam intercepting the controller. Open Steam, go to Settings, then Controller, and disable all Steam Input layers before relaunching the game.
macOS. Xbox Series X|S and Xbox One controllers pair natively over USB and Bluetooth on macOS 11.3 and later. Xbox 360 pads need USB-only on macOS because they have no Bluetooth chip[2]. Pair through System Settings, then Bluetooth, exactly as you would pair AirPods.
Linux. xpad and xpadneo are in the mainline kernel for Ubuntu 22.04+, Fedora 37+, and Arch. Older kernels need xpadneo-dkms installed through your distribution's package manager. Check dmesg for pairing errors if either driver does not load on first plug-in.
Browser. Chrome, Edge, Firefox, Brave, and Vivaldi expose Xbox controllers through the Gamepad API with full input and haptic support. Safari supports inputs but lacks haptics. iOS Safari from version 14.4 onwards supports Xbox Series controllers paired over Bluetooth.
Which Xbox controllers work on which platforms?
| Controller | Windows USB | Windows BT | macOS USB | macOS BT | Linux | Browser |
|---|---|---|---|---|---|---|
| Xbox Wireless Controller (2020+) | ||||||
| Xbox Elite Series 2 | ||||||
| Xbox One Controller (post-Aug 2017 FW) | ||||||
| Xbox One Controller (pre-Aug 2017 FW) | adapter only | adapter only | USB only | |||
| Xbox 360 Controller | USB only | USB only | USB only | |||
| Xbox Adaptive Controller |
Why does my Xbox controller work on USB but not Bluetooth?
Your Xbox controller works on USB but not Bluetooth when the controller's Bluetooth firmware is older than Microsoft's August 2017 update, when your PC's Bluetooth chip is on a 2.4 GHz band crowded by Wi-Fi traffic, or when the previous pairing entry is stale[2]. USB-C connections bypass all three problems because they use a dedicated wired channel.
The 2.4 GHz interference case is more common than most users expect.
If your microwave, neighbours' Wi-Fi network, or a busy USB 3.0 hub sits within two metres of the PC, the controller's Bluetooth link can drop after roughly 10 seconds. Microsoft's own Xbox Wireless Adapter sidesteps the issue because it uses a proprietary RF protocol on a less crowded band.
For the firmware mismatch case, plug the controller into a Windows PC over USB, open the Xbox Accessories app from the Microsoft Store, and let it apply any pending update. After that one-time update, Bluetooth pairing usually works on the first try.
Why does the browser test see the controller but my game does not?
The browser test sees your controller but your game does not because Steam Input or a similar utility is capturing it in exclusive mode before the game polls XInput[1]. The W3C Gamepad API runs at a different level of the input stack, so the browser receives raw events while the game receives nothing.
Disabling Steam Input for the specific game resolves this in most cases.
Open Steam, right-click the game, choose Properties, then Controller, and disable Steam Input. Restart the game. If the game uses DirectInput rather than XInput, add it to Steam as a non-Steam game and use Steam Input as a wrapper, or use ReWASD to translate XInput into the input scheme the game expects.
JoyCheck deliberately polls the controller through the browser-native API only. There is no driver layer between the controller and the diagnostic, which is exactly why it is a reliable check for hardware faults.
When should I replace the controller instead of fixing it?
Replace the controller instead of fixing it when JoyCheck fails to see it on two different PCs across both USB and Bluetooth, when the Xbox button refuses to light up after a 10-second hold, or when the USB-C port wobbles when a cable is inserted. Those three signs together point to a failed connection chip or broken port.
Microsoft offers a 90-day warranty in most regions, with longer coverage in several EU markets under local consumer protection law[2].
For stick-only faults, replacement of the stick module is straightforward, and the stick drift diagnosis guide covers when that is the right call. For connection faults, the economics rarely work out: a new official Xbox Wireless Controller costs roughly £60[4]. Third-party Hall-effect alternatives such as the GuliKit KingKong 3 or the 8BitDo Ultimate Controller cost roughly £70 with a longer expected lifetime.
If you already replaced sticks on the same controller once before, a Hall-effect replacement is the long-term answer rather than a like-for-like swap.
How do I confirm the fix actually worked?
Confirm the fix worked by running a full controller test in JoyCheck after every attempted fix and aiming for two clean passes in a row before declaring the controller fixed. A single clean read after a driver reset is not enough. Input layers can settle for 30 seconds and then fail again, so the second pass catches the slip.
Open joycheck.io, press A or any button to wake the controller, and watch the live diagram populate.
Cycle through every input: both analog sticks at full deflection, all four shoulder and trigger inputs, every face button, the full D-pad, plus View, Menu, and Share. Each input should light up in the diagram. If one specific input fails to register while the others work, that is a localised hardware fault rather than a connection problem, and replacement of that specific component (or the whole controller) is the next step.
For ongoing controllers you rely on for competitive play, run the full test once a month. Connection faults tend to creep in over weeks rather than fail suddenly. According to community field threads on r/xboxone[5], the most reliable early warning is intermittent button drop during long sessions rather than a clean disconnect.
Frequently Asked Questions
Can I tell whether my Xbox controller is broken or just disconnected?
Yes. Run JoyCheck on at least two different PCs. If neither machine sees the controller over USB and Bluetooth, the controller has a hardware fault. If at least one PC sees it, the fault sits in the connection path of the original PC, not the controller itself.
Why won't my Xbox controller pair with Bluetooth on Windows?
The most common reason is firmware older than August 2017, which predates Microsoft's standard Bluetooth support. Plug the controller in over USB-C once and run the Xbox Accessories app from the Microsoft Store to update. After that, pairing usually works on the first try. Make sure the small pair button is held for three to five seconds, not just tapped briefly.
Will an Xbox controller work on iPhone or iPad?
Yes, on iOS 14.4 and later, Xbox Series X|S and Xbox One controllers pair over Bluetooth like any other accessory. Open Settings, choose Bluetooth, and tap the controller's name when it appears. Xbox 360 controllers do not work on iOS because they have no Bluetooth chip.
My Xbox controller works in some games but not others. Why?
Almost always, Steam Input is intercepting. Steam routes the controller through its own input layer, which some games do not expect. Open Steam, go to Settings, then Controller, then Desktop Configuration, disable Steam Input, and restart the game.
Do I need the Microsoft Xbox Wireless Adapter for my PC?
Only if you have an Xbox 360 controller without Bluetooth, or your PC's Bluetooth is unreliable specifically with Xbox controllers. Modern Xbox controllers pair directly over standard Bluetooth on Windows 10 or 11 and macOS 11.3 or later.
Can I update Xbox controller firmware without a Windows PC?
Not officially. Firmware updates run through the Xbox Accessories app, which is Windows-only. Mac and Linux users need to borrow a Windows PC for a single one-time update over USB-C.
The controller pairs but no buttons register in any app. What now?
That is XInput driver corruption. Run the driver reset path: uninstall the device from Device Manager, restart Windows, and replug. If DS4Windows, ReWASD, or vJoy is installed, uninstall those before retrying. They can leave the XInput stack in a stuck state even after they are closed.
Sources & references
- W3C Gamepad API specification. Defines how browsers expose connected gamepads.
- Microsoft Xbox Wireless Controller support. Official Microsoft documentation on Xbox controller compatibility, the August 2017 Bluetooth firmware update, platform support across Windows, macOS, iOS, and Android, and the manufacturer's standard 90-day warranty terms.
- USB-IF USB-C specification overview. USB Implementers Forum reference for USB-C cable and connector behaviour, including the data-versus-power-only distinction that explains why charging cables often fail as controller cables.
- iFixit Xbox Wireless Controller teardown. Public teardown guides covering repair feasibility and end-of-life signals.
- r/xboxone on Reddit. Community-aggregated field reports across PC builds, used as a directional signal for the relative frequency of cable, firmware, driver, and pairing failure modes seen in the wild.