Hi PMpmeklin, -To address your first issue,you may need to attach log file from Flextnet connect folder to get more insight -This issue may be specific to UI theme,which needs to be fixed from InstallShield side.You may expect this to be fixed in their upcoming releases 🙂 -About third one,Symantec flagging with softwares had become trivial now-a-days.It depends upon the type of quarantine that you are flagged.If it is on installshield's setup.exe/binaries you can submit those to them. Last week i was been flagged for .log file,dint even have clue about it. Thanks, Jenifer ... View more

I too am unable to install ( using the most recent installers) IS Premier 2016 on my Windows 7 machine, using either the full installer or the web installer. Are the official installers going to be fixed at some point? ... View more

Am i missing something or is this a bug in Suite when primary package is InstallScript MSI Project? This behaviour is very easy to reproduce: Create an InstallScript MSI setup package (with any contents) and build it. Create a new Suite project, add one feature and add a New executable package (.exe). (Use your just created setup - of course) Create a detection condition for a package. Build suite and install it. After installation, run suite again to enter maintenance mode and select e.g. Repair. No errors, setup starts normally with Maintenance mode and setup can be Modified, Repaired or Removed normally. (No silent modes used in this example.) BUT, if you select from Releases view: Setup.exe tab/Cache Packages Locally = No, (Default is Yes) Build suite again and install it (be sure to uninstall previous version first) Then run suite again to enter maintenance mode - when selecting e.g. Repair - suite dialog starts by saying: Repairing package xxxx and an InstallShield Wizard error message box appears saying: "Another instance of this setup is already running. Please wait...." Any help is appreciated -P- ... View more