The DualSense is one of the better PC controllers you can buy, and it is also one of the more temperamental to connect. Windows sees it as a generic device called Wireless Controller, Sony provides very little PC-side software, and the controller can only hold one Bluetooth pairing at a time. Between those three facts sit most of the problems people run into.

Here are nine fixes in the order I would actually try them, from the ones that take ten seconds to the ones that involve Device Manager.

Fix 1: Check the cable is a data cable

Start here, because it costs nothing and it is the answer more often than anyone admits.

Plenty of USB-C cables are charge-only. They have power lines and no data lines. Plugged into a DualSense, the light bar comes on, the battery charges, and Windows never sees a device. The cable that came with a phone charger is a common offender. The cable that came with your PS5 is a data cable and is the one to test with.

If the light bar lights but nothing appears in Windows, swap the cable before anything else. Also try a rear motherboard port rather than a front panel one, since front panel headers are a frequent source of flaky USB.

Fix 2: Pair Bluetooth using the right button combination

The DualSense does not enter pairing mode the way most Bluetooth devices do.

With the controller off, hold the Create button, which is the small button to the left of the touchpad where Share used to be, and the PS button together for about five seconds. The light bar should flash rapidly in a double-pulse pattern. That is pairing mode. A slow pulse or a solid colour means it is trying to reconnect to something else instead.

Then on Windows: Settings, Bluetooth and devices, Add device, Bluetooth. It will appear as Wireless Controller. Not DualSense, not PS5 Controller. Select it and it should connect without asking for a PIN.

If a device called Wireless Controller is already listed from a previous attempt, remove it first. Stale pairings are a very common cause of a controller that flashes forever and never connects.

Fix 3: Unpair it from your PS5 first

A DualSense stores exactly one Bluetooth host at a time. Pairing it to your PC breaks the PS5 pairing, and reconnecting it to the PS5 breaks the PC pairing. This is not a fault; it is how the controller works, and it is why the pad that worked yesterday will not connect today.

If you switch between console and PC regularly, you have three options. Use a cable on whichever platform you use less. Re-pair each time, which takes about fifteen seconds. Or keep a second controller. There is no setting that makes a DualSense hold two pairings.

Worth knowing that turning the PS5 off does not release the pairing. The pairing is stored in the controller, not the console.

Fix 4: Rule out the Bluetooth adapter itself

Not every Bluetooth adapter works with a DualSense, and the failure mode is a controller that pairs and then immediately disconnects, or connects with buttons working and motion or rumble dead.

The DualSense needs Bluetooth 4.0 or newer and works reliably only on the Microsoft Bluetooth stack. Adapters that ship with their own third party stack are the usual problem. Toshiba's stack has never worked properly with Sony controllers, and some CSR-based adapters fail even when the same chip works fine under the Microsoft stack.

Check what you have in Device Manager under Bluetooth. If the entry shows a manufacturer stack rather than a generic Microsoft driver, that is a strong candidate.

The other adapter problem is physical placement. USB 3.0 ports and devices emit interference in the 2.4GHz band, which is exactly where Bluetooth lives. A Bluetooth dongle plugged into a USB 3.0 port next to an external drive is a well-documented recipe for dropouts. Move the dongle to a USB 2.0 port, or use a short extension cable to get it away from the case.

If the controller works flawlessly wired and badly over Bluetooth, that is the direction to look. Our comparison of Bluetooth versus wired input lag covers what you are actually trading when you choose one over the other.

Fix 5: Confirm Windows sees it before blaming the game

Once the controller connects, verify it is reporting properly before troubleshooting further.

Press Windows + R, type joy.cpl, and check that Wireless Controller is listed with status OK. If it appears there, Windows is receiving input and any remaining problem is game or software side.

For a fuller picture, run it through a PS5 controller tester and press everything. This separates two very different problems: a controller that is not connecting, and a controller that is connected but reporting only some of its inputs. A button test will pick up individual switches that have stopped registering, which is a hardware fault rather than a connection one.

If Windows sees the controller and a specific game does not, the game almost certainly wants XInput and the DualSense speaks DirectInput. That is a translation problem, not a connection problem, and Steam Input or DS4Windows solves it.

Fix 6: Sort out Steam's configuration support

Steam has its own controller layer, and it interacts with everything else on your system.

In Steam, go to Settings, Controller. Make sure PlayStation Configuration Support is enabled if you want Steam to handle the DualSense, including gyro, touchpad, and adaptive triggers in supported titles.

The conflict comes when you run Steam Input and a third-party tool like DS4Windows at the same time. Both create a virtual controller; the game sees two devices, and you get double input: menus that skip two entries per press, or a character that walks when you tilt the stick halfway. Pick one layer and disable the other.

Non-Steam games can still use Steam Input if you add them to your library as a non-Steam game, which is often simpler than installing a separate tool.

Fix 7: Update the controller firmware

Sony ships a Windows application for this. The PlayStation Accessories app for PC lets you update DualSense firmware and adjust some controller settings without a console. Earlier there was a standalone firmware updater tool that did the same job.

Firmware updates have fixed real connection bugs, and running one takes a few minutes over USB. If your controller has never been connected to a PS5, it may be running launch firmware from years ago.

While you are there, it is worth ruling out a deeper controller fault. Our DualSense troubleshooting guide covers the hardware faults that connection problems sometimes mask.

Fix 8: Reset the controller

There is a small pinhole on the back of the DualSense, near the Sony logo beside the upper screw. Push a paperclip or SIM tool in and hold for about five seconds.

