[RESOLVED] XBOX One Wireless Controller Adapter (Windows 7) Issues and Problems

[xtenthousandnightsx]

I've probably searched forums and how-to guides for about 12-18 hours total over the last week, pulling my hair out trying to solve this. I've tried everything from uninstalling drivers (which were rejected at first because auto-update won't accept the drivers because they aren't digitally-signed) which brought me to the "bcdedit" method, which ended up doing nothing for me. Downloaded the drivers from the Windows Update Catalog - no good.

The Adapter itself installed just fine, it's in my devices as "XBOX ACC" and in Device Manager as "Xbox Wireless Adapter for Windows"

The Adapter is actually capable of pairing with the controller just fine, but it's not usable in any form. It simply connects and is recognized as "Unknown Device" under Human Device Interfaces in Device Manager. When I click on the "Unknown Device" it looks like it's recognized as the controller somewhat, but obviously something is missing here, or perhaps an incorrect driver is installed. When I try to manually install the correct driver, it comes up as "XHID game controller" but then reverts back to "Unknown Device". I am unsure how to roll back whatever drivers it's digging from and remove their presence, or even registry entirely and start fresh. System Restore was a joke, it did nothing.

Windows 7 is up to date, I tried Windows Update as well.

I know I'm missing something very crucial here but I can't for the life of me figure it out and I think I may have a unique situation. It works with the micro-USB, of course, which everyone's been reporting similarly, but having already shelled out the money for the adapter and an Eneloop charge kit, I'd like to make the most of this purchase.

Update 1 (6/2/2016) :

I got the computer to recognize the controller by assigning it as "hid-compliant game controller" but it will only work with things like emulators or MUGEN. It currently does not work for any Steam game. When I try to assign it as "xinput compatible HID device" it gives me an error and says that the driver is not intended for this platform, which puzzles me because other people have had success with it on Windows 7. This is progress at least, I guess. Updating drivers has been a nightmare and it won't seem to replace the old ones when I try to reinstall, it keeps giving me the same error. Is there anything I should be doing with the registry keys for that device to remedy this?

[Perlyte]

Originally posted by Nocturnus:

I think I solved it.

The problem seems to be that the drivers are not digitally signed. Hasn't been an issue until now... but that's the way it is now, it seems.


What I did was to follow the instructions of the link Enoch Root posted above:

Originally posted by Enoch Root:

https://www.techspot.com/community/topics/how-to-install-use-unsigned-drivers-in-windows-vista-7-x64.127187/

Just follow the steps of 'Solution number 2'.

Thanks for the fast reply! Can confirm that solution 2 fixed the problem.

EDIT: Your PC has to remain in test mode for the driver to continue working. Not sure if that's a potential security risk since unwanted software could presumably use this mode to make malware look like legitimate software. I may be completely wrong about this, but unless Microsoft decides to update the driver for Win 7, which is not going to happen, there may not be another solution...

EDIT2: Definitely a very high security risk since DSEO requires UAC to be completely disabled. Running your PC in test mode allows unsigned programs to write to and modify System32 files, and will also allow any program that would normally require elevated privileges to run without. It's basically debug mode for Microsoft developers.

[Bad 💀 Motha]

Windows Updates for 7 / 8 / 10
have address major new found bugs regarding AMD CPUs.
You should redo your core hardware Drivers after this update.
MS warns your Network Adapter might be completely non-working after this update; so ensure you have your Updated Drivers ready from the chipset maker. If need be use a Phone/Tablet or another PC and download what you need for them and transfer them to troubled PC and then install them.

https://steamcommunity.com/groups/Master_Race_Geeks/discussions/0/1697176044370572540/

[JonC]

Originally posted by Nocturnus:

I think I solved it.

The problem seems to be that the drivers are not digitally signed. Hasn't been an issue until now... but that's the way it is now, it seems.


What I did was to follow the instructions of the link Enoch Root posted above:

Originally posted by Enoch Root:

https://www.techspot.com/community/topics/how-to-install-use-unsigned-drivers-in-windows-vista-7-x64.127187/

Just follow the steps of 'Solution number 2'.

ok, it works, but what to do with that "Test mode" message appeared after the reboot in the right bottom corner? I found a solution how to disable it there[support.microsoft.com], but it screwed up the Xinput driver again. Do I need to get used to that message then?

UPDATE: sorry, I just read back the thread. so it's not the best idea to keep it in test mode. then I don't know how to fix that.

