How to Fix “No Controllers Connected” Error in DS5Windows (DualSenseX)

You connect your PS5 DualSense controller, Windows recognizes it, and Steam can even read its inputs. But when you open DSX, the application still says “No Controllers Connected.”

This usually means the controller connection is working at some level, but DSX is not detecting or accessing the device correctly. The cause could be Bluetooth pairing, a USB cable, another controller-mapping application, HidHide configuration, or a problem specific to your DSX version.

Work through the checks below one at a time. You do not need to reinstall every driver just because DSX cannot find your controller.

Before you begin: The older free GitHub version of DualSenseX, v1.4.9, is no longer supported or updated. The current Steam version is a separate release with a different development history. Make sure you know which version you are troubleshooting before following older driver instructions.

1. Restart DSX and Reconnect Your Controller

Start with the simplest fix. Sometimes restarting the application and reconnecting the controller is enough to resolve a temporary detection problem.

  1. Close DSX completely.
  2. Disconnect your DualSense controller.
  3. Wait a few seconds.
  4. Reconnect the controller using USB or Bluetooth.
  5. Open DSX again and check the connection status.

If the controller still does not appear, close other controller-mapping applications before trying again.

If you are using Bluetooth, test USB if possible. A wired connection makes it easier to determine whether the problem is related to wireless pairing.

2. Check Whether Windows Can Read the Controller

Before changing DSX settings, confirm that Windows can receive input from your DualSense.

  1. Press Win + R on your keyboard.
  2. Enter joy.cpl.
  3. Press Enter.
  4. Check whether the controller appears in the Game Controllers window.
  5. If it is listed, open its properties and test the available buttons and inputs.

The exact display can vary depending on your Windows setup and controller configuration.

If Windows cannot detect the controller or its inputs do not respond, troubleshoot the USB connection, Bluetooth pairing, or controller hardware first.

If Windows detects the controller and its inputs respond, continue with the DSX-specific checks.

Remember that appearing in joy.cpl does not guarantee that every application can access the controller in the same way. It is simply a useful first test.

3. Check Your USB Cable or Port

If you use a wired connection, make sure your USB-C cable supports data transfer.

Some cables can charge a controller without providing a working data connection. A charging light alone does not prove that Windows can communicate with the DualSense.

Try the following:

  • Use a USB-C cable known to support data.
  • Connect directly to a USB port on the PC instead of a hub.
  • Try another USB port.
  • Disconnect and reconnect the controller.
  • Test the controller again in Windows before reopening DSX.

If another cable fixes the problem, there is no reason to reinstall DSX or its supporting components.

4. Re-Pair the DualSense Over Bluetooth

If you are connecting wirelessly, the controller may appear in Windows without establishing a usable connection for your current setup.

Remove the existing pairing and connect it again.

  1. Open Settings → Bluetooth & devices in Windows.
  2. Find the DualSense or Wireless Controller entry.
  3. Remove the device.
  4. Turn Bluetooth off and back on.
  5. Turn off the controller if it is still powered on.
  6. Hold the Create button and PS button together until the light bar starts flashing.
  7. In Windows, select Add device → Bluetooth.
  8. Select the Wireless Controller entry when it appears.

Once pairing is complete, check whether Windows receives controller input. Then reopen DSX.

If Bluetooth still fails, test USB before changing any drivers. That helps narrow down whether the problem follows the wireless connection.

5. Close Other Controller-Mapping Applications

More than one controller application can complicate device detection.

For example, DS4Windows, Steam Input, or another controller utility may be handling or translating controller input in a way that conflicts with your intended setup.

For a clean test:

  1. Close DSX.
  2. Exit other controller-mapping applications that are running.
  3. Disconnect and reconnect the DualSense.
  4. Open DSX by itself.
  5. Check whether the controller appears.

Steam detecting the controller does not automatically mean Steam is causing the problem. The important question is whether another application or input layer is interfering with the configuration you are trying to use.

If DSX starts detecting the controller after you close another utility, test the applications separately before deciding which one needs to run.

6. Check HidHide Configuration

HidHide is designed to hide selected physical controller devices from applications. It is often used with virtual-controller setups to prevent a game from receiving duplicate input.

However, an incorrect configuration can make a controller appear unavailable to an application that needs access to it.

If you have installed HidHide, check its configuration before changing other drivers.

  1. Close DSX.
  2. Open the HidHide Configuration Client.
  3. Review the Devices tab to see which devices are selected for hiding.
  4. Review the Applications tab to check the applications allowed to access hidden devices.
  5. Confirm that the configuration matches your intended setup.

If you suspect HidHide is responsible, you can temporarily disable device hiding as a diagnostic test. Reconnect the controller, reopen DSX, and check whether detection changes.

If the controller appears when hiding is disabled, HidHide configuration may be involved. Re-enable hiding after the test and correct the configuration if necessary.

Do not assume HidHide is the cause simply because it is installed. If you do not use it, skip this step.

For more information, see the official HidHide project.

7. Check Your DSX Version Before Changing Drivers

This step matters because older DualSenseX guides often describe a different setup from the current Steam release.

The older GitHub version, v1.4.9, used supporting components such as ViGEmBus for virtual-controller emulation. That does not mean ViGEmBus is automatically required to make every current DSX installation detect a physical DualSense.

