When a game controller is not detected, begin by deciding where detection stops: physical connection, Windows, the launcher or one game. Test a known data cable, direct USB port and the Windows controller panel before changing drivers. For Bluetooth, confirm charge, range and pairing, then remove and add the device only if the existing entry will not connect.
A lit controller is not proof that data is flowing, and a controller visible in Windows is not proof that one game has selected it. This guide keeps those layers separate, uses reversible tests and protects game saves and profiles. Change one variable, repeat the same test and record the result.
The steps rely on current Microsoft support guidance for Bluetooth, USB and Device Manager. Hardware-maker and game-specific instructions remain authoritative. Stop if a battery is swollen, a connector overheats or a cable is damaged.
Start with a symptom you can reproduce
Write down whether the controller is absent everywhere, visible in Windows but ignored by one game, detected only by cable, or disconnected after sleep. Test one known game and the Windows controller panel without changing drivers first. A precise symptom prevents random fixes from creating several new variables. For related reporting on safe and checklist, read Gaming Overlays and Recording Tools: A Safe Stutter and Crash Checklist.
Note the controller model, connection type, Windows version, game launcher and the last time it worked. If the failure began after an update, dock change or new USB device, record that fact without assuming causation. The goal is a baseline that can be retested after each reversible step.
Check power, cable and the physical port
Charge the controller or install known-good batteries. For a wired test, use a data-capable cable; some USB cables deliver power but do not carry data. Connect directly to the computer rather than through a hub, monitor or dock. Microsoft’s USB guidance recommends checking the connection and trying an appropriate port. For related reporting on safe and checklist, read PC Game Audio Crackling or Cutting Out: A Safe Driver, Output and Latency Checklist.
Inspect the connector for looseness or damage without forcing it. Try one other port, then return to the original configuration if there is no change. Do not buy accessories until a simple direct connection has been tested. A controller lighting up proves power, not successful data communication.
Separate USB from Bluetooth diagnosis
A controller that works by cable but not wirelessly has already passed several hardware and game checks. Focus on Bluetooth pairing, range, interference and the computer’s radio. Conversely, a Bluetooth connection does not prove the USB cable carries data. Treat the two paths as separate tests. For related reporting on safe and checklist, read PC Game Black Screen After Alt-Tab: A Safe Display, HDR and Driver Checklist.
Microsoft advises turning Bluetooth off and on, confirming the device is charged and in range, and checking interference from nearby USB 3.0 equipment. Perform those steps in a controlled order. Keep the wired path available so you can distinguish a wireless problem from a game-specific input problem.
Remove and pair again only after preserving the baseline
If the controller appears in the Bluetooth list but will not connect, Microsoft recommends removing the device and adding it again. Before doing so, photograph the current device name and status. Remove only the intended controller; do not clear every paired device as a first response.
Put the controller into its documented pairing mode and keep it close to the computer. Wait for Windows to finish adding it before launching a game. If several devices share similar names, turn off the others temporarily. Repeated pairing attempts without removing a stale entry can make the result harder to interpret.
Use Device Manager as evidence, not as a deletion tool
Open Device Manager and inspect Human Interface Devices, Bluetooth and sound or game-controller categories. A warning icon or error code provides a more specific route than guessing. Microsoft documents Device Manager codes and advises following the resolution associated with the code.
Do not uninstall multiple USB controllers, chipset devices or Bluetooth adapters at once. If a single controller entry clearly shows an error, record its properties before changing it. Scan for hardware changes after a targeted action. A missing entry points toward connection or enumeration; a healthy entry shifts attention to game configuration.
Update through Windows and the hardware maker
Install pending Windows updates and use the controller manufacturer’s official application or support page for firmware. Avoid third-party driver bundles. Generic controllers may use drivers already included with Windows, while branded devices may require a supported accessory app for firmware and profiles.
Create a restore point when appropriate and change one layer at a time. Reboot after a driver or firmware change if the official instructions require it. Then repeat the same baseline test. An update that installs successfully is not proof of repair until Windows and the game recognise the controller consistently.
Test Windows input before blaming the game
Open the Windows game-controller test panel or the supported accessory application and confirm that buttons and axes respond. If Windows receives input correctly, the cable, radio and basic driver path are probably functioning. Continue with launcher, game and input-mode checks instead of reinstalling the entire device stack.
If Windows lists the controller but no inputs respond, test without remapping software and disconnect duplicate controllers. Record whether the problem affects every control or only one axis. Hardware calibration, profile corruption and physical wear are different faults, so a detailed input test prevents an incorrect software conclusion.
Eliminate duplicate and virtual controllers
Flight sticks, wheels, phones, remote-play tools and virtual gamepads can change the order in which a game assigns controllers. Disconnect nonessential input devices, close remapping tools and restart the game. Do not uninstall specialised software permanently until a conflict is actually demonstrated.
If the controller begins working, reconnect devices one by one to identify the conflict. Some games select the first enumerated device and offer no obvious prompt. Preserve profiles before resetting tools such as remappers. The safe objective is to identify one interfering layer, not to erase every configuration.
Check the game’s input mode and launcher layer
Some games support only specific APIs or switch between keyboard, Xbox-style and PlayStation-style prompts. Inspect the game’s official controller-support page and in-game settings. A controller can function in Windows while the title expects a different mode or has controller input disabled.
Launch the game from its normal client and test with overlays or input-translation features unchanged first. Then toggle one relevant feature, such as a supported launcher input layer, and retest. Avoid enabling several compatibility modes simultaneously because duplicate translation can produce double input or no input.
Verify files only when the problem is game-specific
If the controller works in Windows and other games but fails in one title, use that launcher’s official file-verification function. This can replace damaged game files without deleting saves, although local modifications may be affected. Back up configuration files before resetting them.
Do not verify every installed game or reinstall a large title as the first step. Compare the affected game’s input configuration with a working title. Check official patch notes and known issues. A game-specific regression requires evidence from that title’s support channel, not a generic controller replacement.
Inspect per-game configuration without deleting saves
Locate the game’s settings file only through official documentation or a reliable support article. Copy it before renaming or resetting it. Never delete the entire save directory to fix an input setting. Cloud synchronization can propagate an unwanted deletion to another computer.
After a clean configuration test, restore custom settings gradually. If the controller works only with a fresh profile, compare input bindings and device identifiers. Keep the backup until progress and preferences are confirmed. Input troubleshooting should not put saved games at risk.
Consider USB power management after simpler checks
Windows may power down some USB devices to conserve energy. If the controller disappears after sleep or during long idle periods, review power management for the relevant hub or adapter using official guidance. Record the original setting so it can be restored.
Do not disable power saving across every USB device without evidence. Test the exact scenario that caused disconnection, including sleep and wake. A controller that fails immediately at boot is unlikely to be explained solely by idle power management. Match the intervention to the observed timing.
Know when the evidence points to hardware
Test the controller on another supported computer or console and test a known-good controller on the original PC. This cross-test separates controller hardware, cable, port and computer configuration. Use supported devices and avoid interpreting one incompatible platform as a failure.
If the same controller fails across supported systems with multiple known-good cables, contact the manufacturer with the recorded symptoms and serial details. Stop using a swollen battery, damaged cable or overheating device. Software troubleshooting should not continue when there is a physical safety concern.
Finish with a stable retest and a short record
Reboot once, connect the controller using the chosen method, open the Windows input test and play the same game section used at the start. Confirm reconnection after sleep if that was part of the problem. A repair is credible only when the symptom no longer reproduces.
Write down the successful step, driver or firmware version and any setting changed. Remove temporary tools and reconnect other devices gradually. If the problem returns, the record avoids repeating risky actions and gives support staff a clear sequence rather than a vague description.
Build a clean support packet before escalating
If the controller still fails, prepare a compact support packet rather than repeating resets. Include the controller model, connection method, Windows edition and build, firmware version, Device Manager status, the games tested and the exact point where detection stops. Add the results of the cross-test with another cable, port or supported system. Redact account names, serial numbers and personal paths from screenshots before posting them publicly.
Contact the controller maker when the device fails across supported systems, the computer maker when several known-good USB devices fail on the same ports, or the game publisher when Windows input works but one title alone ignores it. Use official support channels and keep case numbers. A structured report shortens diagnosis and prevents an input fault from turning into unnecessary driver removal, game deletion or hardware purchases.
