SOLUTION: those who cannot get the controller to connect

[daktah]

i am on windows 10 ltsb 14393. i was having this problem for a few hours upon finding and trying to install this project where while the receiver was running on the libusb driver, the controller would not connect no matter what. i went back and forth reinstalling and trying different things when i finally figured out the (painfully obvious) solution.
i installed the latest libusb32 as well as the latest libusbk drivers as one of the comments suggested (dont know if is actually required, but it cant hurt), then the latest vjoy. then when it came time to run the chatpad application i simply opened the properties of the application, went to the compatibility tab, and set the executable to windows vista compatibility mode (not sp1 or sp2, it must plain vista) as well as run as administrator. upon opening it i synchronized the controller and receiver, and right away it worked perfectly, keyboard and all. mouse mode works, as well as the button combo to toggle it and the combo to turn off the controller. even the backlight on the chatpad lights up. everything seems to be working via vjoy inside the windows controller tester as well. upon closing and reopening the program, the console style press the jewel to connect system works.

a small thing, which may or may not be an issue depending on specific software, is that setting the triggers as buttons option changes the right stick from x and y rotation to z axis and z rotation. again, this may or may not be an issue depending on your specific games if they can recognize or let you configure specific axes.
also, in the original writeup is that you should configure vjoy to use 11 buttons, however you must actually tell it to use 12 otherwise the start button will not work.

[Kytech]

TODO (for self): Add this to a wiki page or a troubleshooting markdown file.

[davidalex342]

i am on windows 10 ltsb 14393. i was having this problem for a few hours upon finding and trying to install this project where while the receiver was running on the libusb driver, the controller would not connect no matter what. i went back and forth reinstalling and trying different things when i finally figured out the (painfully obvious) solution. i installed the latest libusb32 as well as the latest libusbk drivers as one of the comments suggested (dont know if is actually required, but it cant hurt), then the latest vjoy. then when it came time to run the chatpad application i simply opened the properties of the application, went to the compatibility tab, and set the executable to windows vista compatibility mode (not sp1 or sp2, it must plain vista) as well as run as administrator. upon opening it i synchronized the controller and receiver, and right away it worked perfectly, keyboard and all. mouse mode works, as well as the button combo to toggle it and the combo to turn off the controller. even the backlight on the chatpad lights up. everything seems to be working via vjoy inside the windows controller tester as well. upon closing and reopening the program, the console style press the jewel to connect system works.

a small thing, which may or may not be an issue depending on specific software, is that setting the triggers as buttons option changes the right stick from x and y rotation to z axis and z rotation. again, this may or may not be an issue depending on your specific games if they can recognize or let you configure specific axes. also, in the original writeup is that you should configure vjoy to use 11 buttons, however you must actually tell it to use 12 otherwise the start button will not work.

I am aware that it has been a long time since you managed to get this to work, but could someone help me out with this? I am eager to try it out, have been using the wireless controller for ages now, and found a chatpad that im willing to try.

I installed everything in the order as stated in the description and even tried running it in vista compatibility with admin rights, but even that didn't help. A video tutorial would be nice. :)

When I run the Chatpad software, it sees the controller as connected, but everything is grayed out and there are no instructions to be followed..

I'm on windows 10 aswell.
It works great! My bad, the joystick got disconnected somehow.
Sorry for waking up this topic.

[Kytech]

No worries @davidalex342, glad to hear that the information is still relevant. I probably should still put this somewhere in the README or I should make a wiki where I can compile these sort of troubleshooting steps.

[ZaithamOroth]

@Kytech Hi, friend, how are you? Can you specify how you solved the problem? I installed the updated Lubusb driver with Windows Vista compatibility as administrator. I restarted the controller and it connected without any problems. However, after that, Vjoy didn't recognize it, and after restarting the computer, the controller didn't reconnect. I'm really interested in using the chatpad on my PC, not so much for gaming, but for practical purposes. I hope this project continues after all this time.

[Kytech]

@ZaithamOroth when you mention that you installed the latest libusb driver with Windows Vista compatibility, did you download an old version of the driver or run the driver installer with Windows Vista compatibility mode? If that's the case, it may have resulted in an improper driver install. I think the original poster of the issue ran the chatpad app that you download from this repo with Vista compatibility mode, though that hasn't been required for this to run on Windows 10 without issues.

