I'll give it a shot tomorrow, thanks!Have you tried rolling the controller driver back to the previous? Someone suggested it above and if mine weren't working right now, I'd totally try it.
Did you manually download the controller drivers? Windows 10 has them by default (might need to run Windows Update).I just did a completely fresh install of Windows 10 Anniversary Update from media, with nothing installed but graphics drivers, the Xbox One controller drivers, and Steam to test this out. I can confirm I am getting double input in Steam Big Picture and Dragon's Dogma with the controller whether wired or wirelessly (which is an original revision of the controller with latest firmware via Xbox Accessories app).
Edit: Hopefully Microsoft does something about this faulty driver situation...
Did you manually download the controller drivers? Windows 10 has them by default (might need to run Windows Update).
I ask because my Xbox One Elite controller is fine with a clean Windows 10 install. I didn't manually install anything but the Nvidia drivers.
I did not manually install anything except my graphics drivers.
YES! this fixed it for me
If you have an elite and are connecting wireless, there is no xinput device at first
you have to plug in the usb cable to your controller, then it will show up, then you can do this. after that, everything is working again for me
Issue solved! The new "xinputhid.sys" driver doesn't work properly - use old version! https://www.youtube.com/watch?v=ZlvLftCqvSo Where is the QA, Microsoft? Fix it!
Someone suggested this is only with the newer revision, with the headset jack. Not sure how true that is.
This fixed it for me. I also blocked Windows from installing driver updates from Windows UpdateSame problems here, but that video got my bluetooth controller working. You can grab the drivers they mention directly from Microsoft here: http://catalog.update.microsoft.com/v7/site/Search.aspx?q=xbox+wireless
You need the Microsoft - Generic Controller - Xbox Wireless Adapter for Windows driver version 6.3.9600.16384. One package is X86 and the other AMD64. Click on the title to see which is which. The xinputhid.sys and xinputhid.inf files are in there. It says they're for Windows 7 and 8.1, but they'll work just fine.
I'm confused, when rolling back the driver, where are you browsing to to locate the old version? There is a Rollback Driver option in Windows already but it's greyed out. I'm guessing the old driver was removed by the update.
I attempted to take that fix a step further to try to get it to work over Bluetooth. I messed with my permissions until I was able to replace xinputhid.sys under System32 with a previous version of that driver. That way, all devices (whether usb or Bluetooth) that utilize that driver would be using the rolled-back version. It half worked. Steam was no longer registering double inputs, but none of the buttons on the controller were working properly in Steam Big Picture (and games, I assume). The left stick was functional, but everything else was screwed.
I'm glad the fix works for you USB folks, but I'm out of ideas for xinput over Bluetooth.
Same problems here, but that video got my bluetooth controller working. You can grab the drivers they mention directly from Microsoft here: http://catalog.update.microsoft.com/v7/site/Search.aspx?q=xbox+wireless
You need the Microsoft - Generic Controller - Xbox Wireless Adapter for Windows driver version 6.3.9600.16384. One package is X86 and the other AMD64. Click on the title to see which is which. The xinputhid.sys and xinputhid.inf files are in there. It says they're for Windows 7 and 8.1, but they'll work just fine.
i'm not using USB, im using the wireless dongle. i just hooked it up via usb to update the xinput driver, then unplugged the cable, and everything works again
maybe try that and see if it fixes bluetooth?
I am under the impression that steam simply needs an update that will talk proper with the win 10 AU? Surely thats all thats needed
Same problems here, but that video got my bluetooth controller working. You can grab the drivers they mention directly from Microsoft here: http://catalog.update.microsoft.com/v7/site/Search.aspx?q=xbox+wireless
You need the Microsoft - Generic Controller - Xbox Wireless Adapter for Windows driver version 6.3.9600.16384. One package is X86 and the other AMD64. Click on the title to see which is which. The xinputhid.sys and xinputhid.inf files are in there. It says they're for Windows 7 and 8.1, but they'll work just fine.
That is odd. When I auto-updated the new driver, it just put the broken one back on and things stopped working again.My controller is also fixed after watching the video, and using the link for the old drivers. Also, I ran the auto update which re-applied the new 10.0.14393.0 (Dated 7.15.16) driver, and it still works. Which is weird, but my controller works now so I'm happy.
Working
- Launch XB1 Controller (Wired & Wireless Adapter)
- 3.5mm XB1 Controller (Wired & Wireless Adapter)
- Lunar White 3.5mm XB1 Controller (Wired & Wireless Adapter)
This works for you over Bluetooth? Which device did you switch the drivers for? Under device manager in HID devices, I have a disabled XInput device, and an enabled Bluetooth Compatible Xinput Device. I wasnt able to replace the drivers for the Bluetooth Compatible Xinput device. Can you give more specific instructions?
Someone suggested this is only with the newer revision, with the headset jack. Not sure how true that is.
Yeah, this is weird. Going back to the old driver and then updating again to the most recent, and everything now works fine.So earlier in this thread I said I didn't have any problems, but later on I delved deeper and found out I did. This is how I fixed my problems. This fixed the Steam BPM double controller and double input issue for me, but fixed the problems I was having with FFXIII as well.
First I went to Human Interface Devices in the Device Manager, next I went into the properties of my Xbox Controller. I have the newest Xbox One Controller with Bluetooth, but I use the wireless adapter with it. It has the newest firmware as well. For some reason it's labeled Xbox Wireless Controller instead of Xbox One Wireless Controller.
Anyway, I clicked the Events Tab and noticed something strange while checking out the Device Configured option. It said Device Updated: false
So next I decided to downgrade to the previous driver, so I went to the Driver tab and clicked the update driver button. I selected the Browse my computer for driver software option, then selected Let me pick from a list of drivers on my computer. Then I selected the driver highlighted below.
If your controller turns off before this point, a long list of hardware types may show up. Just turn on your controller again and restart the process.
Anyway the controller was downgraded and it worked again in BPM but I was still having problems with FFXIII. So I decided to upgrade the driver to the newest version and this time I noticed under Events that Device Updated was true now.
I tried BPM again and I wasn't getting double inputs or double controller issue anymore and I tried FFXIII and that was working too. So after all of that it seems that my problems have been fixed. You guys should give a shot and see if it works for you.
That's because the old driver has issues with a lot of Unity games.I rolled back the driver, but some things still seem weird. Trying to play Tricky Towers and the dpad seems borked.
So frustrating. I hope MS do something soon. $200 (AUD) for a fancy controller + $30 for the dongle and it feels like I'm using some third party hack now. I really expect better MS.
snip
Oh, this is unfortunate.EDIT: Scratch that, I rebooted and problems came back. Need to use the older driver.
Is there a way to check the battery life of a wireless XB1 controller within Windows? I can't believe such a simple feature can't be found anywhere.
Of course yours works. I'm sure you've never had any issues with any MS product.Love that title... for me everything works perfectly and i tried the Xbox One controller on both my Surface Pro 4 and gaming desktop PC, both with Win10 annyversary update...with such a big update could happen that a minority will get some issues
It's odd that it only has a problem with some games. In my case Dragon's Dogma Dark Arisen is the only game with issues but it's enough of a problem that the game is completely unplayable.
I think from the OS's perspective, the wireless dongle is the same as USB, since signals are received from the dongle's usb port. I believe I can fix it for USB or USB Dongle, but it seems different for Bluetooth. It's a different device in Device Manager when using it over Bluetooth.