This clears stored pairings and resets the controller's internal state. After a reset, connect over USB first and press the PS button, then re-pair over Bluetooth if you want wireless.

It is a genuinely useful step for a controller stuck in a pairing loop, and it costs you nothing except having to re-pair with your PS5 afterwards.

Fix 9: Clear driver conflicts and ghost devices

If you have ever installed DS4Windows, DualSenseX, reWASD or a similar tool, leftovers can block a clean connection.

In Device Manager, enable View, Show hidden devices. Look under Human Interface Devices and Bluetooth for greyed-out entries relating to Wireless Controller or virtual controllers. Ghost entries from old pairings and uninstalled tools accumulate and occasionally take priority over the real device.

Uninstall the greyed-out entries, unplug the controller, reboot, and reconnect.

The other thing to check is USB power management. In Device Manager, find the USB Root Hub entries, open Properties, Power Management, and untick the option allowing Windows to turn the device off to save power. Do the same for the Bluetooth adapter. This setting causes controllers to disconnect after periods of inactivity and is a favourite of laptops in particular.

If you use ViGEmBus-based tools, note that the ViGEmBus project has been retired and its final release dates from late 2023. It still works on current Windows 11 builds, but having multiple versions installed causes exactly this kind of conflict. Nefarius publishes a cleanup tool called Legacinator for removing old driver residue.

When it is the controller, not the PC

Test the pad on another device. A DualSense that refuses to connect to a PS5, a phone, and a PC is faulty rather than misconfigured.

Common physical causes are a damaged USB-C port from repeated cable strain, water ingress, and battery degradation that leaves the controller without enough power to maintain a Bluetooth link.

If it is under warranty, that is the route. Sony's manufacturer warranty runs twelve months in the US and Canada. In the UK and Germany, EU-derived consumer law generally gives you two years against the retailer you bought from. Australian Consumer Law does not fix a period and instead asks what a reasonable person would expect, which has covered controller faults past the twelve-month mark.

If you are weighing whether to repair or switch platforms entirely, our DualShock 4 versus DualSense comparison covers what you gain and lose either way on PC specifically.

Additional troubleshooting and buying advice

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.

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 not zero.

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.

Fix 1: Swap the USB cable (it's usually the cable)

Plug the DualSense into your PC with a USB-C cable and listen for the Windows connection chime. Nothing? The cable is your prime suspect, by a wide margin.

Many USB-C cables, especially the short ones bundled with phones, earbuds, and power banks, are charge-only and carry no data. The controller will light up and charge but never appear as an input device, which looks exactly like a connection failure. Swap to a cable you know transfers data, and plug directly into a rear motherboard port rather than a front-panel port or a hub. This one swap resolves a huge share of "won't connect" reports, so never skip it.

Fix 2: Put it in Bluetooth pairing mode correctly

If you want wireless, the DualSense pairs over standard Bluetooth, so any PC with Bluetooth 4.0 or newer handles it. Desktops without built-in Bluetooth need a USB adapter, and quality matters here, since cheap dongles cause the dropouts people later blame on the controller.

To enter pairing mode, the controller must be fully off first. Then hold the PS button and the Create button (upper-left of the touchpad) together for about five seconds until the light bar flashes in a rapid double-blink. That flash means it's discoverable. On the PC, open Settings > Bluetooth & devices > Add device > Bluetooth and select "Wireless Controller."

The most common reasons this fails: the controller wasn't fully off before you started, so it never entered pairing mode cleanly, or a stale pairing from a previous session is interfering. If it won't appear, remove any old "Wireless Controller" entry from your Bluetooth list, then pair it again.

Fix 3: Reset the controller

A DualSense that refuses to pair or behaves erratically often needs a reset, particularly one recently used on a PS5 or phone. On the back near the Sony logo is a tiny hole. Push a straightened paperclip in, hold the recessed button for about five seconds, then reconnect over 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.

Frequently Asked Questions

How do I put a DualSense into Bluetooth pairing mode?
With the controller off, hold the Create button and the PS button together for around five seconds until the light bar flashes rapidly in a double pulse. A slow pulse means it is trying to reconnect to a previously paired device instead of accepting a new one.
Why does my PS5 controller disconnect from my PC every time I use it on my PS5?
The DualSense stores only one Bluetooth pairing at a time, so connecting it to the console overwrites the PC pairing and vice versa. There is no setting that changes this. Use a cable on one platform, re-pair each time, or keep a second controller.
Windows sees my DualSense but games do not. What is wrong?
The controller reports as a DirectInput device, and most PC games expect XInput. Enable PlayStation Configuration Support in Steam's controller settings, or use a translation tool like DS4Windows. Do not run both at once, since two virtual controllers cause double input.
Does the DualSense need a driver on Windows 11?
No. Windows 11 recognises it as a generic HID device called Wireless Controller over both USB and Bluetooth with no driver installation. You only need additional software to translate it to XInput or expose features like gyro and adaptive triggers.
My DualSense pairs then disconnects immediately. What causes that?
Usually the Bluetooth adapter. The DualSense needs Bluetooth 4.0 or newer on the Microsoft stack, and adapters with their own third-party stack often fail this way. Interference from USB 3.0 devices near the dongle is the other common cause, so try a USB 2.0 port or a short extension cable away from the case.
A

Written by Admin

Hardware testing engineer and contributor at MyGamepadTester. Specializes in controller input latency diagnostics, potentiometer stick drift calibration, and hall effect joystick upgrades.