Skip to main content

PS5 DualSense Controller Not Connecting to PC via Bluetooth — The Windows 11 Setting That's Blocking It

I spent two hours trying to get my PS5 DualSense controller connected to my Windows 11 PC via Bluetooth before I found the actual problem. The controller would show up in Windows' Bluetooth devices list, I'd click "Connect," and it would pair — then disconnect within 5 seconds. Or it would show as "Connected" in the Bluetooth menu but not be recognized as a controller in any game or in Steam.

The standard advice — hold the PS button and Share button until the light bar flashes, then pair in Windows — had me doing it over and over without success. Here's the specific Windows 11 setting that was blocking the connection, and why the standard pairing instructions alone aren't enough on Windows 11.

Why DualSense Bluetooth Fails Specifically on Windows 11

Windows 11 introduced Bluetooth LE Audio — a new Bluetooth protocol that improves audio streaming efficiency and adds support for features like hearing aid connectivity. Bluetooth LE Audio is enabled by default on Windows 11 on any system with a compatible Bluetooth adapter.

The DualSense controller uses Bluetooth HID (Human Interface Device) protocol for its input connection. On Windows 11, Bluetooth LE Audio and Bluetooth HID compete for the same Bluetooth adapter resources during the device negotiation phase — the initial handshake where Windows and the controller agree on which Bluetooth profile to use.

When this competition occurs, Windows 11 sometimes initiates the connection using LE Audio parameters instead of HID parameters — which causes the DualSense to appear paired but non-functional, because the controller's input signals aren't being transmitted over the correct Bluetooth profile. The controller shows as "Connected" because the Bluetooth link is technically established, but nothing works because the wrong profile is active.

