USB Keyboard issue solved. I finally found a good advice on SevenForums It appears that for some magic reason the file C:Windowsusb.inf vanished. I had to recover it from C:WindowsSystem32DriverStoreFileRepositoryusb.inf_amd64_neutral_153b489118ee37b8usb.inf Once the backup file has been copied in the right place, forcing a new device detection in Device Manager discovered again the keyboard. I will see now if it occur again whenever my LogicSniffer requires a new upgrade :D Hard week :) !
The KB was originally connected to a hub but I also tried it direct (KB brand is APM VID 04F2 PID 0111). I also tried a Labtech KB (0603 00F2). While I agree that the HID driver is standard, I have a restoration point that match the initial connection of the OLS and called "Microchip Technology Inc. Ports (COM & LPT)". I bet this one occurred when I connected the OLS first and the COM driver got installed (I remember seeing during the installation something about Microchip CDC). What I also noted when plugging my USB KB on another W7 PC is that the device when it installs correctly get up with HID/VID_04F2&PID_0111 while on my PC it gets on USB/VID_04F2&PID_0111. Very strange. Device is seen and somehow recognized as a "USB Keyboard" as it appears in devmgmt but not recognized as a HID device.... Something got wrong in my registry or something like this and unfortunately I cannot restore ... I appreciate your concern.
Hi Ian Yes, "USB keyboard" appears as "Other devices" with the yellow triangle icon and status says drivers cannot be loaded. I tried to restore my system to a restoration-point before I plugged the OLS, but for some reasons W7 can't perform the restoration, claiming about anti-virus locking a file although I did disabled the anti-virus. Having to re-install W7 each time I do an OLS update is not really an option :( ;)
I had the same problem (win7x64). Following your advice I disconnected all my USB peripherals including : - FTDI USB/TTL adapter - Mouse - KB And PIC upgrade ran fine One was conflicting, I don't know which one...
But now I have another big problem !!
My USB KB does not work anymore. I tried another one which does not work neither whie both KB works well on another PC
Apparently the operation have messed up my windows KB driver