- Jul 7, 2008
- 5,558
- 25
- 91
I know this is possible. My older PC could do it. Does it depend on the motherboard? Or the chipset?
To be more specific: I have an Xbox 360 controller hooked up to the back of my PC (via USB). I use it for only a handful of games, and occasionally I will get a new game that doesn't allow the gamepad to be disabled. Due to lazy programming, some video games will force you to use the gamepad if it detects one, rather than giving you the option to use keyboard and mouse. In this case I must manually unplug the controller or disable it in Windows.
No big deal, right? Well, I don't like to reach behind my PC and unplug the gamepad everytime I play a poorly-designed game. To work around this, I simply go into Windows Device Manager, find the Xbox 360 controller, Right-Click, Disable. That's it. The controller's still plugged in, but my games won't detect it anymore, as if it's not there.
At least... my other PC allowed me to do this. With my new computer, everytime I try to "Disable" a USB device in Windows device manager, I have to reboot my entire computer.
Windows is fully updated, all of my necessary drivers are installed and everything. Why in the world am I now being asked to reboot my computer everytime I disable my Xbox 360 pad?
For reference: My other PC had an i5-2500 CPU with an Asus P8P67 motherboard. I could disable and re-enable the gamepad all day without ever rebooting. My new computer, on the other hand, has an FX-8350 and a 990FXA-GD65 motherboard. It makes me reboot everytime. Why? Is there some kind of limitation of this motherboard that the P8P67 didn't have? Is there some sort of USB plug 'n' play option in the BIOS I need to toggle? What's going on?
Thanks in advanced. Seems like a mundane question but it really irritates me.
To be more specific: I have an Xbox 360 controller hooked up to the back of my PC (via USB). I use it for only a handful of games, and occasionally I will get a new game that doesn't allow the gamepad to be disabled. Due to lazy programming, some video games will force you to use the gamepad if it detects one, rather than giving you the option to use keyboard and mouse. In this case I must manually unplug the controller or disable it in Windows.
No big deal, right? Well, I don't like to reach behind my PC and unplug the gamepad everytime I play a poorly-designed game. To work around this, I simply go into Windows Device Manager, find the Xbox 360 controller, Right-Click, Disable. That's it. The controller's still plugged in, but my games won't detect it anymore, as if it's not there.
At least... my other PC allowed me to do this. With my new computer, everytime I try to "Disable" a USB device in Windows device manager, I have to reboot my entire computer.

Windows is fully updated, all of my necessary drivers are installed and everything. Why in the world am I now being asked to reboot my computer everytime I disable my Xbox 360 pad?
For reference: My other PC had an i5-2500 CPU with an Asus P8P67 motherboard. I could disable and re-enable the gamepad all day without ever rebooting. My new computer, on the other hand, has an FX-8350 and a 990FXA-GD65 motherboard. It makes me reboot everytime. Why? Is there some kind of limitation of this motherboard that the P8P67 didn't have? Is there some sort of USB plug 'n' play option in the BIOS I need to toggle? What's going on?
Thanks in advanced. Seems like a mundane question but it really irritates me.