That's just a GUI for the DEVMGR_SHOW_NONPRESENT_DEVICES environment variable that Shades discussed earlier. It only for removing complete devices that are straggling about on the system.-Stoic Joker
I know, the reason I mentioned it is because I find it's interface easier than trawling through Device Manager.-4wd
Understood, but I got used to it long ago. Which is why I had the batch file I posted earlier "handy", as I still frequently use it.
But what about uninstalling the USB stack/driver?
EDIT: I just realised you might have thought I meant the USB driver for the device. I meant the driver for the USB hardware, (motherboard), not the device.-4wd
Appreciate the clarification, but I already knew what you meant. The simplest answer would most likely be fear.
...If one device is already starting to flake out, I'd rather not take a chance on giving the rest a head start at jumping off a cliff with it.
Not to mention that many USB device installs have the "Don't insert cable until installer tells you to" warning because the device isn't capable of finding its own ass without a map. Sure it's a bit over used and not always really necessary, but... there are the occasions where things get real messy real fast if you miss/skip/ignore that part.
Oh Yeah, I forgot the "fun part" ... Printers (which are the prime offender for this kind of crap) never actually appear
in device manager. On rare occasions (usually if installed wrong), you may get a vague reference to a composite device ... but that's about it.
For other devices that pull this crap, I usually start with device manager or the uninstall if available, then follow up with the phantom search, file system search, and a registry search ... and a few other wing-it slash and burn techniques I've cooked up on the fly. To no avail.
It's the USB port that is Cooked-Off (some how some where), The driver (is off the hook because it) will work perfectly in any other port on the machine. Assuming there is one available...
Recent Posts
