I had a problem similar to this a while back with a USB dongle. Problem turned out to be an INF misconfiguration and the driver was failing the copy into system32/drivers. May or may not be related to your problem.
BTW, you can make a single driver that will handle the device in both states and do the initial firmware load and renumeration, then handle the device normally when it comes back up. NT does the same flailing around to get this working either way, but a single driver seems a little easier to manage, at least to me.
Loren
displayed. “A problem occurred during installation, your hardware might
not
work properly” or “Your new hardware is installed but might not work
properly until you reboot”.Looking into the setupapi.log, does not lead us to any real conclusions,
as
there are no errors indicated. The only thing you do see is :@ 11:32:28.222 #W165 Device “USB\VID_0ADA&PID_8000\6&2C3B5705&24&1”
required
reboot: Device not started (unknown reason).