I'm suspecting it's an issue with the libusb driver. What I'd suggest trying is uninstalling the libusb driver, then reinstalling the libusb driver using Zadig. It's an alternate driver installer utility that might result in more reliable results.

[ZaithamOroth]

@Kytech Good evening, I corrected the driver installation procedure as described in the main project manual. I used libusb-win32-devel-filter-1.2.7.3, the latest version of vJoy, and the Xbox-360-Wireless-Chatpad version hosted by the project. I proceeded to open Xbox-360-Wireless-Chatpad as administrator with Windows Vista compatibility enabled. However, upon launching the program, I receive the error: [09-15-2025 3:57:12] - ERROR: Wireless receiver not found.

I then uninstalled the driver and installed the original receiver driver. Then, I installed zadig-2.9 by selecting the receiver driver:

However, the controller no longer connected, and the problem persists.

What could I be doing wrong?
I use Windows 10 22H2 (OS 19045.6332).

[Kytech]

It looks like the libusb driver may not be installed properly. Go to device manager and uninstall the Xbox 360 Wireless Receiver for Windows device, then unplug it and plug it back in until it gets detected again, then follow the steps I note below to reinstall.

Also, you shouldn't need to run the chatpad app in Vista compatibility. Try disabling that compatibility option, since it might interfere with communication between the chatpad app and the libusb driver.

Try these steps to reinstall the LibUSB Driver:

After disabling that compatibility option, do the following to reinstall the driver:

• In Zadig, select the wireless receiver, then make sure that the box for driver selection below the device name is set so that it says "libusb0" or "libusb-win32", or something to that effect (your screenshot had it as WinUSB, which would have installed the wrong driver). Click install
• Try unplugging the adapter and plugging it back in, then launch the application to see if it works. If not, try restarting your computer, just to be sure the driver loads.
• If that doesn't work, follow steps 4-7 in the libusb install steps on the README to install the libusb filter driver.
• Unplug and then reconnect the adapter, launch the app, and see if it works then. Try one more reboot, just in case, if it's not working.

If all those steps don't work, I'd recommend removing the receiver using device manager, then retry the libusb install process on the repo's README using libusb-win32 version 1.2.6, given that you mentioned you are using a different version. If you're still stuck, let me know, since I'll probably need to tinker with the driver installation steps to see if I can find a more reliable install method if none of those work.

One last question: Is your adapter a Microsoft-branded adapter, or is it 3rd party? I have had occasional issues with this app and 3rd party adapters, but it has worked reliably with 1st party adapters.

[ZaithamOroth]

@Kytech I followed the steps exactly as you instructed, my friend. When I replaced the libusb-win32 driver with zadig-2.9, the controller is no longer recognized even after restarting the computer.

And if I install the driver as a filter, either from zadig-2.9.exe or by installing libusb-win32-devel-filter-1.2.6.0, it recognizes the controller, but the program doesn't recognize the receiver.

Is it essential to have the official Microsoft wireless receiver? In fact, I use an Xbox 360 console receiver with a USB adapter, which works perfectly except for this feature.

I await your comment, brother.

[Kytech]

@ZaithamOroth I saw you opened a new issue for this. I'll respond with more details there.

[ZaithamOroth]

@Kytech In this case, is there a way to set the receiver's hardware ID so this app can recognize it?
I'll print the receiver's hardware ID:

USB\VID_045E&PID_02A9&REV_060:
USB\VID_045E&PID_02A9

[Kytech]

@ZaithamOroth USB device IDs are set by the USB device's firmware. I don't think there's a way to make Windows treat the device as though it has a different ID either.

Your best option is to pull down the source code, modify the line I quoted in #81 from Receiver.cs to match your IDs, recompile it, and try that. Even if you haven't coded in C# before, it should be straightforward to compile with Visual Studio Community (should be able to open the project, edit the file, and test run the modified version with the run button in Visual Studio, as long as you install the C# features for Visual Studio). If you run into issues trying to compile and run the project, feel free to let me know.

Also, if we could keep responses for this particular problem over in #81 to keep things more organized, that would be great.