rguggisberg wrote: Is this happening on Windows 10? Is your InstallShield package a 32 bit package? I ran into the same thing executing PS in a bat file. I found that you need to execute the 64 bit version of PS. YES, there is a 32 bit and a 64 bit version! And if your IS package is 32 bit, it will execute the 32 bit version of PS! Here's what I did in a bat file. Do the translation for your application. REM To avoid error on Windows 10 we need to specify path to 64 bit PS as done below because our parent process is 32 bit. SET "PSx64=" & REM Can't use sysnative on Server 2012 R2 IF "%WinVer%"=="10" SET "PSx64=%windir%\sysnative\WindowsPowerShell\v1.0\" "%PSx64%POWERSHELL.EXE" ... rest of your PS command line I will test this in just a little while and let you know how it goes. Running powershell and doing Dism commands from an install project is all new to me so I'm a little lost and have a project with a lot of IIS and Azure config to do. ... View more

The setup.exe you are using needs to include an application manifest that includes the Windows 10 compatibility GUID in the list of supported OSes. The following MSDN article includes an example manifest that lists Windows 10: Targeting your application for Windows You can also look at the manifests that InstallShield builds into setup.exe's built with the product. The following manifests in the \Program Files\InstallShield\2015\Support folder all include the Windows 10 compatibility GUID: setupexe.admin.manifest setupexe.highest.manifest setupexe.invoker.manifest ... View more

you can look @ MsiSetProperty or use a Type 51 custom action aka set-a-property to set ADDLOCAL with desired features ... View more

For a Basic MSI, you should probably use MsiProcessMessage instead. This will allow Windows Installer to properly parent the dialog, and suppress it in scenarios that should not show UI. However the API will not work if the custom action is invoked in response to a ControlEvent (such as a button press on a dialog). ... View more

For uninstallation through maintenance mode, you can add a dialog box the same way as you do for installation, by hooking up the Next button of the previous dialog box to whatever you want to display (also the Back button of your new dialog to the previous, etc.). You can look at MaintenanceWelcome's conditions and control events to see what's going on. For uninstallation through the Remove button of Add or Remove Programs, though, you can't, really. Only the Execute sequence runs in that case, and you shouldn't put a dialog in the Execute sequence, at least if you believe ICE13. You could disable the ARP Remove button to force the maintenance UI dialogs, but this wouldn't affect things like someone right-clicking the MSI file and choosing Uninstall. ... View more

If you have not, please refer to ISCmdBld.exe. ... View more

Hi Brandon, you need to know what sort of upgrade you are working on. Are you thinking of a minor upgrade, a major upgrade or a small update? See the following document to see what is supported with each of them: http://kb.flexerasoftware.com/doc/Helpnet/installshield18helplib/MajorMinorSmall.htm Once you have decided, you can then find out what condition to use. To give you a clue: For a patch, you could copy-paste the condition that displays the PatchWelcome dialog. For a minor upgrade, you could copy-paste the condition that displays the SetupResume dialog. For a major upgrade, you can use the property set in the "ActionProperty" column in the Upgrade table. But don't forget the following points: You also need to think about silent installation. So your custom action might have to be sequenced in the InstallExecuteSequence. Some properties like IS_MINOR_UPGRADE or IS_MAJOR_UPGRADE are only set if the installation is launched with setup.exe. This is not always applicable when a system administrator performs a silent installation. So, I would not use such properties in your conditional custom actions. Minor upgrades should be avoided, in my humble opinion. And you are likely to face some problems when deploying minor upgrades if you have used dynamic links in your Basic MSI project. ... View more

You can make this from Setup Design, create for each one New Feature and for each feature NewComponent and there you can add your included objects to be installed:) in that way you can select which one to be reinstalled.Make all with Click Right. Good luck! ... View more

Thanks for the help I'm now using MsiEnumRelatedProducts and MsiGetProductInfo and it is working great. I have one other question. I have a chained MSI that I'm installing. Is there a function I can call to get the version from that MSI? I have tried to search for the answer but all the answers are solutions for outside of installshield using SQL or C++. I would hope that installshield would have a function for this. Brandon ... View more

What you need to do is a sort of hybrid major upgrade: [LIST=1] Detect if the previous InstallScript-based version is installed. If it is installed, deinstall it. Install the new version. Here is how I would implement it: [LIST=1] Detect if the previous InstallScript-based version is installed. I don't think there is a method like MsiGetProductInfo for InstallScript-based installed products. So, you could use a System Search instead. There are many traces of the previous installation you could search for: "[ProgramFilesFolder]\InstallShield Installation Information\{OldProductCode}\Setup.exe", for instance. Or search for registry keys/values in "HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\{OldProductCode}". You need to store the value of "HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\{OldProductCode}\\UninstallString" in a property, let's call it "UNINSTALL_PREVIOUS_PRODUCT_COMMAND". Insert a "RemoveExistingInstallScriptInstallation" CustomAction just before or just after RemoveExistingProduct. This new CustomAction will use the UNINSTALL_PREVIOUS_PRODUCT_COMMAND property to start the deinstallation. Install the new version. There is nothing special to do, this will be done by the rest of the sequence you already have. The procedure above assumes that the deinstallation of your previous version works. One more point: the deinstallation of the previous product won't be rollback-able. ... View more

This InstallTalk blog post discusses rollback actions: http://blogs.flexerasoftware.com/installtalk/2011/10/i-take-it-all-back-using-windows-installer-msi-rollback-actions.html. In short, in order to be able to be rolled back, your action needs to be a deferred action (between InstallInitialize and InstallFinalize), with the rollback action occurring before it in the sequences, and generally returns ERROR_INSTALL_FAILURE when you need to trigger rollback. ... View more

Hi, yes I have the conditional check and that part is working fine. I have also fix the silent part and that is working fine. The problem I have right now is that after it installs I get a message from installshield that says "The installation of Microsoft SQL Server Native Client 11.0 (x86) appears to have failed. Do you want to continue the installation?" If I look in control panel the native client has installed fine. If I run it not in silent mode and display all the dialogs the native client still installs fine but I continue to get the error message from installshield telling me it has failed. What is installshield checking that is causing this error message to display? Here is a copy of my PRQ file. Brandon ****EDIT**** I just found that I was checking for the version 10 file. So I have changed the name and file version and I'm rebuilding to test right now. ***New Edit***** That fixed it. Thanks for getting me in the right direction. ... View more

Unfortunately, InstallShield does not provide the ability that allows you get SQL query information back to the installer at this time. I wonder if you could write a SQL script that raises an error if the specified user is not a member of the admin group. ... View more

If you create a brand new project from scratch and add a connection & a script in the SQL Scripts view, is it reproducible? ... View more

Are these custom actions in immediate execution or Deferred Execution (After InstallFiles)? Setting them to Deferred execution will trigger the custom action after the files are copied (provided its sequenced After InstallFiles action) ... View more