Thanks for the info. I'm 100% sure the password is correct because all projects build on other systems with the same build commando. It's only 1 system that gives the signing problem.. and it worked with the previous certificate. Will investigate the option to import the certificate but this has not really my preference.   Thank you ... View more

I have exactly the same problem. The problem occurs on 1 specific build system (with StandAlone Builder 2015 installed) and it came up after we updated our certificate file (pfx file used within the signing tab of the release view). Our previous certificate file (Godday) expired and we replaced it with a certificate file from GlobalSign. As I gave the pfx file the same name as before, I only updated the certificate password in all our installer projects. Building our installer projects manually via Installshield (2015) on my development sytem or automatically on our build systems via Standalone Builder (2015) goes fine for all our projects except on 1 build system. On that system we get signing errors for ALL our installer projects. Below a snipped from a verbose build log file from one of our projects: ============================================================================ Deleting file "C:\Users\amdzm\AppData\Local\Temp\1\ISC4FBC.tmp" Creating path "C:\Users\amdzm\AppData\Local\Temp\1\ISC4FBC.tmp" Copying from "d:\dev\apogee2\installers\sum\dev\tmp_Prepress_x64\resources\files\sum_sources\x64\AgfaLib140\CommonInstaller_dl.dll" to "C:\Users\amdzm\AppData\Local\Temp\1\ISC4FBC.tmp\CommonInstaller_dl.dll" Removing read-only attribute for file "C:\Users\amdzm\AppData\Local\Temp\1\ISC4FBC.tmp\CommonInstaller_dl.dll" Started signing CommonInstaller_dl.dll ... SigningHelper: error 0x80070056 while attempting to sign file ISDEV : error -1027: Failed signing CommonInstaller_dl.dll Deleting file "C:\Users\amdzm\AppData\Local\Temp\1\ISC4FDD.tmp" Creating path "C:\Users\amdzm\AppData\Local\Temp\1\ISC4FDD.tmp" Copying from "d:\dev\apogee2\installers\sum\dev\tmp_Prepress_x64\resources\files\sum_sources\x64\Hardcodet.Wpf.TaskbarNotification.dll" to "C:\Users\amdzm\AppData\Local\Temp\1\ISC4FDD.tmp\Hardcodet.Wpf.TaskbarNotification.dll" Removing read-only attribute for file "C:\Users\amdzm\AppData\Local\Temp\1\ISC4FDD.tmp\Hardcodet.Wpf.TaskbarNotification.dll" Started signing Hardcodet.Wpf.TaskbarNotification.dll ... SigningHelper: error 0x80070056 while attempting to sign file ISDEV : error -1027: Failed signing Hardcodet.Wpf.TaskbarNotification.dll ============================================================================ Any hints, tips... about what the problem can be? I don't understand it as it only happens on one specific build system and before the certificate update, it worked fine! ... View more

Hi @Revenera_Ian , as Powershell script usage don't give you the return processing option 'Asynchronous (No wait for completion)', I had to make an exe that does this job. Making an exe custom action gives you the option 'Asynchronous (No wait for completion)'... what is what you want in my situation.   Thanks for the tips to point me to the correct implementation! ... View more

Hi @Revenera_Ian , I will give your proposal a try and let you now the outcome. Thank you! ... View more

Hi Ian, Thanks for the fast reply... much appreciated. Your second proposal is not an option for us. The installer needs to be started by double clicking the setup.exe 😏 Your first proposal... that is also what I wanted to do but my question is here if there is a place to do so to have the complete logging? Because... doing it at the very end of the installation... I'm afraid the logfile is not complete yet, and it need to be to be honest. Or do I miss something? Thank you! ... View more

Hi Varul, thank you for your input and fast reponse. I understand the solution you propose but for design reasons this is not really possible to be honest. I will safe you the detailed explanation. You see it correct. I'm developing one new msi installer at the moment. Choosing Option A, like you call it, will not install any defined features and components but will call a couple of msi installers (I already made longer ago). Choosing Option B, will lead to the custom selection dialog and will install the selected features. So Option A will skip the custom selection dialog, but also needs to disable all defined features. Is there no other solution possible? Playing around with the REMOVE and ADDLOCAL properties maybe? As already said, setting REMOVE=ALL will not install any feature in case of option A, but will neither not create an uninstall entry. And I don't want that. Hopefully it is clear to you what I try to achieve... ... View more

Hi @Jenifer , ok, this explanation says it all. Not what I wanted to hear actually. There goes my only reason for upgrading to IS 2020... 😏 Any idea if it will ever be possible to use IScript actions in a 64-bit installer project? Something where is already been working on?!? All my installation projects use Installscript custom actions 😞   Thanks for the info! Cheers, Christoph ... View more

@vdonga Finally my patience will be rewarded! 😉 I'm looking forward to it. ... View more

Hi @Jenifer ,   Any idea when the setup.exe process will be 64-bit in a pure 64-bit installation project? It is a real pain in the ass having the setup.exe process still as a 32-bit process in these times. With all the projects we develop we made the switch to 64-bit already a long time ago, but we still need to build the dll's used by the installer during installation time into 32-bit! Every new release of Installshield I'm looking to the new features to see if this is finally supported but still nothing.   What is the reason to not foresee a 64-bit setup.exe launcher? ... View more