Showing results for 
Show  only  | Search instead for 
Did you mean: 
Level 2

IS 2016 SP1 undocumented changes

I have upraded our build machine with IS 2016 SP1 yesterday. And suddenly, our suite installer was not working anymore. After researching the issue, we found out that now, the setup.exe is being copied to a temp dir and renamed to a random name before being executed.
for example, thsi is the beginning of the suite install log:
Engine: we're running from C:\Users\ALA~1\AppData\Local\Temp\{D863CF9B-54E7-4653-BD30-CC4FE1C77D09}\_isA974.exe

And the command-line, later is
Command Line: /log"C:\ProgramData\Installation\Blah_20170302-161534" -IS_temp ORIGINALSETUPEXEDIR="\\da\Daily Builds\build" ORIGINALSETUPEXENAME="SC Setup.exe" /debuglog"C:\ProgramData\Installation\Blah_20170302-161534\SC Installation.log"

These ORIGINALSETUPEXEDIR and ORIGINALSETUPEXENAME properties are not documented, as far as I know.

Just wanted to share this info, in case someone runs into an issue like ours.
Labels (1)
0 Kudos
(3) Replies
Not applicable

Very interesting. Thanks for the heads up.

I also found an issue with suite installs and IS 2016 SP1 - see

Because of this I've had to backout IS2016 SP1 from our build environment and revert to the original release verson of IS2016. I only use Basic MSI setup projects in conjunction with the suite though and so this won't affect everyone.
0 Kudos
Level 6

We are trying to move to InstallShield 2018. I noticed this issue and then searched to findout what was posted.

This change has broken a lot of things in our installs.

Thanks for posting it. It confirms what I am seeing.

0 Kudos
Level 6

It is documented with the SUITE properties in InstallShield 2018,
0 Kudos