Disabling "Would you like to install this device software?"
Hey,
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?
Cheers
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 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?
Cheers
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.
1 Comment
[ + ] Show comment
-
@dugullette. Thank you very much this was extremely helpful years after it was posted. Thanks Much! - Rickm19 4 years ago
Answers (6)
Please log in to answer
Posted by:
dugullett
12 years ago
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
http://www.migee.com/2010/09/24/solution-for-unattendedsilent-installs-and-would-you-like-to-install-this-device-software/
Comments:
-
Thanks, this worked well for Oracle VirtualBox 5.1.4 - VexingGoat 8 years ago
-
Reiterating the information found via the migee link, you will need KB3033929 and KB2921916 if you're targeting Windows7 or 2008R2. - sitchris 7 years ago
-
Thanks. This worked on Win7 and Win10 for me. - ebjorgan 5 years ago
-
This was super helpful years after it was first written. Thanks so much! - Rickm19 4 years ago
Posted by:
anonymous_9363
14 years ago
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.
Posted by:
TheKZA
14 years ago
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.
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.
Posted by:
pjgeutjens
13 years ago
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.
PJ
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.
PJ
Posted by:
TheZman1
13 years ago
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.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.