I spend some time on this before cracking the nut, so I thought I’d share with you all in case you ever experienced something similar. See I was hardware certifying a HP 6930p laptop for SCCM and things was fine until my attention moved to installing the “HP Quicklaunch buttons”, my first issue was that even though I extracted the installed drivers using Driver Magician or Driver Max it did not work – both programs failed to extract the certificate for the drivers thus you would have a ‘drivers not certified’ warning when installing them, well I decided to simply install the HP package with the -s switch and here things became really annoying – the installation proceeded fine and in device manager we moved from “Unknown device” to “HP Quicklaunch Buttons” but accompanied by the text “Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)” and no amount of reboots fixed this.  I tried with numerous versions of the install package, just in case it was some issue with a specific version of the package – but all had the same result. A lot of googling led me to this article where a guy named Eric has a very similar issue, he has detected a common denomitor namely  virtualization.  Eric has discovered that if he deploy a workstation using a wim image captured on a VmWare workstation and then later try to install “HP Quick Launch Buttons” he gets this issue with the ‘corrupted or missing drivers’, but if he manually installs the same machine then there is no issue.  The solution is simple, all that is missing to make things work is three files; hidclass.sys hidparse.sys hidusb.sys these files need to be copied to “C:\windows\system32\drivers” (or the equivalent on your system), and after a reboot the “HP Quick Launch Buttons” is now working fine..  But where do you get these files from?  You can of cause get them from a different system (copy them to a usb pen or what ever), but there is another easy way around this – see these three files are all related to “Human Interface Devices” and all you need to do to have them installed (copied to c:\windows\system32\drivers) is to insert an external usb mouse or keyboard (this will launch an automated installation of these three files).  Now where inserting a USB mouse or keyboard may work for a single user it’s not really appropriate for corporate installation environments, so in our corporate setup we will be copying these three files into the C:\windows\system32\drivers folder during installation – having them there will do no harm.