Controller disconnects mid-test: what to inspect

Your controller appears in a test, then vanishes while you press buttons or move the sticks. A mid-test disconnect can point to a weak cable, low battery, wireless interference, or a browser that stopped seeing the device. The symptom alone does not tell you which one is responsible.

Use the Gamepad Test to see whether button, stick, trigger, and vibration input is still arriving. Then compare what the browser reports with what your computer or phone does when the controller disconnects.

Check the controller during the test

1. Open the Gamepad Test on the device where the controller disconnects. Connect the controller before testing.
2. Press a controller button, then move each stick and trigger. Watch whether the test shows the inputs.
3. If the controller disappears, wait a few seconds and try an input again. Note whether the controller returns without reconnecting.
4. If the test checks vibration, try it only after the basic inputs work. Notice whether the disconnect happens when vibration starts.
5. Reconnect the controller and repeat the same actions. If possible, compare a wired connection with wireless, or try a different USB port.

Keep track of whether the operating system also loses the controller. If a controller still appears connected in your computer's Bluetooth settings but vanishes from the browser test, the issue may be with browser detection rather than the physical connection.

What the result means

The controller disappears from the test and the device

The connection is dropping below the browser. For a wireless controller, check its charge, distance from the computer, and Bluetooth link. For a wired controller, suspect the cable, connector, USB port, or an adapter.

The operating system still sees it, but the test stops showing input

The controller may still be connected while the browser stops receiving updates. Close and reopen the test page, then connect the controller and try again. If the browser consistently misses it but games recognize it, the issue may be browser support or a page-specific limitation.

The controller stays visible, but some controls stop responding

This points to an intermittent control, a worn cable, or a controller problem more than a complete connection loss. Test buttons, sticks, and triggers separately. If only one input fails while the others continue to respond, focus on that control.

It disconnects when vibration starts

Vibration draws extra power. A low battery, weak cable, or unstable USB connection can become noticeable when the motors run. Charge the controller and test it again with vibration off or with a different connection.

It works in the test but disconnects in one game

The controller and browser test can communicate, but the game may have its own connection, mapping, or compatibility issue. Check the game's controller settings and test the controller in another game before assuming the hardware is faulty.

How to fix it

1. Charge the controller. Charge it fully, or replace its batteries, then repeat the test. A low battery can cause wireless dropouts before the controller shuts off completely.
2. Move closer and reduce interference. Test within a few feet of the computer, with a clear path between them. Move USB 3 drives, hubs, and wireless receivers away from the controller's Bluetooth receiver if possible.
3. Reconnect the cable or receiver. For USB, unplug and reconnect both ends, then try a different port. For a wireless receiver, connect it directly to the computer rather than through a hub. Try another data-capable cable if you have one.
4. Pair the controller again. On Windows 11, open Settings › Bluetooth & devices › Devices, remove the controller if it is listed, then pair it again. On macOS, open System Settings › Bluetooth, remove or forget the controller, and reconnect it. On an iPhone, use Settings › Bluetooth. Android menu names vary, but look under Settings › Connected devices for the controller and pairing options.
5. Close other apps using the controller. Quit games, controller-mapping utilities, and other browser tabs that may be reading input. Reopen the test page and try the controller by itself.
6. Restart the device and check for updates. Restarting can clear a stuck Bluetooth or USB connection. If the problem continues, install available system updates and check the controller maker's instructions for firmware updates.

When the controller may be faulty

Test it on another device, using a different cable or connection method if available. If it disconnects there too, even after charging and pairing again, the controller or its connector may be damaged. A cable that disconnects when gently moved is a strong clue, but do not bend it forcefully to reproduce the fault.

If the controller is under warranty, contact the seller or manufacturer before opening it. For an older controller, replacing a damaged cable or battery may be practical if those parts are replaceable. A controller with repeated wireless dropouts across several devices may need repair or replacement.

Why the browser test can behave differently

A browser test checks whether controller input reaches the web page. It does not confirm that every game supports the controller, that every button is mapped the way a game expects, or that the controller is working perfectly under all conditions. Some browsers also need you to press a controller button before they show the device to a page.

Run the test on the same device and connection you want to diagnose. If the controller works in the test but not in one game, troubleshoot that game's settings separately. If it disappears from both the test and the device's connection settings, start with the battery, cable, receiver, and pairing.