UPDATE2: looks good, worth a check

[Nocturnus]

Originally posted by JonC:

UPDATE2: looks good, worth a check

I don't see this as a practical solution because you would have to spam F8 everytime while booting up... should be annoying as hell, especially the one time you forget about it...

The testing mode I suggested before is not very good either, I admit...

I think I'm going to uninstall that damned windows update that brought this mess upon us...


UPDATE:
This works.
I will stay away from this update until MS get their s**t together...

Its Security Update KB4284826, for those of you that don't want to search on their own.
And put your Win Update settings on 'download and install manually...'

[Perlyte]

Originally posted by Nocturnus:

Originally posted by JonC:

UPDATE2: looks good, worth a check

I don't see this as a practical solution because you would have to spam F8 everytime while booting up... should be annoying as hell, especially the one time you forget about it...

The testing mode I suggested before is not very good either, I admit...

I think I'm going to uninstall that damned windows update that brought this mess upon us...


UPDATE:
This works.
I will stay away from this update until MS get their s**t together...

Its Security Update KB4284826, for those of you that don't want to search on their own.
And put your Win Update settings on 'download and install manually...'

I did the same, and it's working. Since the official driver for Win 7 got removed and was made a Windows Update only feature, then deliberately broken, I have a feeling that this isn't going to be fixed at all (The certificate for the official xinput driver for DirectX expired on March 19 2016). Microsoft is desperately trying to forcibly phase out Windows 7, so I think the only solution is to wait for someone to create an unofficial xinput emulator.

[Joonas]

Hey thanks! I deleted the update and now my wireless xbox one controllers work. Maybe someone should tell microsoft that the update breaks the drivers.

[Tathendal]

THanks awesome. WTF I bet this is M$'s idea to get people to go win10...conspiracies ftw... updateKB428482 my a$$

[JonC]

works for me too if I uninstalled that update. afterwards I hid it, so it will not bother me anymore.

[Mad]

Got the same issue after the most recent W7 update so I followed the easy steps in this article and everything seems to be working fine now: https://www.reddit.com/r/windows/comments/8qyghj/latest_windows_7_update_kill_your_xbone_wireless/

[Bad 💀 Motha]

Originally posted by Nocturnus:

Originally posted by JonC:

UPDATE2: looks good, worth a check

I don't see this as a practical solution because you would have to spam F8 everytime while booting up... should be annoying as hell, especially the one time you forget about it...

The testing mode I suggested before is not very good either, I admit...

I think I'm going to uninstall that damned windows update that brought this mess upon us...


UPDATE:
This works.
I will stay away from this update until MS get their s**t together...

Its Security Update KB4284826, for those of you that don't want to search on their own.
And put your Win Update settings on 'download and install manually...'

No, once you use that Disable Signature WHQL Checking; its disabled and done.
I did this back when I reinstall Win7 back in 2015, the same system still running just fine without problems, that WHQL checker is still disabled.

[BastardSmacker]

Thanks to whoever it was that found this bad update. I spent hours on the phone with MS about this, and they acted totally oblivious about it. I uninstalled this update (kb4284826) and then had to update the driver from hdinput to xinput, but it worked. I called them back to tell them they issued a broken update, and they said they "would escalate it to their technical team". We will see. Huge thanks again to the finder of the bad update.

[skif_]

i have the same problem !!!
i can confirm unninstaling update kb4284826 FIX this problem !!! DONT FORGET TO RESTART YOUR PC AFTER DELETING THIS UPDATE

[Dosani]

Originally posted by skif_:

i have the same problem !!!
i can confirm unninstaling update kb4284826 FIX this problem !!! DONT FORGET TO RESTART YOUR PC AFTER DELETING THIS UPDATE

THANKS!!! This is the only thing that worked, really grateful to you all

[Krasius]

Hi,
I also want to uninstall this update but i can't find it in the install section. I can see it in the history update section.. I tried manually with a cmd command but it say that the update is not installed.... Any idea how to remove this or should i just delete all update and start again from 0 ?

[skif_]

Originally posted by Krasius:

Hi,
I also want to uninstall this update but i can't find it in the install section. I can see it in the history update section.. I tried manually with a cmd command but it say that the update is not installed.... Any idea how to remove this or should i just delete all update and start again from 0 ?

you should go to control panel > programs > programs and components > installed updates
right click with mouse and there will be buton delete
this update come out 11 july 2018 +- some days