At first I thought you were talking about taking this other thread to the next stage: "USB Daisy-Chaining gone haywire"
But in all seriousness - I'd probably just reboot (as aggravating as that is).
This is way
past a reboot-will-fix-it issue. This is more of a the inner workings of the OS need to be beaten with a hammer kind of issue.
IIRC there is a setting (registry?) that enables the Windows device manager to show hidden devices. That includes All and every USB device ever connected. Uninstalling the troublesome device will help with this problem.
Yeah, I know what you're after there, a batch file will do it (used it many times for CD burner issues in the Win2k days):
Echo Find Phantom Devices
But that's not what we're after here either. It is not a full device (present or otherwise) that is causing the problem. It's more of a fragment of a device, that is being clung to by the USB subsystem itself. I have literally seen and participated in this scenario many times:
Device X, plugged into Port X, and had been working there forever, just stops.
Nothing you do with or too Device X will bring it back to life (uninstall/reinstall/reboot/whatever), nothing...it is dead to Port X.
Now, the fun part.
Plug any other
device into Port X, and it instantly springs to life and works perfectly.
Plug Device X into any other
port ... and it instantly springs to life and works perfectly.
Plug Device X back into Port X ... and we're right back to it being deader than hell. Port X is/has been Cooked-Off.
If by chance you have the time, or are just that mad, flattening the machine and reinstalling the OS ... Will result in Device X once again happily working in Port X. Which does (/did in the past) at least confirm that is/was not a hardware problem ... but it is a bit over-the-top.
Hence my quest for something that will effectively flatten the dynamically created USB configuration info only and therefore allow the to X's to once again play nice together.