How to fix a Bluetooth controller that keeps disconnecting

Bluetooth controllers disconnect for six root reasons: a dying battery, a stale or corrupted pair entry on the host, 2.4 GHz interference from Wi-Fi or USB 3.0, an out-of-date driver on the host's Bluetooth adapter, out-of-date controller firmware, or aggressive power-save settings idling the radio after a short period of inactivity[1]. Three of those causes account for nine out of ten cases. Fix them in order to save time.

Battery weakness is the single most common cause and the easiest to misdiagnose. Modern gamepads light up and pair at 5 to 15 percent charge, then drop the link the moment the radio or the rumble motor pulls a current spike. Users assume Bluetooth has failed, when the battery has sagged below the voltage the radio needs to hold a connection. This guide tests for that first.

The second most common cause is a stale pair entry on the host. Operating systems cache pairing keys, and those keys can grow corrupt after a firmware update, a Bluetooth driver update, or a system migration. A clean re-pair clears it. The third most common cause is RF interference, which is everywhere in 2026 because Wi-Fi, wireless mice, wireless keyboards, USB 3.0 hubs, and microwaves all share the 2.4 GHz band Bluetooth uses.

The remaining three causes (driver, firmware, power-save) cover the long tail. Each takes about three minutes to test once you know where to look. The 30-second test in the box above tells you whether to start at the top of the ladder or whether your problem is unrelated.

Battery first. Always. The cost of being wrong about this step is one set of AAs or 90 minutes on a USB-C cable. The cost of skipping it is two hours of driver and firmware work that does nothing.

Three symptoms that point to a battery cause:

• Dropouts get more frequent as a session runs longer. A fresh battery holds the link for an hour, then drops every fifteen minutes, then every five. This is voltage sag under load.
• Rumble triggers a disconnect. Rumble motors pull a brief current spike. A weak battery sags below the radio's minimum voltage and the link drops mid-rumble.
• Re-pairing succeeds but the link only holds for a few minutes. The pair handshake works on stored capacity, then the radio's continuous draw exhausts the remaining charge.

Action by controller:

• Xbox Wireless Controller (AA cells): swap for fresh alkalines or 2000 mAh+ NiMH rechargeables. Do not trust the battery indicator below 40 percent on Bluetooth. The indicator was tuned for Xbox Wireless protocol, not Bluetooth, and it overstates remaining charge by 10 to 20 percent on BT.
• DualSense and DualSense Edge: plug into USB-C for 90 minutes. The pack is 1560 mAh and charges to 80 percent in roughly 70 minutes. Test after.
• Switch Pro Controller: plug into USB-C for 90 minutes. The pack is 2050 mAh.
• 8BitDo Pro 2, Ultimate, SN30 Pro: 90 minutes on the supplied cable. Some 8BitDo pads ship with replaceable 18650 cells; if the pad is more than two years old and the battery cover unscrews, swap the cell.
• Xbox Elite Series 2: the internal lithium pack degrades after 300 charge cycles, which most owners hit between 18 and 30 months of regular use. If yours is past that window, this is the cause. Microsoft offers an out-of-warranty battery replacement service in the US, UK, and EU.

Test in JoyCheck after the battery is fresh. If dropouts stop for at least 10 minutes of active use, you have your fix.

The second-most common cause is a corrupt pairing record on the host. The remedy is a full unpair followed by a clean pair. Not a "reconnect" from the device list. A deliberate forget-and-pair-again cycle.

On Windows 11

1. Settings, Bluetooth & devices, find the controller in the list.
2. Three dots on the right, Remove device. Confirm.
3. Power the controller off. Wait five seconds.
4. Hold the controller's pair button (Xbox: small black button on the top; DualSense: PS + Create held together for five seconds; Switch Pro: small sync button on the top edge; 8BitDo: Start + the button shown in the manual for your pairing mode).
5. Add device, Bluetooth, wait for the controller to appear in the discovery list, click to pair.

On macOS

1. System Settings, Bluetooth.
2. Hover over the controller, click the small i info icon, Forget Device.
3. Put the controller into pair mode using the same combos above.
4. Wait for the device to appear in the Bluetooth list and click Connect.

On Android and iOS

Same pattern. Forget the device, place the controller into pair mode, re-add. On Android specifically, clear the Bluetooth cache before re-pairing if the controller has been unstable: Settings, Apps, show system apps, Bluetooth, Storage, Clear cache. Restart the device, then pair.

