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:

Windows Security
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.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


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.
Answered 08/31/2010 by: VBScab
Red Belt

Please log in to comment
You're right, I'm familiar with dealing with unsigned drivers; however like I mentioned, this driver and MSI have been used with Windows 7 x86 SOEs for some time. It's only now that I'm verifying my packages on Windows 7 x64 that I've got the problem.

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.
Answered 08/31/2010 by: TheKZA
Senior Yellow Belt

Please log in to comment
Did you find a solution for this?
Answered 05/26/2011 by: jmaclaurin
Third Degree Blue Belt

Please log in to comment
I have to say I've recently run into a driver where the driver was signed, when you open the .cat file it says 'driver correctly signed' but when looking at the vendor's Verisign Certificate that comes with the driver we noticed it expired on May 11th this year. So the result still is the Windows Security dialog...

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.

Answered 05/30/2011 by: pjgeutjens
Red Belt

Please log in to comment
I have had problems in the past with expired certificates and the difficulty of trying to get the vendor to issue a new one. I find it is much easier to find a similar updated driver elsewhere.
Answered 06/02/2011 by: TheZman1
Yellow Belt

Please log in to comment

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.

  1. 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.
  2. 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.
  3. From there I added the below into my command line. Followed by my installer.
certutil -addstore "TrustedPublisher" cert_name.cer



Answered 09/18/2012 by: dugullett
Red Belt

  • Thanks, this worked well for Oracle VirtualBox 5.1.4
  • Reiterating the information found via the migee link, you will need KB3033929 and KB2921916 if you're targeting Windows7 or 2008R2.
Please log in to comment