Disabling "Would you like to install this device software?"
I have a driver package in the form of an MSI installer. I've been using it fine under x86 systems, but I'm now tuning my packages for Windows 7 x64 and installing this MSI from my VBScript now gives me this warning box:
Would you like to install this device software?
With a "Always trust software from blah blah" checkbox.
I wonder what other AppDeployers do to get around this situation? Is there a reg key I can write before the install to trust the publisher?
EDIT: I should mention that this isn't strictly a scripting question, but I figured the solution would probably require a script, so I put it here. My apologies if a mod thinks it should be posted elsewhere.
I know this question is old, but I didn't see an answer. I also just ran into this problem on a unattended install of a local printer. I'm using a Win 7 x64 machine.
- On my test box I ran through the installer. When asked if I would like to install I checkmarked "Always trust software", and clicked install.
- Once the install was done I ran certmgr.msc. Under certmgr.msc I navigated to Trusted Publishers>Certificates>"name of new cert". Right click the cert and export it. I left all questions at default.
- From there I added the below into my command line. Followed by my installer.
certutil -addstore "TrustedPublisher" cert_name.cer
I figured the solution would probably require a scriptYou figured wrong.
I'm surprised you haven't come across the problem on pre-W7 OSs as it's a common issue with XP, viz. that the driver is unsigned. Most of us either badger the vendor for a signed version (it beggars belief that these chumps still release them unsigned...) or simply sign them ourselves. There's pages and pages on AppDeploy about driver signing.
Is there any difference in the driver signing model between x86 and x64, or something else that might cause this? I guess that's my main query.
I'm still trying to get the vendor to give me a new certificate, or to be more correct, still trying to get them to see the issue. No luck so far. It seems the concept of a silent install is somewhat foreign to them.
Oh, and this was a driver downloaded directly from said vendor's website.
so that the conversation will remain readable.