This is why the controller connects and immediately disconnects on some systems (Windows rejects the LE Audio handshake when it detects the device isn't audio-compatible), and shows as connected but non-functional on others (the LE Audio handshake completes but transmits nothing useful).

The Exact Fix — Disable Bluetooth LE Audio in Windows 11 Device Manager

Step 1 — Open Device Manager

Press Windows key + X > select "Device Manager." Expand the "Bluetooth" section by clicking the arrow next to it.

Step 2 — Find your Bluetooth adapter entry

Look for an entry that says something like "Intel Wireless Bluetooth," "Realtek Bluetooth Adapter," or your specific adapter name. Right-click on it > "Properties."

Step 3 — Disable Bluetooth LE Audio in the adapter properties

In the Properties window, click the "Advanced" tab. Look for a setting called "Bluetooth LE Audio" or "LE Audio" in the property list. Select it, then in the Value dropdown on the right, change it from "Enabled" to "Disabled." Click OK.

If you don't see a Bluetooth LE Audio option in the Advanced tab: your Bluetooth adapter doesn't support LE Audio, which means this isn't your issue — skip to the alternative fix below.

Step 4 — Restart the Bluetooth service without restarting your computer

Press Windows key + R > type "services.msc" > press Enter. Find "Bluetooth Support Service" in the list > right-click > "Restart." This restarts the Bluetooth service with the LE Audio setting disabled, without requiring a full system restart.

Step 5 — Put the DualSense into pairing mode and reconnect

Hold the PS button and the Create button (not the Share button on PS4 — the Create button on DualSense is in the same position but has a different name) simultaneously for 3 seconds until the light bar flashes rapidly in blue. Then go to Windows Settings > Bluetooth & devices > "Add device" > "Bluetooth" and select "Wireless Controller" when it appears.

The controller should now connect and stay connected because Windows is negotiating the HID profile without LE Audio interference.

Alternative Fix — If Your Adapter Doesn't Have the LE Audio Setting

If your Bluetooth adapter's Device Manager properties don't show a Bluetooth LE Audio toggle, the protocol conflict can be resolved through a different approach: connecting the DualSense through USB first to establish the HID profile, then switching to Bluetooth.

Connect the DualSense to your PC with a USB-C cable. Windows will automatically install it as a HID controller. Open a game or Steam and confirm the controller is recognized and functional over USB.

While the USB connection is active, hold the PS button and Create button for 3 seconds to put the controller into Bluetooth pairing mode simultaneously with the USB connection. Add the device through Windows Bluetooth settings. Because the HID profile is already established via USB, Windows negotiates the Bluetooth connection using the HID profile rather than LE Audio.

After pairing, disconnect the USB cable. The Bluetooth connection maintains the HID profile that was established during the USB-simultaneous pairing.

One More Specific Issue — DualSense Shows as "Audio Device" Instead of "Controller"

If your DualSense connects via Bluetooth and Windows recognizes it as an audio device rather than a controller (you can check in Device Manager under "Sound, video and game controllers" versus "Human Interface Devices"), this confirms the LE Audio profile issue exactly.

In this state, the DualSense's speaker and microphone are being routed through Windows as a Bluetooth audio device — which is technically correct behavior for LE Audio — but the controller inputs aren't being processed because Windows expects audio data, not HID input data.

Fix this specific scenario: in Device Manager, find the DualSense entry under "Sound, video and game controllers," right-click > "Uninstall device" > check "Delete the driver software for this device" > confirm. Then disable LE Audio as described above and re-pair. Windows will re-detect it as a HID device rather than an audio device.

Using Steam as an Alternative to Windows Bluetooth Pairing

If the Device Manager fix doesn't apply to your adapter and the USB-simultaneous method doesn't work, Steam's controller support bypasses Windows' Bluetooth profile negotiation entirely.

Open Steam > Settings > Controller > enable "PlayStation Controller Support." Put the DualSense in pairing mode. Steam's Bluetooth stack handles the HID negotiation independently of Windows' Bluetooth settings, and it consistently succeeds where Windows' native Bluetooth pairing fails for DualSense.

The limitation: Steam's controller handling only works within Steam games and Steam Big Picture mode. If you want the DualSense to work as a system-wide controller outside of Steam, the Device Manager fix is the correct solution.

Pro Tip: Use DS4Windows as a Permanent Solution if Bluetooth Keeps Dropping

After fixing the initial pairing issue, some users find the DualSense Bluetooth connection remains unstable — dropping every 15 to 30 minutes during gameplay. This is a separate issue from the initial pairing failure and is caused by Windows' power management putting the Bluetooth adapter to sleep to save energy.

Install DS4Windows (ds4-windows.com — free, open source) and in its settings, go to Settings > "Prevent Sleep." This keeps Windows from applying power management to the Bluetooth adapter during controller use.

Additionally, in Windows Device Manager, find your Bluetooth adapter > Properties > Power Management tab > uncheck "Allow the computer to turn off this device to save power." This removes the hardware-level power management that causes mid-session drops independently of DS4Windows.

Both changes together — DS4Windows' sleep prevention and the Device Manager power management setting — have eliminated mid-session Bluetooth drops on every Windows 11 system I've tried them on.


Last updated: July 2026. Steps are specific to Windows 11 with DualSense controller firmware version 3.xx and later. Bluetooth adapter models vary — the LE Audio setting may appear under different names depending on your adapter manufacturer.

Comments

Popular posts from this blog

YouTube Keeps Logging Me Out on Samsung Smart TV After the 2026 Update

If you've recently updated your Samsung Smart TV and now find yourself getting signed out of YouTube every few minutes, you're not alone. This issue spiked noticeably after the latest firmware rollout, and it's frustrating enough to make you want to throw the remote across the room. Here's what's actually going on, and how to fix it without resetting your entire TV.   Why This Is Happening The short version: the 2026 Tizen firmware update changed how Samsung TVs handle cached authentication tokens for third-party apps. YouTube relies on a locally stored session token to keep you logged in, and the update appears to be clearing or corrupting that token faster than it should — sometimes within minutes of signing in. This isn't a YouTube-side bug. It's a conflict between Samsung's updated app sandboxing and YouTube's token refresh cycle.   Common Fixes (Try These First) Restart the TV — Hold the power button for 5 seconds, not just a quick press. A sof...

Amazon Order Stuck on "Preparing for Shipment" for Over a Week? Here's What's Really Happening

Your order says "Preparing for Shipment" and it hasn't moved in days. You've refreshed the tracking page a dozen times, maybe even called support and gotten a generic script read back to you. So what's actually going on, and is there anything you can do besides wait? Let's break it down. What "Preparing for Shipment" Actually Means This status doesn't mean your package is sitting untouched. It means Amazon's fulfillment center has confirmed your order but hasn't yet handed it off to a carrier for scanning. The label may already be printed. The item may already be boxed. It's the handoff step — between warehouse and shipping carrier — that's stalling. There are three common reasons this drags on past 2-3 days: Inventory mismatch — the system shows stock available, but the physical item isn't where it's expected to be in the warehouse, triggering a manual recount Carrier capacity issues — especially common arou...

Paid for YouTube Premium but Still Seeing Ads? Here's the Real Fix

You upgraded to YouTube Premium specifically to get rid of ads, and now they're still showing up. Before you contact support and sit through a generic troubleshooting script, here's what's actually causing this — and the fix that works when the obvious steps don't. The Three Most Common Reasons Premium Isn't Blocking Ads Not all ad situations are the same. Which one you're dealing with changes what you need to do. 1. Your account isn't signed in on the device showing ads This is the most common cause and the easiest to miss. YouTube Premium is tied to your Google account, not to the app or device. If you're watching while signed out — or signed into a different Google account — YouTube has no way of knowing you're a Premium subscriber. Check the account icon in the top-right corner of the YouTube app and confirm it shows your correct profile. 2. Your Premium subscription lapsed without warning YouTube sometimes fails to send a renewal failu...