Opening DSX to a “No Controllers Connected” message, even though Windows or Steam clearly sees your DualSense, is frustrating but usually traces back to one of a handful of specific, fixable causes.
Checking DSX’s Device Settings
Occasionally, support for a specific controller type gets toggled off in settings, sometimes from an accidental click, sometimes carried over from a previous configuration.
- Open DSX and go to Settings
- Look for a Device Options or controller support section
- Confirm DualSense support is enabled, if you see it unchecked, check it
- Restart DSX (Stop, then Start) to apply the change
If you don’t see an obvious toggle matching this description, check nearby settings related to controller type detection, exact wording can vary a bit between versions.
Checking HidHide for Whitelist Conflicts
If you’re using HidHide to prevent double-input issues, a misconfigured whitelist can accidentally block DSX from seeing your controller at all, the opposite of what HidHide is supposed to do.
- Close DSX completely
- Open the HidHide Configuration Client
- Go to the Applications tab and confirm DSX’s executable is listed there correctly
- If it’s missing, or the path looks outdated (from a reinstall or update), add it fresh, or remove and re-add it
- As a diagnostic step, you can temporarily uncheck “Enable Device Hiding” under the Devices tab, if your controller immediately appears in DSX once hiding is disabled, that confirms HidHide’s whitelist is the issue, re-enable hiding once you’ve fixed the whitelist entry
Re-Pairing Over Bluetooth
If you’re connecting wirelessly, Windows can occasionally lose the controller’s pairing security key, leaving it showing as “Connected” in Windows settings while not actually sending usable data to any application.
- Open Windows Settings, Bluetooth & Devices
- Find your Wireless Controller, click the three dots, and select Remove Device
- Turn Bluetooth off and back on
- Put your DualSense back into pairing mode: hold Create/Share and PS together until the lightbar flashes rapidly in a double-pulse pattern
- On your PC, Add Device, Bluetooth, and select “Wireless Controller” again, don’t release the controller buttons until pairing completes
Checking Your USB-C Cable
If you’re connecting with a wire and getting no detection, it’s worth confirming the cable itself supports data transfer, not just charging.
Many budget cables, especially ones bundled with phone chargers, only carry power, not data. Swap to a cable you know handles data (the cable that ships with a PS5 console is a reliable reference point), and connect directly to a motherboard USB port rather than a front-panel hub or unpowered extension.
A Few Things Worth Checking Before Deeper Troubleshooting
Confirm the controller works at all. Test it briefly in Windows’ own controller check (joy.cpl via the Run dialog) to rule out a genuinely dead or malfunctioning controller before assuming it’s a DSX-specific software issue.
Restart DSX itself, not just your controller. Sometimes the app’s connection to the driver layer gets into a stuck state that a fresh restart clears, faster to try than working through every other step first.
Check for a second controller-mapping tool running simultaneously. If DS4Windows or another similar tool is also active, it can end up claiming the controller before DSX gets a chance to detect it.
If Nothing Above Resolves It
At this point, the issue may be at the driver level rather than anything specific to controller detection settings. Confirm ViGEmBus is properly installed, our Drivers page covers this along with HidHide setup in more depth. Our Troubleshooting guide also covers broader connection issues that might be contributing to detection failing consistently.
Working Through This Systematically
With this many potential causes, it helps to change one thing at a time and restart DSX between each attempt, rather than making several changes at once and hoping something works. If you fix a genuine issue (say, a HidHide whitelist problem) but also happened to change three other settings at the same time, you won’t know which change actually mattered, which makes it harder to fix quickly if the same issue recurs later. Working through the list above in order, testing after each step, tends to get you to a resolution faster than it feels like it should, even though it means more individual restarts along the way.
When It’s Actually a Hardware Issue
If you’ve worked through every software-side fix here, tested the controller successfully with joy.cpl, ruled out cable and Bluetooth pairing issues, and DSX still won’t detect it specifically, it’s worth considering whether the controller’s Bluetooth or USB hardware itself has degraded, more common on an older controller that’s seen a lot of use. Testing the same controller on a different PC, or a different controller on your current PC, is the most reliable way to isolate whether the problem is following the controller itself or staying with your system’s configuration.