Wireless Receiver Not Found when using Official Microsoft Adapter Pulled from Xbox360 Console

[ZaithamOroth]

Hi, I know it's been a while I've been trying this for quite some time without success, no matter how I do it, when running Xbox-360-Wireless-Chatpad, I always get the error [14-09-2025 21:23:51] - ERROR: Wireless Receiver Not Found.

I am operating on Windows 10 22H2 and I have followed the following steps.,
Busy program versions:- libusb-win32-devel-filter-1.2.7.3

• libusbK-3.1.0.0-setup
• zadig-2.9- vJoySetup (latest version)- Xbox-360-Wireless-Chatpad
  first install libusb-win32-devel-filter-1.2.7 and later run to synchronize the Xbox 360 receiver, then run install-filter-win.exe to filter the "Xbox 360 Wireless Receiver for Windows" controller with which you already The Xbox 360 controller works. When filtering, run vJoy with the following settings:

After this, the controller synchronization works but when running "Xbox 360 Wireless Chatpad.exe" it simply does not recognize the receiver by throwing the error [14-09-2025 21:40:46] - ERROR: Wireless Receiver Not Found.

I ran the Xbox 360 Wireless program Chatpad.exe as an administrator and with Windows Vista support turned on, but the problem persists.

Thinking that the problem is the libusb-win32-devel-filter-1.2.7.3 driver, I have uninstalled the driver and subsequently tried to filter the original receiver driver with libusbK-3.1.0.0-setup and zadig-2.9

But I can't get "Xbox 360 Wireless Chatpad.exe" to recognize the program.
Is there anyone who has currently had the chatpad work with this method in Windows 10? If so, is there anything I can fix in the procedures described or any versions of the drivers and programs used that suggest I should try? I would greatly appreciate it if someone could give me a little guidance on what I'm doing wrong. Best regards.

[Kytech]

@ZaithamOroth It looks like your adapter has a different device ID compared to what the standard PC adapter has, based on your Zadig screenshot. You mentioned in your comment on #75 that your adapter was pulled from a console, which would explain the difference.

The application is trying to connect to a USB device with a different Vendor and Product ID, based on the code responsible for connecting to the receiver:

// Open the Xbox Wireless Receiver as a USB device
// VendorID 0x045e, ProductID 0x0719
wirelessReceiver = UsbDevice.OpenUsbDevice(new UsbDeviceFinder(0x045E, 0x0719)) as IUsbDevice;

That's the ID for the adapter Microsoft made and sold for PCs. Your adapter's Vendor ID matches, but not the Product ID portion.

I'd guess that the receiver you pulled from the console uses the same protocol, so there's a very high chance that recompiling the application with the device ID values set to match your adapter (changing the 0x0719 to 0x02A9 on the line I copied over from Receiver.cs), along with following the standard driver install steps you initially tried, would make it work, if you would want to give that a shot. I can't say with 100% certainty that it will work, but I'd say it's quite likely that it would work.

[ZaithamOroth]

Incredibly...it worked.

I downloaded the project zip file and used Visual Studio Community 2022 to edit the Receiver.cs file as you said. It compiled without a hitch.

I installed libusb and filtered the same driver used. I simply launched vJoy and then the edited and compiled program. At first, it didn't recognize it, but after a restart, it did.

I had little hope that a console accesory over 17 years old would work on my computer, but it's incredible what these projects achieve.

Thank you so much.

The functionality is perfect.
The only thing I would edit is the mouse speed when pressing LT to make it a little faster, but everything else is perfect.

Thank you again, dear friend. I hope there are more updates on this project.

[Kytech]

@ZaithamOroth I'm glad to hear it works with the adapter you pulled from the console after changing those IDs!

I should probably release an update to the application so that it tries that device ID as well, if it can't find the ID that Microsoft uses on the PC-marketed adapters. I'll leave this issue open for now, then I'll close it once that change is made.