Browse
Category
DiscussionsUncategorized

[SOLVED] Fix my XBOX Wireless Controller and win 3 games of your choice

Closed
DrDudePhD

I have Windows 7 x64 | Had no issues for 3 years | My XBOX Wireless Controller is original

This works:

  • Anything that supports DirectInput.
  • This includes the Windows 7 Test Device window.

This somewhat works:

  • Brutal Legend, Psychonauts, and Big Picture Mode, all of them have some kind of bug. When I press the button [B], is actually [A], when I press button [X], is actually [B], and so forth. Right analog stick doesn't work. Guide button doesn't work but it does to show me the battery status. In Big Picture mode, I can only map one trigger (either Left Trigger or Right Trigger, but not both).

This doesn't work:

I'm suspecting this is related to some kind of XInput joypad detection.

What I already did:

  • Reinstalling drivers both with Windows Update and standalone executable.
  • Reinstalling June 2010 DirectX drivers.
  • Reinstalling Steam.
  • Tested several USB ports.
  • I disabled ALL deviced in the control panel of my PC, and still got the same issue =( I thought this would be it, but no...
  • I also tried the xsys.dll from my Windows 7 on the laptop, it was different in size (probably because it's the 32 bits version), but then again, didn't work.

Update 1: Joypad works fine on my crappy laptop. Big Picture Mode had no issues, so it's my current Windows install.

Update 2: This is so annoying, if you give me a good tip that leads to fixing this issue, I'll give you 3 bundle games of a list of 10, I think.

Update 3: Solved. It could be one of a couple things:

  • I uncompressed the x64 drivers with WinRAR, then manually reinstalled the drivers directly from the extracted folder (though it's the same .dll build number).
  • I re-enabled a couple of services - Windows Driver Fundation and Windows Management Instrumentation (I'm guessing it was this last one)
  • I did as some user told me, disabled a HID, then restart, then try the buttons again.

Will do a bit of research on this, in any case, only solution 3 will win the games since 1 and 2 were my ideas.
And the user who posted that deleted his post =\

1 decade ago*

Comment has been collapsed.

79 Comments
Xana

The fact that only some buttons are recognized reminds me a lot of when Darksiders wanted me to use my n64 controller as an xbox 360 controller - very few of the inputs were recognized even though they should've been mapped to the buttons. I disabled all of my "game controller" devices in device manager and that fixed it (it let me use my keyboard for once!), but i can't tell if that's what you meant by your second to last point.

Have you updated your USB drivers? Are there any system restore points from around the time you noticed it stopped working that might give you an idea of what broke it?

1 decade ago
Permalink

Comment has been collapsed.
DrDudePhD

Well, the wireless controller is two components. The Reciever, and the Joypad. The drivers are OK, but I'm suspecting something in the middle broke, regarding xinput. I'm investigating xsys.dll which is the "Windows Common Controller" or something. Might be the issue.

Also tried disabling all other devices, no luck.

1 decade ago
Permalink

Comment has been collapsed.
Tuffdog

For some games a command in the developer console activates it for the game. May I also suggest x360ce?

1 decade ago
Permalink

Comment has been collapsed.
Shahbaz

THIS IS 2 Easy nsane..
Take a Hammer..
Find ur controller..
Hit it as Hard as u can
Break it into 100 pieces..
Then put them in a paper bag..

Go to a Shop
Buy a New Xbox controller.
hook it up to ur pc
and Enjoy ur game

U might ask.. What to do with the pieces in the paper bag.. ?

What else.. Throw them in the Garbage

1 decade ago
Permalink

Comment has been collapsed.
Shahbaz

u can also try to check ur Wireless reciver thingy

1 decade ago
Permalink

Comment has been collapsed.
DrDudePhD

It's not the hardware, khan, it works on the other PC. It isn't the xbox drivers neither, I'm guessing it's the windows driver that connects the xbox driver and windows (sort of a middleman).

1 decade ago
Permalink

Comment has been collapsed.
calimero100582

You have a DRIVER PROBLEM, no matter what you say or what you have done. There is some file or registry key that are not cleaned up even with a reinstall.

3 Solutions:

  • Try to find the problem
  • Do a fresh install of Windows
  • Get another controller
1 decade ago
Permalink

Comment has been collapsed.
DrDudePhD

well, it is a software problem, not hardware. Read about that.

But yes, there might be some registry or windows thingie that didn't get cleared or got replaced. I'm pointing towards that xsys.dll, but I think that one is shipped with windows.

1 decade ago
Permalink

Comment has been collapsed.
nonamejuju

Used ccleaner?

1 decade ago
Permalink

Comment has been collapsed.
DrDudePhD

Yes.

1 decade ago
Permalink

Comment has been collapsed.
tchoob

Maybe it's something as simple as a missing or corrupted xinput DLL? Have you checked the Windows Event Log (eventvwr) for any errors concerning XInput? I'm on the same config (Win7 64, wireless 360 controller), I can provide you with xinput1_1.dll, xinput1_2.dll, xinput1_3.dll and XInput9_1_0.dll.

1 decade ago
Permalink

Comment has been collapsed.
DrDudePhD

to be fair, I had/have Windows Event Logs disabled...
so DirectX.log was empty, too, I checked.

1 decade ago
Permalink

Comment has been collapsed.
Fynal

Did you reinstal Microsoft XNA Framework and Net Framework 4 ? In both this framework are libraries with XInput.

And did you try maybe XBCD? http://vba-m.com/forum/Thread-xbcd-0-2-7-release-info-updates-will-be-posted-here

1 decade ago
Permalink

Comment has been collapsed.
DrDudePhD

I'll try.

1 decade ago
Permalink

Comment has been collapsed.
tchoob

There's also DirectX.log in your Windows folder - if you know when your controller stopped working properly you may be able to find what happened to DirectX before that moment.

1 decade ago
Permalink

Comment has been collapsed.
darko55

is the controller connected with a quick play and charge connector? If so I know exactly whats causing the problem if not then use CCleaner to remove the registry files (and uninstall the driver) and do a fresh install. if that doesn't work I'll need the specs of your system (including OS) and the controller model to tell you whats up.

1 decade ago
Permalink

Comment has been collapsed.
DrDudePhD

nope, just a normal receiver and joypad.

1 decade ago
Permalink

Comment has been collapsed.
tchoob

Also - dxdiag, Input tab - can you see your controller there? It should be listed as Controller (XBox 360 Wireless Receiver for Windows).

1 decade ago
Permalink

Comment has been collapsed.
DrDudePhD

it was always listed with that exact name.

1 decade ago
Permalink

Comment has been collapsed.
miffmoff

Can you use a keyboard-joystick mapper like http://pinnaclegameprofiler.com/ ?

1 decade ago
Permalink

Comment has been collapsed.
Iliuthenin

open Device Manager and locate your wireless controller unit. Remove the drivers and manually install them again by using Device Manager. Worked for me when my XBOX 360 controller didn't work (after updating to win 8).

Also, make sure you have the latest drivers (microsoft.com still have the old ones as well). The new drivers are named "XBOX 360 accessories" or something like that.

1 decade ago
Permalink

Comment has been collapsed.
TheChack

So how did you fix it?
EDIT: I see.

1 decade ago
Permalink

Comment has been collapsed.
TheRealDealReece

funny, mine just started playing up too...

1 decade ago
Permalink

Comment has been collapsed.
DrDudePhD

if you need with that, hit me up.

1 decade ago
Permalink

Comment has been collapsed.
TheRealDealReece

it seems to have fixed itself for now thanks for the offer anyway.

1 decade ago
Permalink

Comment has been collapsed.
nerka99

use http://code.google.com/p/x360ce/ or something similiar :)

1 decade ago
Permalink

Comment has been collapsed.

Closed 1 decade ago by DrDudePhD.