our latest whql'ed custom driver has incorrect entry 1 of our upcoming product. upcoming product composite device , our whql'ed driver has entry matches device id composite device instead of individual interfaces.
when new device connected machines have whql'ed driver, device gets binded our driver , not windows generic parent driver (usbccgp.sys). prevents interfaces in device being listed.
we manually fix uninstalling driver device , making bind usbccgp.sys driver. in vista , higher versions, delete driver binaries @ time of uninstall. there no direct way delete driver binaries in xp. makes difficult cleanly uninstall driver
can fixed using uninstaller? best way fix affected machine in automated way?
download windows driver development kit (win ddk) , locate devcon.exe executable architecture. then, elevated command prompt:
devcon.exe find =usb to list of current devices.
devcon.exe -r remove =usb *your_hardware_id* will complete disassociate device , driver target machine. if have trouble getting hardware id can blow away usb drivers , let windows auto-detect them after reboot.
devcon.exe -r remove =usb * extreme, yes. effective, yes. work virtual comm ports day , our test machines experience same issue. technique has yet fail.
Comments
Post a Comment