@harryclipper  and I have solved the problem by using signtool.exe after the build. @harryclipper  you can mark this post as "solved". regards Markus ... View more

To re-sign a msi file after build in a Postbuild Event is not complicated. But yes it is easier if this is a feature in InstallShield. regards Markus ... View more

Good Morning Harald, I send you a private message ... regards Markus ... View more

@harryclipper , Are you from Germany ? I just ask to known in which time zone you are located. regards Markus ... View more

You can use signtool.exe to sign your msi package manually. I use this procedure to sign my msi packages which I have build in older InstallShield version: Example: signtool sign /a /t http://timestamp.digicert.com /fd sha256 "E:\Develop\InstallShieldProjects\IS2012SP\Projects\XYZ-Product\Product Configuration 1\Release 42.3000\DiskImages\Disk1\XYZ-Product.msi" signtool.exe is part of the Windows SDK which you can download at the Microsoft. Just looked at your log file. You build your msi package with setup.exe bootstrapper and as single image. So my suggestion does not work for you. You can only sign the setup.exe but not the msi file inside. May be think about to not compress everything in setup.exe. regards Markus     ... View more

Okay, but you can not execute an InstallScript function in a msi package to alter the summary information. What you can do is create a vbscript, .Net or C/C++ program that runs after the msi file was created, read the version info with the automation interface and modify the msi file with MsiSummaryInfoSetProperty or SummaryInfo object. An example from a vbscript, which does something similar: Dim objInstaller As Object Set objInstaller = CreateObject("WindowsInstaller.Installer") If Not objInstaller Is Nothing Then Dim objNewDatabase As Object Set objNewDatabase = objInstaller.OpenDatabase(szLocNewInstPackage, 0) If Not objNewDatabase Is Nothing Then Dim objSummary As Object Set objSummary = objNewDatabase.SummaryInformation(3) objSummary.Property(11) = Now objSummary.Property(13) = Now objSummary.Persist objNewDatabase.Commit End If End If Just theory, you have to try/test/modify regards Markus ... View more

You can add some info also in the InstallShield Editor: regards Markus ... View more

I solve this, that (depending on the project type msi/installscript/suite/...) I set the "Project File Format" to XML, then I open the file with a text editor and do a "find all" on the path variable I search. If I find not more than the entry itself, I know I can delete. If it occurs more than once I can see where it is, because the XML file format is readable. regards Markus ... View more

Just 2 questions: have you signed the MSI package and also all your support/program files ? it looks like you use VBScript in your MSI package, is this correct ? regards Markus ... View more

see here: https://community.flexera.com/t5/InstallShield-Knowledge-Base/Hide-Build-Warnings-Selectively/ta-p/4073 regards Markus   ... View more

You could use a "System Search" to check if the keys/values exists and store that in a property. And use the property/result in a condition in your component. regards Markus ... View more

@Dan_Galender , just looked to the help library, and yes what I said is wrong. But I use the /debuglog switch in suites since Installshield 2013, so it should work also in 2014. Just looked to the user's guide and the /debuglog switch exists since IS-2013 and is valid for Basic MSI, InstallScript MSI and Suites. regards Markus ... View more