After the new pair, leave JoyCheck open for five minutes with light controller input. If the link holds, the corruption was the cause and you are done.

Windows ships a generic Bluetooth stack that handles HID gamepads, but two host-side settings cause silent disconnects[2]. Both are worth checking before assuming the controller is faulty.

Update the Bluetooth adapter driver

1. Device Manager, expand Bluetooth, find your adapter (often labelled "Intel Wireless Bluetooth", "Realtek Bluetooth Adapter", or similar).
2. Right-click, Properties, Driver tab. If the date is older than 2024, click Update driver, Search automatically.
3. Restart the PC after the update completes. Re-pair the controller.

If the in-box update finds nothing newer, check the laptop or motherboard maker's support page directly. Intel, Realtek, and Qualcomm all ship newer drivers than Windows Update sometimes catches. For Intel adapters specifically, the Intel Driver & Support Assistant tool is reliable.

Disable Bluetooth power-save on the adapter

Windows aggressively idles the Bluetooth radio to save power on laptops. For controllers that report state once every 4 to 8 ms, the radio is never idle for long, but Windows still cycles it down between bursts and that causes drops.

1. Device Manager, Bluetooth, your adapter.
2. Right-click, Properties, Power Management tab.
3. Uncheck Allow the computer to turn off this device to save power.
4. Apply. Repeat the same uncheck for every HID-compliant game controller entry under Human Interface Devices.

Disable USB selective suspend

If your Bluetooth radio is a USB dongle (most desktop builds) Windows can also suspend the USB port itself.

1. Control Panel, Power Options, Change plan settings, Change advanced power settings.
2. USB settings, USB selective suspend, set to Disabled for both On battery and Plugged in.
3. Apply, restart.

If you are on a desktop and the onboard Bluetooth chip has been flaky since you built the PC, a $15 USB Bluetooth 5.0 dongle (TP-Link UB500 is widely reliable) is the cheapest fix. Disable the onboard chip in Device Manager first so Windows does not split traffic between two adapters.

Bluetooth shares the 2.4 GHz band with Wi-Fi, microwaves, wireless mice and keyboards, baby monitors, and USB 3.0 ports[3]. When the band is crowded, Bluetooth retries packets and drops the link once retries exceed the radio's threshold. This is the cause behind "my controller only drops in the evenings" or "it drops every time the microwave runs".

The interference checklist:

• Distance. Bluetooth gamepads expect 2 metres or less between controller and host. Past 5 metres on a 2.4 GHz channel, dropouts become frequent. Test from 1 metre away with line of sight.
• USB 3.0 separation. USB 3.0 ports radiate at frequencies that overlap 2.4 GHz Bluetooth. Move USB 3.0 hubs, drives, and dongles at least 30 cm from the Bluetooth adapter. If your Bluetooth dongle plugs in next to a USB 3.0 device, swap to a USB 2.0 port or use a short USB extension cable to move it away.
• Wi-Fi band. If your router pushes both 2.4 GHz and 5 GHz, force the host device onto 5 GHz for the duration of your session. Most modern routers let you split the SSIDs.
• Other Bluetooth devices. A paired phone in the same room counts. A wireless mouse and keyboard count. Each adds Bluetooth chatter. Power off what you are not using.
• Time-of-day test. Try the controller at 7 AM and again at 7 PM. If dropouts only happen in the evening, you have neighbour Wi-Fi or shared-channel congestion on the 2.4 GHz spectrum. A 5 GHz router or wired host is the only real fix.

The brutal truth about RF: you cannot fix your neighbour's microwave. If your environment is congested and you cannot move the host, a wired controller via USB-C is the only reliable answer. Section 8 covers that path.

Out-of-date controller firmware causes a class of dropouts no host-side fix will solve. Each maker has a different update path.

Xbox Wireless Controller (Series X|S, One, Elite). Connect via USB-C, open the Xbox Accessories app on Xbox console or Windows, accept the firmware update prompt[4]. Microsoft has shipped seven firmware revisions for the Series X|S controller since its 2020 launch. See the Xbox calibration guide for the full Accessories app walk-through.

DualSense. Sony's "Firmware Updater for DualSense wireless controller" runs on Windows and macOS[5]. Download from Sony's official support page, connect the DualSense by USB-C, run the updater. Firmware updates change Bluetooth handshake behaviour in roughly one out of every four releases since the controller launched in 2020.

