USB controller connection: cables, ports and testing

Wired connection is the simplest baseline for troubleshooting.

A charging light is not a data test

Some cables carry power only; others develop damaged data conductors while still charging. Use a cable known to transfer data and connect directly to the PC rather than through a hub for the initial check.

Connect and verify

Connect the correct cable: micro-USB for DualShock 4, USB-C for DualSense/Edge and Switch Pro.
Wait for Windows device detection.
Open joy.cpl and inspect controller input, or use a browser tester if accessible.
Start DS4Windows and select the detected physical controller.
Choose a simple output profile and verify the virtual device separately.

If the connection is intermittent

Inspect the cable and controller socket without forcing the connector. Try another PC port and a second cable. If movement of the cable reliably disconnects the pad, solve the hardware connection before changing profiles or drivers.

USB audio can change Windows defaults

Connecting a PlayStation controller can add speaker, headphone or microphone endpoints. If your ordinary speakers go silent, check Windows Sound output and per-app routing. Detection of an audio endpoint does not establish that a game has routed audio to it.

When Windows sees it but the app does not

Check the controller-family setting and HidHide allowlist. A hidden physical pad can still be connected correctly. DualShock 3 requires its dedicated driver setup; a standard cable alone does not provide the DS4Windows integration.

Sources: Nexus release documentation · Project and screenshot credits. Updated 11 November 2026.