A Bluetooth connection between a DualShock 4 and a Windows PC is simple in principle and fiddly in practice. The pairing itself takes under a minute, but stale pairings, an adapter fighting USB 3.0 interference, or a power-saving setting that puts the radio to sleep will make the same controller flawless on Monday and unusable on Tuesday. This deep pairing guide covers the full lifecycle: entering pairing mode correctly, removing old pairings, re-pairing after the controller has been used on another device, and the environment fixes that stop lag and disconnects. It assumes InputMapper is your mapping layer, as set up in how to use InputMapper, but most of it applies to any Bluetooth use of the controller.
Pairing Mode, Done Exactly
- Charge the controller first. A nearly flat battery can enter pairing mode and then die mid-handshake, leaving a half-registered device behind.
- Make sure the controller is fully off. If it is awake and connected to anything — a console, another PC, a phone — turn that device’s Bluetooth off or unplug the controller’s cable so it lets go.
- Hold Share and PS together and keep holding. The lightbar must reach a rapid double-blink pattern. That double-blink is pairing mode. A single slow pulse means the controller is merely trying to reconnect to its last device — release, wait for it to go dark, and hold the buttons again.
- On the PC, open Settings, Bluetooth & devices, Add device, Bluetooth, and select “Wireless Controller”.
- Wait for the “ready” confirmation, then open InputMapper and confirm the controller is listed.
If Windows asks for a PIN, something has gone off-script — a DualShock 4 pairs without one, and a PIN prompt usually means you selected the wrong device from the list. Cancel and pair again, checking the device name carefully. Our quick version of this flow lives in connecting a PS4 controller to PC; this guide continues where that one stops.
Removing Stale Pairings
Bluetooth remembers. Every previous pairing leaves an entry in Windows, and the controller remembers its last host too. When those memories disagree — after a Windows reinstall, a new adapter, or months of use elsewhere — you get the classic symptoms: the controller appears but will not connect, connects and drops within a minute, or pairs happily to everything except your PC.
- In Windows Bluetooth settings, find every “Wireless Controller” entry and choose Remove device. Duplicates are common and all of them should go.
- Restart Bluetooth or the PC, so the radio starts from a clean list.
- Put the controller into pairing mode again with the Share + PS hold, and pair fresh as above.
- Test in InputMapper for a full minute of button presses before launching a game.
Ninety percent of “Bluetooth is broken” cases end at this step. Do it before you change drivers, buy hardware, or blame InputMapper. Persistent drops after a clean re-pair are a different problem, covered in Bluetooth lag and disconnects.
Re-Pairing After Switching Devices
A DualShock 4 happily pairs with a PlayStation, a phone, or a second PC — but it reconnects automatically to only one remembered host at a time, and switching back is not automatic. Expect this routine whenever the controller has been elsewhere:
- Returning to the PC after console use: the controller will try to wake the console. Pair it to the PC again from scratch — remove the Windows entry if the quick reconnect fails, then Share + PS pairing mode and Add device.
- Keep a micro-USB cable in the loop. Plugging in gives you instant wired play while you sort pairing out, and wired is also how you prove the controller itself is healthy.
- If two PCs are in the same room, turn Bluetooth off on the one you are not using. A discoverable controller in pairing mode will attach to whichever host grabs it first.
Players who switch constantly often dedicate one controller to the PC and leave its pairing untouched. It feels extravagant until the third evening spent re-pairing instead of playing.
USB 3.0 and 2.4 GHz Interference
Bluetooth lives in the 2.4 GHz band, and USB 3.0 ports and cables are a known source of noise in exactly that band. A Bluetooth dongle plugged directly into a USB 3.0 port, surrounded by external drives and their cables, can have a fraction of its expected range — fine on the desk, hopeless from the couch. Fixes, in order of effort:
- Move the dongle away from USB 3.0 hard drives and hubs. Even a short distance helps.
- Use a short USB extension cable to raise the dongle into clear air, away from the PC case and its tangle of cables. This is the single most effective cheap fix.
- Keep line of sight in mind. A dongle behind a metal case under a desk asks the signal to pass through both.
- Reduce crowding: other 2.4 GHz transmitters — wireless mice dongles, older Wi-Fi — all share the band. You cannot empty the band, but spacing transmitters apart reduces collisions.
Adapter quality matters too, and it is why we list two options below rather than one: a general Bluetooth dongle, and a UGREEN adapter as an alternative if your current radio is the weak link. Test interference fixes before replacing hardware, though — an extension cable has rescued more “bad” adapters than any purchase.
Bluetooth Power Management: Stop Windows Putting the Radio to Sleep
Windows can turn off Bluetooth hardware to save power, and on some systems it does so aggressively enough to drop a controller mid-session or after every sleep. To check:
- Open Device Manager and find your Bluetooth adapter under the Bluetooth section.
- Open its properties and look for a Power Management tab.
- If “Allow the computer to turn off this device to save power” is checked, uncheck it and apply.
- Also check any generic Bluetooth radio or USB root hub entries the adapter hangs off, if your disconnects happen right after the PC wakes.
Not every adapter exposes the tab. If yours does not, the equivalent behavior is sometimes controlled by the PC’s power plan — using a high-performance plan while gaming achieves the same end. If drops continue with power management off and pairings clean, work through Bluetooth lag and disconnects and the wider troubleshooting hub.
Wired Is the Fallback Test — Always
Every Bluetooth diagnosis should include one wired session. Connect the controller with a micro-USB data cable — not a charge-only cable, as warned in the connection guide — and play normally for ten minutes. If wired is flawless, the controller, InputMapper, your profile, and ViGEmBus are all proven good, and the problem is confined to the radio path: pairing, interference, adapter, or power management. If wired shows the same fault, stop debugging Bluetooth entirely and look at the software chain instead. This one test, done early, is what separates a ten-minute fix from an evening of guessing.
Better Bluetooth Hardware
If testing shows your adapter is genuinely the weak link, these are the two options we link for this site.
Bluetooth Dongle on Amazon UGREEN Bluetooth Options
Affiliate link — see our Affiliate Disclosure.
Frequently Asked Questions
Why does my controller show a slow pulse instead of double-blinking?
A slow pulse means the controller is trying to reconnect to its last paired device, not offering itself for a new pairing. Let it go dark, then hold Share and PS again until the lightbar double-blinks rapidly, which is true pairing mode.
Why does my DualShock 4 connect and then drop after a minute?
The most common causes are a stale pairing, Bluetooth power management turning the adapter off, or USB 3.0 interference weakening the signal. Remove the pairing and re-pair cleanly first, then check power management and dongle placement.
Do I have to re-pair after using the controller on my console?
Usually yes. The controller reconnects automatically to one remembered host, and after console use that host is the console. Remove any failed Windows entry if needed, then pair again using Share and PS pairing mode.
How do I prove the problem is Bluetooth and not InputMapper?
Play wired with a micro-USB data cable for ten minutes. If wired play is flawless, the controller, InputMapper, and your profile are proven good, and the fault is in the pairing, interference, adapter, or power management.