Windows Update & Xbox One Gamepad driver issue

[buddymanson]

So if I install the last two Windows Updates, my mouse will eventually start behaving odd and I get strange beeps. This happens when I use my Xbox One wireless dongle(turn on controller unplugged).

Removing and hiding these updates resolves the issue(I use a tool from Microsoft).

So either we need a new Xbox driver or Windows needs to fix their ♥♥♥♥.

Win 10
970 GTX
4690K
DV 362.00

[WarmedxMints]

Yes it's an xinput isssue. It only happens for most when the wireless controller turns off after being idle for 10 mins. So a solution for now is to plug in a usb cable when not using it or use it all the time with the cable.

[Blue Palmetto]

Not to revel in other's misery, but thank goodness! I literally just built my first PC and started experiencing this error. I thought I'd missed something.

[Bad 💀 Motha]

Just uninstall that Windows Updates; simple and fixed the issues.

[buddymanson]

引用自 Aleister Crowley：

It's not the XBox driver, it's XInput HID driver. Unfortunately they have greyed out the option for driver roll back along with this broken update, too.

Ah ok.

Are you referring to Windows Update? Removing the last broken update is simple. Uninstall it and hide it with this tool - https://support.microsoft.com/en-us/kb/3073930

[da_legit_dubya]

Win10. Been playing original Skyrim for a number of years now, using an XBox One pad. The only issue I had up until the recent "update" was that on fairly rare occasions the game would fail to detect the pad. Most of the time I could just unplug/replug the cord to the pad, sometimes it would work, sometimes not. But recently the left stick started pulling to the left... but testing with other games through emulation (e.g. DOSBox) it doesn't seem to happen.
Oddly enough, I switched out to my 360 pad and it works just fine. The downside it that the failure occurs more often because of a port issue: the pad/cord connection isn't as tight as it should be, and has been since the day I bought it. I guess Gamestop/Walmart had been working on phasing out 360 peripherals, So I was lucky to get the 360 pad when I did.
It's the MacroSloth fcukups like this that make me feel more and more that it's time to return to Linux.

[_I_]

its steams controller config
steam -> settings -> controller -> [general] -> select controller -> properties
increase the deadzone for the controllers joystick inputs

[Bad 💀 Motha]

引用自 da_legit_dubya：

Win10. Been playing original Skyrim for a number of years now, using an XBox One pad. The only issue I had up until the recent "update" was that on fairly rare occasions the game would fail to detect the pad. Most of the time I could just unplug/replug the cord to the pad, sometimes it would work, sometimes not. But recently the left stick started pulling to the left... but testing with other games through emulation (e.g. DOSBox) it doesn't seem to happen.
Oddly enough, I switched out to my 360 pad and it works just fine. The downside it that the failure occurs more often because of a port issue: the pad/cord connection isn't as tight as it should be, and has been since the day I bought it. I guess Gamestop/Walmart had been working on phasing out 360 peripherals, So I was lucky to get the 360 pad when I did.
It's the MacroSloth fcukups like this that make me feel more and more that it's time to return to Linux.

If that truly is the case, simply uninstall the update in question.

You state it was a recent update, but which one exactly?

Folks should not be installing new updates when they release for Win10. Instead just pause updates for 28 days. After that period if said update is still available and not been pulled, re-released, etc. Then it should be an OK update to then apply.

It is however, always possible that a WinOS Kernel related update might mess with certain hardware and the way to address this usually is to either reinstall the driver of the affected hardware, or go download and install the latest driver version, if one exists.