xbox 360 controller driver windows 10 hde

The controller is also compatible with PCs the wireless version requires a Wireless Gaming Receiver. Original Xbox controllers are not compatible with the Xbox 360.

The Xbox 360 controller comes in both wired and wireless versions. It is a newer white Dualshock 4, that's the only thing hardware-wise that's changed as far as I know.The Xbox 360 Controller is the primary controller for Microsoft's Xbox 360 console and was introduced at E3 2005. Salt and Sanctuary refuses to let me use the controller, even though it's input is visible in DS4Windows as well as the Game Controller applet. Any ideas how to get it back? I'm particularly concerned with games that instead of showing Xbox buttons use 'Button 20' and other nonsense, but most of all, some games just don't accept the controller as input at all. I've tried several options that used to work and both wireless and wired- the controller will only show up in the control panel (and 90% of the games I play) as 'Wireless Controller'. I uninstalled InputMapper and reinstalled DS4Windows and now for the life of me I can't figure out how to make the controller show up as 'Xbox 360 Controller' in the control panel. I'm in a bit of a bind here folks, I gave InputMapper a go for a few days and I wasn't very happy with it, it kept dropping the wireless connection and constantly whined about latency, whereas I've never had that problem with DS4Windows.

I'm pretty sure a driver cleaner of some sort would do you some good if you don't want to perform all these steps- I'm staying away from InputMapper as it seems it goofs around with a lot of stuff in the OS that does not get cleaned up after uninstall. I restarted the PC, and reinstalled the latest version of DS4Windows, did the 'Step 1' driver install again, and now the controller is back as a Xbox 360 for Windows controller and works in Salt and Sanctuary. I unpaired and deleted the 'Wireless Controller' drivers as well, and made sure no remnants of the controller were in both Bluetooth environments and Services. I did the same with DS4Windows which messes with the OS considerably less. EDIT: Don't mess with Regedit if you don't know what you're doing! I found all of InputMapper's entries in my appdata and documents folders, as well as ran through regedit and deleted everything I could find regarding InputMapper and any search phrase I could think of. I solved the problem I was having and I believe it had to do with orphaned files left behind by InputMapper. (Update- Solved my problem, original post below)

Xbox 360 controller driver windows 10 hde