Pls help before I lose my eish!

Does OP have a twitch channel? Would pay to see the rage quits.
 
Yes I am not sure what receiver you are using or is it a cabled controller. If it's an older USB device legacy support could help with stuff like this.

Also go to power settings use performance settings and disable power management from powering off USB's that could be the real problem that because of no mouse movement or keyboard Windows 10 thinks there is no activity and shuts down USB power disconnecting your controller. Especially if the timing on this is exact every time.
 
Yes I am not sure what receiver you are using or is it a cabled controller. If it's an older USB device legacy support could help with stuff like this.

Also go to power settings use performance settings and disable power management from powering off USB's that could be the real problem that because of no mouse movement or keyboard Windows 10 thinks there is no activity and shuts down USB power disconnecting your controller. Especially if the timing on this is exact every time.
So basically it's a legit Xbox wireless receiver plugged into USB and a legit Xbox 360 Controller plugged into USB (for power), although, it connects wirelessly to the receiver.

Maybe a weird setup but it's the only way I've ever had it working and it's worked for around 3yrs now. As mentioned, every now and then I have this sync issue to the receiver and usually updating the driver manually from the list fixes it, but not this time. Hope that paints a clearer picture?

Thanks for the valuable input. Will go check power settings when I'm home although I'm almost certain my PC is on Performance power settings, unless a Windows update changed that at some point. Who knows... Will revert, thanks!
 
Had a similar issue with a Logitech mouse disconnecting from the receiver. In the end I swopped the receiver from the USB3.1 port to a USB2.0 port and haven't had the issue again.

May have just been coincidental too.
 
Had a similar issue with a Logitech mouse disconnecting from the receiver. In the end I swopped the receiver from the USB3.1 port to a USB2.0 port and haven't had the issue again.

May have just been coincidental too.
Did actually have this work on one isolated occasion where swapping from USB3.0 to 2.0 port worked but unfortunately that didn't work this time.
 
Top
Sign up to the MyBroadband newsletter
X