Xbox One Controller Disconnects Anniversary Update new info

[Mock]

Hi

I used a lot of time investigating this issue many have about the controller suddenly won't connect. The issues comes by the controller is working for a long time playing games, but if the controller lose battery or idle so it turns off the controller has the problem. it will now only turn on for a short while, and turn itself off again.

there is many theories about this and lots of misleading info on the internet. Google is not your friend on this issue i can tell. just to mention some of the why people think solves the problem

-Everything is something to do with Anniversary Update! Is it really Microsoft fault?
-Reinstall Windows
-Download an old driver from microsoft update. (this is the worst to do, and breaks windows. maybe this has worked earlier before anniversary)
-Get a new controller or dongle (this has been something Microsoft recommends, but don't solves anything)
-ohhh and then again, radio interference that always comes up when working with wireless (many forums mention to get rid of cellphones, routers, microwaves. There is so much BS from people not knowing what they talk about
-Turn of powersave from the driver (i think this must be a pure guess from people, because it doesn't do any difference at all)

here is some of the things to identify if you have the same issue

-Device manager should have Network Adapter/Xbox One Wireless Adapter + Human Interface Devices/ Microsoft Wireless Controller (only when turned off, else show hidden devices)
-xinputhid.sys needs to be 43520 bytes that is the newest
-When the issue appears, see if a reboot solves it. It should, but only until you idle or remove batteries

i think steam is a big player in this issue.

Try this.

from within Steam, have the controller connected and working. than take a battery out so it turns off, or idle the controller for 10 min. now the issue should appear if you put the battery back and turn on the controller, it quick turns on and off again, and works in short period of time.

from device manager on events from the wireless controller there is an error about migration failed. but doesn't lead to any information.

But if you now exit Steam and turn on the controller, it should work normal again.

so far so good. I think there can be other things to this issue. no many will think it's a Steam+Microsoft Issue, but trying to exit Steam and slowly kill many of the Windows task and see if it reproduces, by doing what i earlier described. Its possible to get Steam working and the controller working after idle.

What i think is the problem here, is many applications use Xinput and maybe conflict, it could be the driver or controller that sends a signal that its turned off to one application but the other don't have that info. and then loops when trying to turn on the controller again, this is just a guess

For me. I found Nvidia Experience that i know using a lot of modified Xinput for streaming and coop. after uninstalling this. everything worked normal again. let me hear if it helps other, or maybe there could be other application that conflicts.

[|Olly|]

Wow.

I was just about to create a new thread about this problem when I read this, and you are right, exiting Steam allowed my to turn on my controller again, and after uninstalling Geforce Experience I could turn on my controller even with Steam running. For the record, I will paste my description of my problem and troubleshooting that I was about to post in a new thread:

I know this is a problem many people have experienced, however none of the solutions in other threads have worked for me. My situation is this:

If I restart my PC, everything works fine, my controllers connects wirelessly without any issues and stay connected for as long as I need. The problem starts after I put my computer to sleep and wake it again, now my controller won't turn on, it just blinks a couple of times and then shuts off. For the record, the problem doesn't only start after waking the computer from sleep, it also happens if I just unplug my xbox wireless adapter and replug it, no matter if I plug it in the same port or a different one. Connecting my controller to the PC with a USB cable always work.

I have tried the following:

• As many threads have suggested, I have tried installing an older driver version downloaded from http://catalog.update.microsoft.com/. In fact, I tried 3 different versions, all ended in the same result as described above.
  
• Verified that it's not a battery problem by using both official Xbox play and charge recharable battery packs, 3rd party battery packs and regular AA batteries.
  
• Verified that it's not a controller problem, I have 3 controllers, all display the same behavior (They all work perfectly fine when connected wirelessly to my Xbox One)
  
• Further verified that it's not a controller problem by updating them to the latest firmware, one was updated via Xbox One, the other two via the Xbox Accessories app for Windows.
  
• I have plugged my wireless adapter in various USB ports, I've tried the USB 3.0 and 2.0 ports on the front of my case, as well as 3.0 and 2.0 ports on the back of my motherboard.
  
• I've tried to uncheck "Allow the computer to turn off this device to save power" under Power Management on the wireless adapter properties.

[Mock]

One of my friend that asked me about this problem called Microsoft at first, they said it was a faulty wireless dongle so they just send him a new right away. but the problem is still software related, but its crazy how much wrong information the internet has about this issue.

[Ryuzaki Koizumi]

Thank you. You helped me greatly on fixing, as I had the same problem.

Upon further investigation, I narrowed down that the service named "NVIDIA Wireless Controller Service" was causing the problems. I had it disabled for awhile, played some games, no random disconnects. Also turning it off, and back on, no auto off problems. Once I re-enabled, problems re-appeared again. Once I killed Steam and GeForce Experience and disabled the service again, the controller works as intended....

[Mule]

Sell that dusty bucket of bolts, and buy some ram. ;)

[graywoodford]

Hello
Just to update the thread, I have had exactly the same issues for a while and thought it was a hardware issue so I have replaced my wireless adaptor and my elite controller and I am still getting the same issue.

Controller connects fine the first time afetr boot but after idle or turn off it would not connect again, just flash for a second as if connected then nothing.

After testing and reading thsi thread it only happens for me when steam is launched, if i close steam pad is fine for re-connects, steam open and no chance.

So after reading here i uninstalled the geforce experience (i was on the latest version) restarted my pc and tested. All fine and working now, even when steam is open, working as it used too.

So it looks like geforce experience was the problem after all.

[bobabrowncoat]

I'm still having this exact same issue. Has anyone found a solution besides closing Steam?

[graywoodford]

Hi Mate

I did for mine in the end.
I had to uninstall nvidia geforce experience and the issue was gone so i removed my driver too and then did a fresh clean install of them both and everything was fine.

Do you have an Nvidia graphics card?

If you need any help just update this thread

Gray

[bobabrowncoat]

It seems to be working now without me changing anything. I wonder if there was a Windows 10 automatic update that fixed the issue.

[KontryBoy706]

OMG... I've been having this issue for months. I have had no idea what to do and like you said GOOGLE IS NOT YOUR FRIEND when searching for this issue. However with dilligence of finding an answer to this... I have to admitt it was GOOGLE that led me to your post. For months I have been frustrated not knowing what the hell the problem could be. I have tried everything outside of reinstalling windows because I'm not just abou to do that. But thankfully I ran into this thread.

I KNEW there had to be a problem with Steam but I didn't know it was also related to GeForce Expierence. See last week when we had that last beta update to Steam my Steam client would not start at all. It would hang when trying to open and I had to force quit. I wrote Steam on Twitter and got no response. I tried lots of things and I got to the point where I was going to uninstall Steam. BUT I tried one more thing.... I unplugged the controller... and Steam started right up. I couldn't believe it. Plugged it back in and shut down steam and Steam would NOT restart until I unplugged the controller. So... there's definitely some bugs between Steam, the controller and NOW GeForce Experience. But at least now I know to just shut Steam down when I need to restart the controller but there needs to be a solid fix.

[KontryBoy706]

DID SOME FURTHER DIGGING AROUND THE NVIDIA SITE AND SAW THIS POST FROM RIZAKIKIZUMI


Sup. I noticed as of late my Xbox One controller would power down as soon as I turned it on, regardless if my battery was full. I use the wireless dongle, btw. Since GFE 3 I noticed this happening, and after endless searching I discovered to get my controller working again I had to close both Steam and GFE. After that I tried my controller again and it stayed on. Digging further into the issue, I discovered I can turn off the wireless controller service, and still use my controller while GFE was running. If it was on, I'd be back to square one.
Now after the 375.70 driver update, the install reset the wireless controller service, made it start with Windows again, and my controller would act up again. So as of now I uninstalled GFE because of this issue.
If you experience something similar, post here. As for a workaround, go to services.msc, find NVIDIA Wireless Controller service, stop it, and set Startup type to Disabled.
And for NVIDIA themselves, fix this. Seriously.... breaking controllers now?

[graywoodford]

Hello, have you tried doing a fresh re-install of your nvidia drivers (click the clean installation option during install too) after uninstalling your current ones.

This solved the issue for me, i think mine got the issue after updating my drivers so much but after clean install all was working fine. Try it.

When I had ths issue I found it was to do with the nvidia controller service as this is for the nvidia shield tablet streaming when connected.

Im glad you found this post, I had the issue for months intil i found it and investigated too

[godota2.com/dota2vipgame.com]

Originally posted by Rizaki Koizumi:

Thank you. You helped me greatly on fixing, as I had the same problem.

Upon further investigation, I narrowed down that the service named "NVIDIA Wireless Controller Service" was causing the problems. I had it disabled for awhile, played some games, no random disconnects. Also turning it off, and back on, no auto off problems. Once I re-enabled, problems re-appeared again. Once I killed Steam and GeForce Experience and disabled the service again, the controller works as intended....

[DT]

Yep. It was the "Nvidia Wireless Controller service". Disabled it and now it's all good.

F'kin hell nVidia...

[Mock]

One of my friends said that he had GFE and steam installed, where it works, after the newest updates, but havn't confirmed it myself. I think im better of without GFE after all that trouble

[Son W]

in the beta update of geforce experience 3.2.2.49, it remove the Nvidia Wireless Controller Services.


THE ISSUE COMES BACK!!

I quit the steam and it restores normal.