A wired gamepad that lights up but refuses to work in Windows 11 can be frustrating—but power and data are not the same thing. Before reinstalling drivers, check the cable and USB connection, then use Windows’ built-in Game Controllers panel to see what the PC recognizes.

This guide is for USB-connected gamepads in Windows 11. Allow about 15 minutes for the basic checks, though driver downloads or a restart may take longer.

A game controller is connected to a desktop PC displaying controller calibration and setup options. 1. Check the cable and USB port​

Start with the physical connection:

  1. Unplug the controller and reconnect it firmly.
  2. Plug it directly into another USB port on the PC, bypassing any hub, dock, or adapter for now.
  3. If the cable is detachable, try another compatible cable known to carry data, not just power.
  4. If possible, test the controller on another computer and test a different USB device in the original port.

A controller’s light coming on does not prove that Windows is receiving data. If the gamepad works with a different cable, the original cable or its connection is a likely culprit. If it works on another PC but not yours, focus on the port, Windows detection, and drivers.

Some controllers have selectable modes or require manufacturer-specific setup. Check the instructions for your exact model before assuming every USB connection uses the same protocol.

2. See whether Windows detects the gamepad​

Microsoft’s hardware-testing documentation uses joy.cpl to check whether a game controller appears in Windows. It is a useful first test before investigating an individual game.

  1. Connect the controller.
  2. Press Windows + R.
  3. Type joy.cpl and press Enter.
  4. Look for the controller in the Game Controllers window.
  5. If it appears, select it and choose Properties. On the test screen, press buttons and move the sticks to see whether the indicators respond.

What the result means:

  • Listed and responding: Windows is receiving at least some controller input. If one game still ignores it, investigate that game’s controller settings and compatibility.
  • Listed but not responding: Recheck the connection and any controller mode, then inspect the device in Device Manager.
  • Not listed: Continue to Device Manager. The panel is a helpful diagnostic, but absence from this one view is not conclusive proof that the hardware has failed.

Not every feature is necessarily represented in this test. For example, Microsoft documents that certain XUSB controllers expose their triggers differently through the older DirectInput interface than through XInput. An unusual trigger display alone is not enough to diagnose a broken controller.

3. Inspect the controller in Device Manager​

  1. Right-click Start and select Device Manager.
  2. Look under Human Interface Devices, Sound, video and game controllers, Universal Serial Bus controllers, and, if present, Other devices.
  3. Watch for a controller-related entry or an unknown device with a yellow warning symbol. Names vary by model.
  4. If you are unsure which entry belongs to the gamepad, unplug it and reconnect it while watching which entry disappears or appears.
  5. Right-click the relevant entry, choose Properties, and read Device status on the General tab.

Write down any error code. Microsoft’s Device Manager guidance distinguishes, for example, Code 28, which indicates that drivers are not installed, from Code 43, which means Windows stopped a device after it reported problems. Those clues are more useful than installing random driver packages.

If no entry changes when you connect the controller, repeat the cable and port checks before changing drivers. Also try Action > Scan for hardware changes in Device Manager.

4. Update the game controller driver​

Microsoft recommends Windows Update as the primary way to obtain Windows drivers.

  1. Open Settings > Windows Update and select Check for updates.
  2. Go to Advanced options > Optional updates. If a relevant controller driver is offered, select it and choose Download and install.
  3. Restart if prompted, then test again with joy.cpl.

You can also right-click the identified controller entry in Device Manager, select Update driver, and choose Search automatically for drivers.

If Windows does not find an update, check the controller manufacturer’s official support site for a driver for your exact model and Windows version. Follow its installation instructions. A message saying the best driver is installed does not rule out a compatible manufacturer-provided update. Avoid third-party driver-download sites.

5. Reinstall the device​

If the controller is identified in Device Manager but still will not work, reinstalling its device entry is a reasonable next step:

  1. Save your work and close open apps.
  2. In Device Manager, right-click the entry you have identified as the gamepad and select Uninstall device.
  3. Confirm the uninstall. If offered an option to delete the driver software, leave it unchecked for this initial attempt.
  4. Restart the PC with the controller connected. Windows will attempt to reinstall the device driver.
  5. Open joy.cpl again and test the controls.

Microsoft notes that automatic reinstallation is an attempt, not a guarantee. If the device does not return, try Action > Scan for hardware changes, or install the compatible driver supplied by the manufacturer. Do not uninstall an unrelated USB hub, keyboard, or mouse while guessing which entry is the controller.

6. If Windows sees it but the game does not​

Test another controller-compatible game or application. In the affected game, check its controller settings and supported controller types, and disconnect other gamepads temporarily to reduce ambiguity.

Windows detection does not guarantee that every game supports every controller. Microsoft documents multiple input interfaces, including XInput and DirectInput, and their capabilities differ. A game-specific compatibility or configuration issue is therefore possible even when the controller responds in Windows.

If the controller fails across multiple PCs and known-good cables, contact its manufacturer or consider hardware repair or replacement. If it works elsewhere, keep the Device Manager error code and controller model handy when seeking further help.