Hello. I recently bought a Xbox One Wireless controller with the PC wireless adapter. The problem is... after I logon into Windows 10 the controller connects fine ONE TIME, then, after turning it off and then turning it on again, the controller connects (light stay still) for about 1 or 2 seconds and then the controller turns off again, I even can use it in those 1 or 2 seconds, showing that it successfully connected, but then it disconnects. The problem is only solved after I logoff and login again into Windows (don't need to do a full reboot). My wired Xbox 360 controller works like a charm. Why do the next gen controller of Microsoft doesn't work well with a system developed by the same company? When I google it, it's problems all around. And judging by the behavior, it's a driver problem, not hardware, cause if it was a defective unit a simple logoff-login wouldn't fix it (and lots of other people wouldn't have similar problems). Thanks in advance. EDIT : link to the same post on the Feedback Hub: https://aka.ms/Phrwta so anyone passing by can easily enter and give a vote to the problem. Thanks!

Xbox One Wireless controller keeps disconnecting

Anonymous

Ok I was having the disconnect problem with the xbox one x controller on the pc - What worked for me was in device manager I chose to show hidden devices and I saw that i had an xbox 360 wireless adaptor installed even though it was not connected, I uninstalled it and now my xbox one x controller and adaptor work fine and dont disconnect or need any kind of logoff or restart.

Hope this helps

0 comments

Anonymous

OK, I have an actual solution for this.

Go into your GeForce Experience options menu, in-game overlay settings, and disable Stream (Experimental).

You can verify that this has worked by turning on your controller with Steam running, putting your computer into Sleep mode, turning it back on, and powering your controller back on.

0 comments

Anonymous

This was it for me. Turned off the beta and now my controller works perfectly! Thank you!

0 comments

Anonymous

Ok, guys... As Patrick Oberli stated before (thanks, Patrick!), now I think we really isolated the culprit.

Actually the problem surfaced two times for me, even after the latest updates and all.

And what made it work again (without the need to logoff/login) was to CLOSE STEAM. Yep, it seems Steam is the great evil boss here. :P

So, please, try this within your systems and tell me how it goes. After closing Steam you could turn on the controller again and the bug should've went away (even launching steam again, turning the controller off and on most of times seems to work, you should need to close it only sometimes).

"Recently" Steam launched a new functionality that takes over the xbox controller anywhere in the OS. You could even control the mouse cursor with it (if properly enabled in the Big Picture mode), and probably this is the main problem and what is causing this bug, even when the functionality is disabled.

Please, give us your feedback so we could make sure the culprit really and finally is Steam and other people could come here and try this temporary fix as well.

Edit: I was thinking here... if it still doesn't work, maybe it's a combination of the new Creator's update and closing Steam. Worth a try, if you ask me...

Its not isolated Steam issue, this problem happens whenever ANY PROGRAM\GAME polls xinput API at the time of xbox one controller entering sleep mode, after that It ca not connect to wireless controller while ANY program THAT CALLS XINPUT API actively is running, so the only way to re-connected Is to quit any Xinput calling program, be it steam of game... hovever if that would happen mid-game with rare saves you are screwed, as you would not be able to reconnect xbox one controller until you quit the game.

For some reason driver 1.0.46.1 fixed issue for me for several month that's to settings of selective suspend... but yesterday it started to happen again, I deleted driver, but now Windows update does not download this driver anymore and download very old driver from 2015 year, I found out on windows catalog that new driver is present http://www.catalog.update.microsoft.com/Search.aspx?q=xbox+adapter but for some reason it has different hardware id than what I have on my wireless receiver, and I'm pretty sure driver for my revision of receiver was present but now removed from windows update catalog (seems like MS trying to outdate old recievers to push sales of new smaller models, seems like anti-monopoly commission need to hear that and make MS pay for that), driver that was present had this in INF

;-------------------------------------------------------------------------

; Supported devices

;-------------------------------------------------------------------------

[Microsoft.NTx86.6.2]

; DisplayName Section DeviceID