Before installing or removing anything, identify the version you are using.

  • Current Steam DSX: Check the current application’s documentation and requirements.
  • Legacy GitHub DualSenseX v1.4.9: Follow instructions specifically written for that older release.
  • Virtual-controller emulation: Check whether your particular configuration requires a virtual-controller driver.

You can find the current Steam release on the official DSX Steam page and the older project’s releases on GitHub.

Avoid downloading replacement drivers from unrelated websites or removing working components without first identifying the cause.

8. Does ViGEmBus Need to Be Installed?

Not necessarily.

ViGEmBus was used by the legacy DSX application to create virtual controller outputs, such as an Xbox 360 or DualShock 4 controller. It is not a universal fix for physical-controller detection problems.

If DSX detects your physical DualSense but a game cannot see the virtual controller you selected, the virtual-controller setup may need attention.

If DSX cannot detect the physical controller at all, start with the USB or Bluetooth connection, Windows input testing, other controller applications, and HidHide if installed.

Also note that the ViGEmBus project has been retired and archived. Review its official end-of-life information before relying on older installation instructions.

9. Check for a DSX Configuration or Application Problem

If Windows receives controller input but DSX still shows no connected controllers, review the settings available in your specific DSX version.

Do not assume every version has a setting called “Device Options” or a toggle that enables DualSense detection. Menu names and available options can differ.

Instead:

  1. Open DSX and review its controller-related settings.
  2. Look for any documented device or connection settings relevant to your version.
  3. Check whether the application has an available update.
  4. Close and reopen DSX after making a relevant change.
  5. Test the controller again.

If the problem began immediately after a DSX update or configuration change, that detail may help identify the cause.

Avoid resetting every setting at once. Make one change, test it, and move on if it does not help.

10. Restart Windows Before Reinstalling Anything

A full Windows restart is worth trying if the controller was previously working and suddenly stopped appearing in DSX.

Save your work, restart the PC, reconnect the DualSense, and open DSX again.

This is particularly useful after installing or removing a driver or changing device configuration.

If the error remains, return to the earlier checks and identify which part is failing. Reinstalling the entire application should not be the first response to every detection problem.

11. When Should You Reinstall DSX?

Consider reinstalling DSX only after you have confirmed that:

  • Windows can detect the controller.
  • The controller responds in Windows’ controller test.
  • USB or Bluetooth is working.
  • Other controller-mapping applications have been ruled out.
  • HidHide is not incorrectly hiding the device, if installed.
  • You have checked the requirements for your particular DSX version.

Before reinstalling, identify whether you use the current Steam release or the discontinued GitHub version. Follow the appropriate uninstall and installation instructions rather than mixing the two setups.

For the broader removal procedure, see our How to Uninstall DS5Windows (DualSenseX) guide.

12. How to Tell Whether the Controller Has a Hardware Problem

A “No Controllers Connected” message does not automatically mean the DualSense is faulty.

To narrow it down, try testing the same controller on another PC, if available. You can also test a different DualSense on your current computer.

These tests help distinguish a controller-specific problem from a Windows or application configuration issue.

Consider a hardware problem if the controller repeatedly fails over both USB and Bluetooth, does not respond on other devices, or shows other persistent connection problems.

If necessary, use the official PlayStation PC accessories and support resources for firmware and controller support information.

Quick Troubleshooting Checklist

Before making major changes, work through these checks:

  • Restart DSX and reconnect the DualSense.
  • Test the controller using joy.cpl.
  • Try a known-good USB data cable and another port.
  • Remove and recreate the Bluetooth pairing if using wireless.
  • Close other controller-mapping applications.
  • Review HidHide settings if HidHide is installed.
  • Confirm which DSX version you are using.
  • Check driver requirements for that version and for your intended controller mode.
  • Restart Windows.
  • Test the controller on another PC if the problem persists.

Change one thing at a time and check the result before moving to the next step. That makes it easier to identify the actual cause instead of creating additional problems while troubleshooting.

Frequently Asked Questions

Why does Steam detect my DualSense but DSX does not?

Steam and DSX are separate applications and may access or handle controller input differently. If Steam sees the controller, test it in Windows, close other controller utilities, and check HidHide if you use it. Also confirm that your DSX version is compatible with the setup you are following.

Do I need ViGEmBus to fix “No Controllers Connected”?

Not in every case. ViGEmBus is associated with virtual-controller emulation in the legacy DSX setup. First determine whether DSX is failing to detect the physical controller or failing to create a virtual controller output.

Can HidHide prevent DSX from detecting my controller?

An incorrect HidHide configuration can interfere with access to a hidden device. Check its device and application settings, and temporarily disable device hiding only as a diagnostic test if needed.

Should I reinstall DSX immediately?

No. First check whether Windows detects the controller, test USB or Bluetooth, and rule out conflicting controller software. Reinstall only after the simpler checks have narrowed down the problem.

Does this error mean my DualSense is broken?

Not necessarily. The error can be caused by software configuration, device access, connection problems, or version-specific requirements. Testing the controller on another PC is one way to determine whether the problem follows the hardware.

Related Guides

Leave a Comment