PS5 Controller Won't Connect to PC (Bluetooth + DS4Windows fix)

The DualSense is one of the better controllers you can use on a PC, which makes it doubly annoying when Windows refuses to see it. The good news is that the DualSense is genuinely plug-and-play at the hardware level, so most connection failures come down to one of a handful of predictable causes: a bad cable, a Bluetooth pairing that won't take, Steam and DS4Windows fighting over the same controller, or a driver that needs a nudge. Work through the sections below in order and you'll land on the fix.

One thing before you start troubleshooting: figure out whether the controller is truly not connecting, or connecting but not registering inputs, because those are different problems with different fixes. The fastest way to tell is to open a browser-based gamepad tester once Windows shows the controller, press some buttons, and see if anything lights up. If the tester reacts, your hardware and connection are fine and the problem is game-side. If nothing shows up at all, keep reading.

Start with the USB cable (it's usually the cable)

Plug the DualSense into your PC with a USB-C cable and watch for the Windows connection chime. If you hear it, wired is working and you can move on to Bluetooth or software.

If nothing happens, the cable is the prime suspect. Many USB-C cables, especially the short ones bundled with phones and earbuds, are charge-only and carry no data. The controller will charge but never appear as an input device. Swap to a cable you know transfers data, and plug directly into a rear motherboard USB port rather than a front-panel port or a hub, since those introduce their own failures. This single swap resolves a large share of "won't connect" reports.

Getting Bluetooth to pair

Wired works, but you want wireless? The DualSense pairs over standard Bluetooth, so any PC with Bluetooth 4.0 or newer can handle it. If your desktop has no Bluetooth, you'll need a USB Bluetooth adapter, and a decent one matters, since cheap dongles cause dropouts and input lag.

To put the controller in pairing mode, turn it off, then hold the PS button and the Create button (the small button to the upper-left of the touchpad) together for about five seconds. The light bar will flash rapidly in a double-blink pattern, which means it's discoverable. On the PC, open Settings > Bluetooth & devices > Add device > Bluetooth, and select "Wireless Controller" when it appears.

If pairing fails or the controller never shows up, the usual culprits are: the controller wasn't fully off before you started (a sleeping DualSense won't enter pairing mode cleanly), a stale pairing from a previous session (remove "Wireless Controller" from your Bluetooth device list and pair fresh), or Bluetooth being disabled in Windows entirely. If it pairs but drops constantly, that's almost always a weak dongle or interference from a USB 3.0 port right next to the adapter. Bluetooth also disables the DualSense's onboard headphone jack; that's normal, not a fault.

Wondering whether to bother with wireless at all? Our breakdown of Bluetooth vs wired input lag covers the real-world latency difference, which, for a DualSense, is small but nonzero.

Does Windows see it? Check Device Manager

If neither cable nor Bluetooth produces a working controller, confirm whether Windows detects the hardware at all. Right-click Start > Device Manager, and look under "Human Interface Devices" and "Sound, video and game controllers" while you plug the controller in. If a device appears and disappears as you connect and disconnect, Windows sees the hardware and the issue is software (skip to the DS4Windows section). If nothing changes, it's a hardware or cable problem: try a different cable, a different port, and the controller reset below.

Reset the controller

A DualSense that behaves erratically or refuses to pair can be reset. On the back of the controller near the top, there's a tiny hole beside the Sony logo. Push a straightened paperclip in, hold the recessed button for about five seconds, then reconnect via USB and press the PS button. This clears the controller's pairing memory and internal state, and it fixes a surprising number of "connects to nothing" cases, especially controllers that were recently paired to a PS5 or phone.

The DS4Windows question: do you even need it?

Here's where a lot of confusion lives. DS4Windows is a tool that makes Windows treat your DualSense as an Xbox controller, because a few games only support Xbox-style (XInput) input and won't recognize a PlayStation pad natively. That's the entire job.

But you often don't need it. Windows and Steam both support the DualSense natively now, and most modern games read it fine on their own. So the first thing to try is nothing: plug in the controller and launch your game. If it works, don't install DS4Windows at all; it can only add complications.

You need DS4Windows when a specific game only supports Xbox controllers and ignores your DualSense, when you want to remap buttons at the system level, or when you want features like custom light bar colors tied to battery. If none of that applies, skip it.

When DS4Windows and Steam collide

If you do run DS4Windows, know that Steam has a built-in behavior that trips people up: when Steam detects DS4Windows running, it deliberately ignores real and virtual PlayStation controllers, because it assumes you're emulating an Xbox pad and is trying to prevent double inputs. Most of the time this is invisible, and games work fine. But it means your DualSense can't drive Steam's Big Picture / Gamepad UI while DS4Windows runs, and a few games that route PlayStation support through Steam's own configuration won't work.

The setup that avoids fights:

Decide on one input path, not two. Either let Steam handle the controller natively with DS4Windows closed, or run DS4Windows and turn off Steam Input for that game (in the game's Properties > Controller, set "Override for [game]" to "Disable Steam Input"). Running both untuned is what produces the classic double-input bug, where one button press registers twice.

If you're getting double inputs, the cleanest fix is to hide the raw controller from games so only the emulated one gets through. DS4Windows has a "Hide DS4 Controller" toggle in its Settings tab, though it can reset on reboot. A more reliable option many players use is HidHide, a free tool that hides the physical controller at the system level and persists across restarts; you whitelist Steam so it still sees the emulated pad. Our guide on eliminating input lag on PC touches on keeping your input chain clean, which is the same principle: fewer layers, fewer conflicts.

One important limitation to accept: DS4Windows emulation disables the DualSense's adaptive triggers and haptics, because those are PlayStation-specific features that don't survive being translated into an Xbox controller. If you want the fancy trigger effects, you need native DualSense support and no DS4Windows in the chain.

Wired or wireless for actual play?

Once both connection methods work, which should you use? For most people, wired is the safer default on PC. It sidesteps every Bluetooth headache at once: no pairing to lose, no dongle quality lottery, no dropouts mid-match, and the lowest input latency you can get from a DualSense. It also keeps the controller charged. The only cost is the tether.

Wireless is fine for couch play and slower-paced games, where a few milliseconds of extra latency and the small risk of a dropout don't matter. If you go wireless, a good Bluetooth adapter is the single biggest factor in whether the experience is smooth or maddening. The bundled radio on many motherboards is adequate; the $3 dongles are not. Position matters too, since sitting the adapter beside a USB 3.0 port is a reliable way to introduce interference you'll spend hours misdiagnosing as a controller fault.

If you play competitive shooters and care about every frame, wired removes one variable entirely, which is why a lot of PC players keep a long braided USB-C cable specifically for the controller and never think about Bluetooth again.

Driver cleanup, if it's still broken

If Windows sees the controller but it behaves strangely, a corrupt or duplicate driver can be the cause. In Device Manager, uninstall the DualSense-related entries (check "delete the driver software" if offered), unplug the controller, reboot, and reconnect so Windows reinstalls cleanly. If you've installed and removed DS4Windows or similar tools repeatedly, leftover virtual controller drivers (like ViGEmBus) can also confuse things; reinstalling DS4Windows freshly usually rebuilds them correctly.

Confirm the fix

Once the controller connects, verify it actually works before you jump into a game. Open the trigger test and run through the bumpers and analog triggers, then check the sticks on the joystick calibration page. Sixty seconds here tells you the controller is fully functional, so if a game still misbehaves afterward, you know the problem is the game's settings and not your DualSense.

If you're weighing whether to keep using a DualSense on PC versus an older PlayStation pad you have lying around, our DualShock 4 vs DualSense comparison covers how each behaves on Windows.