Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Driver Package Installer (DPInst) with the “/s” (silent) flag fails to install a signed driver on Windows XP. The certificate is a valid one (an Authenticode certificate) but not a WHQL one. How can I fix this problem?
DPInst has two "silencing" flags —
/q(Quiet) and/sw(Supress Wizard)./qimplies Quiet but also probably (I didn’t test!) sets DI_QUIETINSTALL when issuing the DIF_REMOVE request. Apparently this makes the SetupAPI library (of Windows XP) go "they’re trying to go sneaky on me!" and reject the installation if the certificate isn’t a treasured WHQL[*] one.Note that DPInst itself ignores the certificate’s validity when the
/lm(Legacy Mode) flag is set, but it’s the underlying Windows that’ll reject it still.The solution is to use the
/swflag (along with/lm).BTW, I’m still yet to check the implications of this – e.g. does Windows pop-up a "STOP Installation" prompt box under some configurations? I’ll test and update this answer accordingly.
The "STOP Installation" prompt" looks like:
[*] … or another Windows System Component Verification certificate, but that’s besides the point.