driver-signing | 易学教程

dpinst / DifX won't install signed driver silently

阅读更多关于 dpinst / DifX won't install signed driver silently

问题 When installing a signed driver (i.e. with a properly signed .CAB) on Windows 7 through DpInst, unless it's a WHQL-signed driver, you cannot install it silently. If you run DpInst in the non-silent mode, it'll prompt you to trust the "publisher". If you run DpInst in silent mode, it would fail with a signing-related error code (something like 0x800b0109 -- check your setupapi.app.log). 回答1: While ilya's answer is good, the solution on Windows 7 is even easier. The command below deploys the

Sign cat file that uses Winusb.sys as kernel-mode code

阅读更多关于 Sign cat file that uses Winusb.sys as kernel-mode code

问题 I'm trying to make an USB driver to be installable in Windows 8, this USB driver uses only WinUSB. According to this post Signed INF driver works on the computer where it was signed, not others and also this website Practical Windows Code and Driver Signing all I have to do is to generate an .inf file, to generate a .cat file and sign this .cat file, but I'm having trouble with the signing part, the other steps are ok. The sites I listed above makes clear that to sign a catalog file which the

Windows 10: Error code 52 in device manager with correct signature in cross-signed driver

阅读更多关于 Windows 10: Error code 52 in device manager with correct signature in cross-signed driver

问题 we developed a driver and signed the cat and sys file with our company's Verisign signature (SHA1 + SHA256, including certificate chain). We tested it under Windows 7 and 10 both 32 and 64 bit versions. Now we have some random customers that report that our device is not recognized correctly in device manager and that error 52 shows up: Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is

Can .inf file reference a built-in driver such that it won't give warning during installation?

阅读更多关于 Can .inf file reference a built-in driver such that it won't give warning during installation?

问题 Our device relies on a built-in windows driver (usbser.sys). Do we still need to go through WHQL testing or can we install in such a way that the user won't see a warning about not passing Logo testing? I found http://support.microsoft.com/kb/837637 but it's not clear to me if this will do what I want. Does it matter whether I use DPInst program or have my own program that calls DriverPackagePreinstall? [Edit: changed "Our code" to "Our device" based on comment] 回答1: You don't need to sign

Using Driver Signing Certificate for Code Signing

阅读更多关于 Using Driver Signing Certificate for Code Signing

问题 When distributing Software (by Microsoft ClickOnce), are there downsides on using an existing Driver Signing Certificate (from GoDaddy) for Code Signing? 回答1: There shouldn't be any difference using a kernel code certficate instead of a normal Code-Signing-Certificate. They are both based on the Microsoft Authenticode system but they are - for what I know - on a different level of trust: Code-Signing-Certificates: Class 2 Microsoft-Kernel Code: Class 3 (based on https://www.startssl.com/?app

How painful is the WHQL certification process?

阅读更多关于 How painful is the WHQL certification process?

问题 Can you give an estimate of how painful the WHQL (Windows Logo for Hardware) certification process is? I see there is a 43 page step by step guide where the first step is installing Windows Server 2008 R2 x64. About how long does it will take to go through the whole preparation process before making a submission? And then how long does it take to get back a result? (My understanding is that I can avoid the installation warning for post-XP operations by just signing, but that I need to go

Windows 10: Error code 52 in device manager with correct signature in cross-signed driver

阅读更多关于 Windows 10: Error code 52 in device manager with correct signature in cross-signed driver

we developed a driver and signed the cat and sys file with our company's Verisign signature (SHA1 + SHA256, including certificate chain). We tested it under Windows 7 and 10 both 32 and 64 bit versions. Now we have some random customers that report that our device is not recognized correctly in device manager and that error 52 shows up: Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)

INF file for HID device - setting name and icon

阅读更多关于 INF file for HID device - setting name and icon

问题 I'm looking to create an inf file for a HID device (which has a custom VID/PID). I just want to replace the strings "HID-compliant device" and "USB Input Device" for our device with our strings. I know this will need signing by Microsoft, but is there a good example of how to do this? 回答1: Example of custom HID INF file on MSDN may help you 来源： https://stackoverflow.com/questions/19401162/inf-file-for-hid-device-setting-name-and-icon

Can .inf file reference a built-in driver such that it won't give warning during installation?

阅读更多关于 Can .inf file reference a built-in driver such that it won't give warning during installation?

Our device relies on a built-in windows driver (usbser.sys). Do we still need to go through WHQL testing or can we install in such a way that the user won't see a warning about not passing Logo testing? I found http://support.microsoft.com/kb/837637 but it's not clear to me if this will do what I want. Does it matter whether I use DPInst program or have my own program that calls DriverPackagePreinstall? [Edit: changed "Our code" to "Our device" based on comment] Ilya You don't need to sign usbser.sys (KMCS) but you still need to sign your .inf, because the matching of usbser.sys to your

How painful is the WHQL certification process?

阅读更多关于 How painful is the WHQL certification process?

Can you give an estimate of how painful the WHQL (Windows Logo for Hardware) certification process is? I see there is a 43 page step by step guide where the first step is installing Windows Server 2008 R2 x64. About how long does it will take to go through the whole preparation process before making a submission? And then how long does it take to get back a result? (My understanding is that I can avoid the installation warning for post-XP operations by just signing, but that I need to go through WHQL to avoid that on XP. Please correct me if this is not true.) 来源： https://stackoverflow.com