Working Xbox 360 controllers on Windows is now possible.
Working Xbox 360 controllers on Windows is now possible.
I’ve been using an Xbox 360 controller on my PC for years, and it has always worked perfectly without any issues. However, after updating Windows to the 2004 version, it suddenly stopped recognizing the controller – it won't pair with the receiver at all. I’ve even tried reinstalling drivers manually through Device Manager, letting it choose the drivers itself, but nothing seems to work. It just doesn’t recognize it anymore. To fix this, I had to revert back to the 1909 version where everything was working fine. I made a backup of those drivers and attempted to install them in the 2004 version, but they didn't work either. Has anyone else found a workaround for this problem? I’m hesitant to update Windows again until we figure out how to resolve it.
So it is most likely faulty driver. If the core windows works and excel updates works, they most likely push it and ignore rest of the stuff that could work with it. Sorry to say, but I don't see any different way to overcome this, than just wait on 1909.
Here’s a rewritten version of the text, aiming for natural flow and human-like language:
“Let’s talk about getting my controller to work properly on Windows. It can be frustrating! I’ve found that using ‘Make Windows Remember This Device’ – then reconnecting it – seems to consistently get things working when connecting via Bluetooth. It's a bit of a tedious process, but it works surprisingly well across both versions of Windows (1809 and 2004).
I’ve also had some luck with the InputMapper emulator; while it might seem silly, it sometimes recognizes the controller correctly. And when connecting via USB cable, it's generally reliable too. It seems like a lot of troubleshooting is needed to get everything working perfectly – especially if you’re using older versions of Windows. Honestly, it can be pretty dull dealing with these compatibility issues!”
My Xbox 360 controllers are connect via an usb receiver that use wireless conection with the controller, and it can be paired like a console, but windows version 2004 doesn't recognize the receiver like it should so the controller keeps searching with a device to pair with. It stays like a unknow device, and not matter if i try to intall the right driver, it stays that way
The thing is, i know the controller, the receiver and the drivers that i use are fine, because they are working in my actual version (the old one 1909).
Ps4 controller are easier to connect, because is with BT
So it is most likely faulty driver. If the core windows works and excel updates works, they most likely push it and ignore rest of the stuff that could work with it. Sorry to say, but I don't see any different way to overcome this, than just wait on 1909.
Sorry to derail your thread OP, but have a question for you about this adapter you are using.
As a "for instance"...I had been using a dongle, PS3 controller, and SCP toolkit to use that controller with PC, and still do in my living room. I had some issue between one of my remaining controllers and the main pc so I swapped to Xbox One controller.
When I pair on this machine is via the bluetooth built in. Each single time I want to use I have to turn on, go pair in the console for BT, then on to game...before it was hit power button, hear sound, play.
Does this adapter you are using make like the second scenario?
I’m wondering if this device actually works—it’s the Black eTopSell Wireless Gaming Receiver from Newegg: https://www.newegg.com/black-etopsell-69...000Z-00010. It seems to primarily be designed for Xbox 360 controllers, and I’m a little concerned it might not work with PlayStation controllers.