; ----------- ------- --------

%GenericVHT.DeviceDesc% = MTWLAN.ndi, USB\VID_045E&PID_02E6

[Microsoft.NTAMD64.6.2]

; DisplayName Section DeviceID

; ----------- ------- --------

%GenericVHT.DeviceDesc% = MTWLAN.ndi, USB\VID_045E&PID_02E6

Now new 1.0.46.1 drivers has this instead

;-------------------------------------------------------------------------

; Supported devices

;-------------------------------------------------------------------------

[Microsoft.NTx86.6.2]

; DisplayName Section DeviceID

; ----------- ------- --------

%GenericVHT.DeviceDesc% = MTWLAN.ndi, USB\VID_045E&PID_02FE

[Microsoft.NTAMD64.6.2]

; DisplayName Section DeviceID

; ----------- ------- --------

%GenericVHT.DeviceDesc% = MTWLAN.ndi, USB\VID_045E&PID_02FE

Instead of E6 they have no FE, more than this, a bit older versions there have even more different hardware ids, and one driver just have one id supported instead of full range of ids of all released models:

For example 1.0.45.0 and 1.0.45.1 has this:

;-------------------------------------------------------------------------

; Supported devices

;-------------------------------------------------------------------------

[Microsoft.NTx86.6.2]

; DisplayName Section DeviceID

; ----------- ------- --------

%GenericVHT.DeviceDesc% = MTWLAN.ndi, USB\VID_045E&PID_02F9

[Microsoft.NTAMD64.6.2]

; DisplayName Section DeviceID

; ----------- ------- --------

%GenericVHT.DeviceDesc% = MTWLAN.ndi, USB\VID_045E&PID_02F9

While 1.0.45.4 has this

;-------------------------------------------------------------------------

; Supported devices

;-------------------------------------------------------------------------

[Microsoft.NTx86.6.2]

; DisplayName Section DeviceID

; ----------- ------- --------

%GenericVHT.DeviceDesc% = MTWLAN.ndi, USB\VID_045E&PID_091E

[Microsoft.NTAMD64.6.2]

; DisplayName Section DeviceID

; ----------- ------- --------

%GenericVHT.DeviceDesc% = MTWLAN.ndi, USB\VID_045E&PID_091E

Also I noticed that names of INI has different letter suffix

RL, BR, CL

I tried to install all of these drivers for my wireless receiver but non worked, gladly somone made a backup for original model driver before it was removed from windows update catalog:

https://yadi.sk/d/\_7qphV0b3MYXZp

try it and see if that can fix disconnect issue for you (it fixed for me for about 6 month, but now I'm again suffering from this issue even with this driver).

So we have also another connected issue - instead of providing one unified driver for all hardware ids MS provides recent driver only for recent revision of receiver and while initially drivers was present for old models, Microsoft removed them on purpose from windows update and only allows a driver from 2015 year to be installed while 2017 is still present for newer models.

We have like 4 models here:

USB\VID_045E&PID_02E6

USB\VID_045E&PID_02F9USB\VID_045E&PID_02FE

USB\VID_045E&PID_091E

while inf files on windows catalog only support 1 for different version.

Also I don't know why 1.0.46.1 stopped working properly again, but I do know that issue will not be fixed in 1 month, I will sue the **** out of MS for not fixing faulty product like 2 years since Anniversary update that caused this issue.

if you want to join class action - let me know. Maybe fear of class action will finally make MS do a one unified updated driver for all models of receiver and fix driver or wnidows 10 system bug in driver or cumulative system update (not in new version of widnows - do you hear me MS? I don't want to wait for next windows version that will fix 1 thing and will ruin 10 more, like usual). Oh and I will sue MS if driver or firmware issue that causing sound cracking in headset (that present like 3 years) will not be fixed as well. I'm tired of MS doing nothing to fix their mess. If you tired too - join class action.

0 comments

Anonymous

I was never logged into steam in the first place.

0 comments

Xbox One Wireless controller keeps disconnecting

98 answers