need help for a Microsoft Xbox 360 controller for WINDOWS it is the one made for Win

[BirdDad]

I just bought this from Amazon and am trying to get it to work on my HTPC which is Intel Sandy Bridge 6 core not the black edition and not OCed. It is a X97 chipset and I am running the gamepad from an integrated USB2.0 port.
The game pad is made for Windows. I am running Windows 8.1 and do not see the driver I need(they have one for Windows 7 but not 8.1).
Is there anyway I can get this to work on 8.1?
I contacted Microsoft tech support and they kept transferring me around telling me that this department cannot support this, always transfering me to XBOX support where I needed to be registered to get support but there is no registration in the box!
Thank you.

 

[BirdDad]

no one? I was hoping not to send them back but if no one can help me than I have little choice.

 

[nsafreak]

The driver for 7 should work just fine for 8.1, very little has changed between the two in terms of drivers and generally a driver for one will work for the other.

 

[McGraw]

I just bought this from Amazon and am trying to get it to work on my HTPC which is Intel Sandy Bridge 6 core not the black edition and not OCed. It is a X97 chipset and I am running the gamepad from an integrated USB2.0 port.
The game pad is made for Windows. I am running Windows 8.1 and do not see the driver I need(they have one for Windows 7 but not 8.1).
Is there anyway I can get this to work on 8.1?
I contacted Microsoft tech support and they kept transferring me around telling me that this department cannot support this, always transfering me to XBOX support where I needed to be registered to get support but there is no registration in the box!
Thank you.

I found the wireless receiver driver for my 360 receiver at the very bottom of the list that comes up when you choose to install the driver from a list of devices (ie. not from Windows update and not from "Have Disk").

It should be round there but definitely built into Windows 8.1 but not in the same place as the Win 7 driver I believe.

 

[ControlD]

In Windows 8.1 I didn't need to look for a driver at all to use my X360 controller, the driver is already baked into the OS.

What I DID find however is that if I have any other device connected to my computer that registers as a gaming controller, the X360 pad will not be properly recognized until I disconnect whatever that other device is. It is an annoying issue, but anytime I want to use my X360 controller I have to make sure to disconnect my Tartarus controller first. I spent a lot of time trying to get the controller to work the first time before I came upon that solution.

 

[BirdDad]

I am returning them neither worked when installing the driver manually.
I just couldn't get them to work.

 

[SMOGZINN]

I am returning them neither worked when installing the driver manually.
I just couldn't get them to work.

Odds are you got a knock off that is not actually an official Microsoft product. The knock offs are known for having some problems, the most serious being that they won't work if you have any other USB device plugged in at the same time. These knock offs are often marketed as XBOX controllers and sold by a company calling themselves XBOX360.

This is a real Xbox 360 controller for PC

 

[McGraw]

Ignore.

 

[ControlD]

Odds are you got a knock off that is not actually an official Microsoft product. The knock offs are known for having some problems, the most serious being that they won't work if you have any other USB device plugged in at the same time. These knock offs are often marketed as XBOX controllers and sold by a company calling themselves XBOX360.

This is a real Xbox 360 controller for PC

Hmm.

I have that EXACT issue and I have to believe my controller is an authentic X360 controller. Either that or it was the best fake I have ever seen. Came with a Microsoft driver CD, MS branded box and warranty card, etc. Whatever the case, if I have another device plugged in that registers as a game controller my X360 pad simply will not work. I always assumed it was some type of DirectX problem.