Share via

Xbox One Controller not connecting via Bluetooth after being plugged in with USB

Anonymous
2019-09-20T00:45:11+00:00

I have a Xbox One Wireless Controller without the PC adapter so I use Bluetooth to connect directly to my PC.  After charging the controller through one of my PC's USB ports while the PC is on, once the USB to the controller is disconnected it can no longer connect via Bluetooth.  It will still work while the USB is connected but won't work via bluetooth.

Trying to un-pair the controller or uninstall it through devices or device manager often doesn't uninstall.  The most successful method of getting it to work again is to un-pair in the Bluetooth devices and uninstall in both the devices and printers and device manger, then restarting the PC and attempting to pair via Bluetooth again.  This works most of the time but occasionally won't work.

I assume this problem is related to Windows or driver as the device still works perfectly when it is connected via USB. It is like it is flipping a switch to say that it is USB only when it detects the USB connection.

A solution to this problem would be appreciated as I only have 1 USB cable long enough to reach my gaming position and if my headset goes flat while my controller is charging, I have to spend 20+ minutes trying to get the controller to work again via Bluetooth.

Thanks.

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

  1. Anonymous
    2020-05-16T21:29:34+00:00

    Hi everyone,

    Improved Solution:

    1. Settings > Devices > Bluetooth & Other Devices

    Find Xbox Wireless Controller and Remove Device.

    1. Windows Search > Device Manager > View > Show Hidden Devices

    Find "Human Interface Devices" and uninstall HID-compliant game controller.

    *Important to "Show hidden" or you won't find it as the device is disconnected*

    1. Go through the normal pairing process. *Turn on Bluetooth*

    Settings > Devices > Bluetooth & Other Devices > "Add Bluetooth or other device" > Bluetooth.   Don't use "Everything else" even though it says Xbox controllers.

    1. Turn on your Xbox controller and press the sync button. You should now be able to pair AND connect to your computer.

    I really hope this was the main and only issue. If it isn't, go into my last post for the clean slateidea. Upvote if this worked!

    100+ people found this answer helpful.
    0 comments No comments

Answer accepted by question author

  1. Anonymous
    2020-01-04T13:05:04+00:00

    I had a similar problem (although I could repair controller without PC restart)

    I found a workaround:

    1. Connect controller via USB
    2. Go to win+X -> device manager and disable (not delete) Xbox one controller here
    3. After that repair controller via Bluetooth

    Thus when you connect controller via USB it will only charge but will not connect as a device - and Bluetooth connection will remain connected

    I have win 10 1909

    50+ people found this answer helpful.
    0 comments No comments

115 additional answers

Sort by: Most helpful
  1. Anonymous
    2019-09-20T13:35:11+00:00

    Do you guys actually read the posts and the suggestions that you provide?  I stated almost everything that is in that link in my original post, including the steps that make it work again.

    The problem is that I have to do it every time that I need to plug the controller in via USB while the PC is on.  There is obviously a problem with the way that Windows controls the device, it disables the Bluetooth connection and doesn't re-enable it once it is unplugged from USB.

    I am looking for a way to not have to spend 20 minutes troubleshooting this every time I need to charge it.

    10+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2019-11-16T01:24:11+00:00

    This is exactly what is happening to me as well. It's pretty dumb that this was seemingly completely missed, or ignored... I just spent $30 on the official MS battery pack and now you're basically telling me I can't charge it without having to re-pair my controller every time. That's completely unacceptable.

    10+ people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2019-09-24T00:46:50+00:00

    I have this exact same problem and, as of yet, I haven't found a solution for it. Pairing my XBox One controller works fine and everything is smooth. The moment that it's plugged into a machine to act as a wired controller is seems to forget that it was ever wireless in the first place. My son will often use my controller with the cable on his machine and when I try to reconnect it to my machine, even though it was never paired to his, it won't connect. The same thing will happen if I connect it to my machine and then unplug it and try to go back to Bluetooth. It just won't connect. 

    What I end up having to do is go to setting -> devices and tell it to forget the controller. I then re-pair the controller and everything works as it should. I already know that when I get the controller back from my son that I'm going to have to do this (though every time I try to link it first even as I'm opening settings just out of blind foolish optimism and hope). When I have to charge it while I'm still playing I have a spare USB brick that came with an old phone that I plug the controller into and then into a wall outlet. This doesn't seem to have any effect on the function of the controller. If you search around the net you'll find that this is an old and known issue with these controller and so far I haven't found any explanation for it. It has nothing to do with your hardware or BIOS or the Windows version since it was doing this to me on 1709 and is still doing the same thing on 1903. It seems that the Bluetooth implementation for these controllers is just a little wonky.

    10 people found this answer helpful.
    0 comments No comments