InputMapper is open, your controller is plugged in or paired, and the device list stays empty with a “No compatible controllers detected” message. Nothing is broken yet — this message simply means InputMapper has not seen a supported controller in a usable state. Work through this checklist in order, because the most common causes are also the quickest to rule out: the cable, the pairing, and what Windows itself can see.
If your controller connects but then misbehaves in games, that is a different problem covered in our troubleshooting hub. This guide is only about getting a controller detected in the first place, following the same basic flow as how to use InputMapper for the first time.
First, Confirm the Controller Is Supported
InputMapper officially supports the DualShock 4, DualShock 4 V2, Xbox 360 and Xbox One controllers, the DualShock 3 and PlayStation Move Navigation controller only via a Magic-NS dongle, and generic DirectInput and XInput devices. That list matters because two popular pads are not on it: the DualSense and the Switch Pro Controller are not supported by InputMapper at all.
If you are holding a DualSense, no cable or setting in this checklist will make InputMapper detect it. Use our guide to the DualSense on PC or the DS4Windows install guide instead. Switch Pro owners should likewise use a tool that supports that controller. For every supported pad, continue below.
Check 1: Data Cable vs Charge-Only Cable
The single most common cause of a wired DualShock 4 not being detected is a charge-only micro-USB cable. Many cables bundled with chargers and power banks carry power but no data lines. The controller lights up and charges, which makes the cable look fine, while Windows receives no data at all and InputMapper sees nothing.
Swap in a cable you know carries data — for example, one you have used to transfer files to a phone. Keep it short and plug it directly into a motherboard USB port rather than a front-panel port or unpowered hub for the test. Then watch Windows, not just InputMapper: a newly recognised controller should appear in Device Manager and in the Game Controllers panel. If a known data cable fixes detection, retire the old cable for controller use so you do not repeat the diagnosis next month.
Check 2: Bluetooth Pairing State
If you connect over Bluetooth, start by checking the pairing state in Windows Bluetooth settings. A controller that shows as paired but not connected, or that was paired to another device or user profile in between, often stays invisible to InputMapper. Remove the controller from the Bluetooth device list entirely, put it back into pairing mode, and pair it again as a fresh device.
Stay close to the PC during pairing and make sure the controller is charged; a nearly empty battery can drop the connection before InputMapper ever enumerates the device. Our Bluetooth pairing guide covers the exact pairing sequence and clean setup from scratch. If pairing repeatedly fails or the device vanishes, test with USB instead — the next check explains why that comparison is so useful.
Check 3: What Does Windows See?
Press the Windows key, type joy.cpl, and open the Game Controllers panel. This panel shows what Windows itself can see, independent of InputMapper. If your controller appears here, Windows has a working connection and the problem sits inside InputMapper or its drivers, so continue to the next checks. If the controller does not appear here either, InputMapper cannot invent it: fix the connection itself first, using the cable and pairing checks above.
While the panel is open, select the controller and open its properties to test a few buttons and sticks. Live responses confirm the device is not just listed but actually reporting input. A device that is listed but never responds is often connected over a failing cable, a weak Bluetooth link, or with a flat battery, even though it looks detected at first glance.
Check 4: Refresh InputMapper’s Device List
Sometimes Windows sees the controller but InputMapper’s list was built before the device was ready. Disconnect the controller, close InputMapper completely, reconnect the controller, wait a few seconds for Windows to settle, and only then reopen InputMapper. Starting InputMapper after the controller is already present gives it the cleanest chance to enumerate the device.
Also connect one controller at a time during diagnosis. Multiple pads, dongles, and virtual devices from other tools make it hard to tell which entry InputMapper is reacting to. Once detection works with a single controller, you can reconnect your other hardware and confirm everything still works together.
Check 5: Is ViGEmBus Installed?
InputMapper 1.7 outputs its virtual Xbox controller through ViGEmBus, the independent driver project by nefarius. If ViGEmBus is missing or its installation failed, InputMapper may have nothing to attach its output to and device handling can stall. The final ViGEmBus release is 1.22.0 from November 2023, distributed through GitHub releases only.
If you suspect the driver is missing, follow our ViGEmBus install guide rather than grabbing an installer from a random download site. Never use vigem.org: that domain was handed over, and old updaters pointing there are a documented risk. A reboot after installing the driver is not optional — complete it before retesting detection.
Check 6: Try the Other Connection Type
End the checklist by crossing over: if you have been testing over Bluetooth, test wired, and if you have been testing wired, test over Bluetooth (or on another USB port). This one comparison splits the problem in half. Detection over USB but not Bluetooth points at pairing, the adapter, or interference. Detection over Bluetooth but not USB points at the cable or the port. Detection on neither path, with Windows also seeing nothing, points at the controller itself — try it on another PC or console to confirm it still works.
Hardware Causes: Cable and Dongle
When the checklist points at hardware, replace the weak link rather than reinstalling software again. A short, proper data cable removes the most common wired failure, and a decent Bluetooth adapter placed close to your desk removes the most common wireless one.
Get a Data Micro-USB Cable on Amazon
Get a Bluetooth Dongle on Amazon
Affiliate link — see our Affiliate Disclosure.
Frequently Asked Questions
Why does InputMapper say no compatible controllers detected?
InputMapper has not seen a supported controller in a usable state. The most common reasons are a charge-only USB cable that carries no data, a stale Bluetooth pairing, or the controller not appearing in Windows at all. Work through the cable, pairing, and joy.cpl checks in this guide in order.
Does InputMapper detect the DualSense or Switch Pro Controller?
No. InputMapper officially supports the DualShock 4, DualShock 4 V2, Xbox 360, Xbox One, DualShock 3 via Magic-NS, and generic DirectInput and XInput devices. The DualSense and Switch Pro Controller are not supported and will not be detected.
How can I tell if my USB cable carries data?
Test the cable by transferring a file to a phone or another device. If it only charges, it is a charge-only cable and a DualShock 4 connected with it will never appear in Windows or InputMapper, even though the light bar turns on.
What should I check if Windows sees the controller but InputMapper does not?
Restart InputMapper after the controller is already connected so its device list is rebuilt, connect only one controller while testing, and confirm ViGEmBus 1.22.0 is installed from GitHub releases with a reboot afterwards.