Switch Pro Controller and Joy-Con. No PC update path exists. Updates ship via the Switch console only. Open System Settings, Controllers and Sensors, Update Controllers, connect the controller by USB-C, accept the update.

8BitDo. The 8BitDo Ultimate Software runs on Windows and macOS. Check the version in the app and flash if older than 2024. 8BitDo ships firmware updates more frequently than any first-party maker.

DualShock 4. Sony provides no first-party PC firmware tool. Updates ship via PS4 silently. If your DS4 drops on PC and has not seen a PS4 in over a year, the firmware is likely behind and there is no clean way to update it without a PS4 console. See the PS4 controller calibration guide for the full picture on DS4 limitations.

After any firmware update, do a clean re-pair (Step 2). Pairing records from older firmware versions often fail to validate after a flash. Re-pair, then test.

Each controller family has its own Bluetooth behaviour that catches users out.

Xbox Wireless Controller

Xbox controllers do not handle multi-host Bluetooth gracefully. If you have paired the same pad with a PC, an Xbox console, and a phone, drop the PC pair and keep one active host at a time. The radio's pairing table corrupts faster the more hosts it remembers. Microsoft confirmed this limitation in support documentation[4]: the Xbox controller is designed for one primary Bluetooth host and Xbox Wireless protocol for the console.

DualSense

Adaptive triggers and haptic feedback push more data over Bluetooth than older controllers. If your DualSense drops only during games that use adaptive triggers heavily (Returnal, Astro's Playroom, Stray), the bandwidth load is the cause. Two paths: disable adaptive triggers in the game's settings, or switch to a USB-C wired connection for those titles. The DualSense radio is specced for the PS5's Bluetooth 5.1 stack; PCs on Bluetooth 4.x adapters cannot match its bandwidth ceiling.

Switch Pro Controller

The NFC chip on the right grip can interfere with the Bluetooth radio if a Switch console is nearby in Sleep mode. Power off any nearby Switch consoles completely. Hold the power button on the Switch dock for five seconds to fully power down rather than leaving it in Standby.

Joy-Con (left, right, paired)

Single Joy-Cons paired separately drop more than paired Joy-Cons used together. This is by design: a single Joy-Con uses a smaller subset of the Bluetooth profile and times out faster on idle. If you only use one Joy-Con on PC for indie games, expect more drops than with a pair. See the stick drift diagnostic guide for the related at-rest test.

8BitDo controllers

8BitDo pads support multiple host modes (XInput, DirectInput, Switch mode, Mac mode) selected via button combos at boot. If you boot into the wrong mode for your host, the pad pairs but the link is unstable because the host expects different HID descriptors. Hold Start + the mode button while powering on. The Pro 2 manual lists the combos; for the Ultimate, the dock shows the active mode on a small LED.

Logitech racing wheels (G29, G920, G923)

These wheels do not use Bluetooth. If a G29 is "disconnecting", it is a USB cable, power adapter, or driver issue, not a wireless one. See the Logitech wheel setup guide for the wired diagnostic flow.

If you have worked through Steps 1 to 6 and the controller still drops on Bluetooth but holds for 10 minutes wired in JoyCheck, the Bluetooth radio inside the controller is failing. At that point, a USB-C cable is the answer, not another driver update.

What you need:

• A data-capable USB-C cable. Charge-only cables are the single most common reason "the cable does not work". Look for cables labelled USB 2.0 data or USB 3.x data. The cable that came in the controller's retail box is always data-capable.
• For Xbox controllers: any USB-C to USB-A data cable. Xbox One controllers (pre-2020) used micro-USB instead; check before buying.
• For DualSense: the cable in the box, or any quality USB-C data cable rated for at least 480 Mbps.
• For Switch Pro: USB-C data cable. The official Nintendo cable works on PC.
• For 8BitDo: the supplied cable, which is USB-C on the controller end.

Test wired in JoyCheck for at least 10 minutes of active input. If the link holds wired but drops wireless, the radio is the cause and only a controller replacement (or a board-level radio repair, which costs more than a new pad) restores Bluetooth.

Honest opinion: for competitive play, wired is the right answer regardless of Bluetooth health. Bluetooth adds 5 to 15 ms of input latency on top of game and display latency, and the spectrum is unpredictable. A USB-C cable removes both variables. See how JoyCheck reads your controller for the polling-rate detail behind those numbers.