WalterT wrote: First of all, bryanwolf thanks for your post back in 2008! It helped me a lot today in 2011! Our programmer was trying to start a service which was using a VC SXS runtime, which he was installing via Merge module and he kept getting an error about it which rolled the installation back. The problem was it is an older merge module for which there is no matching redistributable to be found. Our way of dealing with it (using the info in the post of bryanwolf) was to make our own prerequisite that only installed that merge module, and install it before our main installer with the service. It worked like a charm. Hope this helps someone. Another option is to create your own prerequisite that installs vcredist.exe (Microsoft allows it to be redistributed in your installer). The difference between the two are that prerequisites get installed before your msi even runs, while merge modules are installed along side all your files. This is why you have to wait until InstallFinialize to use MFC and the like for installing the vc runtimes merge modules. I've successfully gotten MFC to work in the UI Sequence using this method, at it may resolve the problems mentioned here. ... View more

Poltron wrote: You need to add a new property in your Basic MSI. MSIRESTARTMANAGERCONTROL with a value of Disable and you'll no longer see the FilesInUse dialog. Rather than simply adding it as a property to have it globally turned off by default, I set the property at run time where we know it doesn't work for us; uninstall: Property-Set custom action (type 51): Install UI Sequence: After MaintananceWelcome Install UI Condition (_IsMaintenance="Remove") Property Name: MSIRESTARTMANAGERCONTROL Property Value: Disable I've blogged how I came to this solution at buildmaestro.wordpress ... View more

SteveLovell wrote: I too need to know how to use MSIRESTARTMANAGERCONTROL, I have seen this: http://msdn.microsoft.com/en-us/library/aa370377(v=vs.85).aspx But I am using a Basic MSI project, I dont mind converting to an Installscript MSI if I need to, but I still dont know how to use the MSIRESTARTMANAGERCONTROL. You need to add a new property in your Basic MSI. MSIRESTARTMANAGERCONTROL with a value of Disable and you'll no longer see the FilesInUse dialog. ... View more

Actually, this may be better. Install watch Pro http://www.brothersoft.com/installwatch-download-9407.html ... View more

That product seems to no longer be available. Maybe try: http://www.innovative-sol.com/uninstaller/ Advanced Uninstaller ... View more

I guess Express doesn't have that feature. The setup.exe bootstrapper can pass arguments to msiexec.. do a setup.exe /? and check out the /v argument. ... View more

RobertDickau wrote: I suppose it's that the UI sequence doesn't "do" anything---doesn't make any system changes---so (the thinking presumably goes) why would properties need to trickle back from the Execute sequence process to the UI sequence process? I can think of a million and 1 reasons for the UI to display properties set in the Execute sequence. Execute makes system changes, the UI displays status of those changes. In programming this is similar to a Model View Controller. Execute Sequence-Server: Runs our installscript to set the filename of a shortcut to a pdf of the language the user chose. example (GSM_Enu.pdf). The resulting property, [HELP_FILE], is added as the target value of a shortcut. UI Sequence-Client: On the SetupCompleteSuccess dialog we display a button for the user to click that SHOULD open the GSM_Enu.pdf. Well, it doesn't work because the "Server" won't share it's properties with the "Client", so we have to revert to hacks in order to transfer the information back to the UI. Perhaps I'm missing a simpler way of accomplishing this... ... View more

I had a problem like this where the major upgrade was uninstalling prerequisites and not fully installing them, leaving me with a broken machine. 😞 We changed to handling the major upgrade ourselves. In the upgrade table we have an entry for: MAJORUPGRADE_DETECTION with the advanced tab settings: Upgrade Code: {00000000-0000-0000-0000-000000000000} Detect Property: MAJORUPGRADEGUID Then a custom action: MSI CA type number: 98 working dir: SystemFolder Filename & Command line msiexec.exe /x[MAJORUPGRADEGUID] /qb /passive Then we call this from the custom action "Install" button in the UI Sequence. Doesn't work for silent installs and we have another CA to abort major upgrades if it's a silent install. Not a perfect solution, but it's been working for the last 2 years. ... View more

tpascal wrote: Thanks Walt! Currently I'm not sure where I'm "installing the msi"... Install Shield builds me a setup.exe file.. and I just run that... Media > Releases > Setup.exe tab. "MSI Command-Line Arguments". ... View more

http://community.flexerasoftware.com/showthread.php?t=182506 ... View more

I'm seeing the exact same thing. Anyone? ... View more

RobertDickau wrote: Another option (assuming an MSI project) is to create a non-advertised shortcut with Target [WindowsFolder]explorer.exe and Arguments /select,"[ProgramFilesFolder]Seagull\BarTender Suite\SDK\Assemblies". (If there's any chance the user can change the installation directory, you might use [INSTALLDIR] or the like instead of [ProgramFilesFolder]etc.) Thank you, this worked. Oddly though, I had to add it as an 'advertised shortcut' instead of just the 'add shortcut' menu item. 'add shortcut' pops up a dialog box and I have to locate a file, and [windowFolder] is not a valid selection and it does not let you continue. So I first chose 'add advertised shortcut' and then changed the advertised property to no. THEN I was able to use the settings you shared above. Thanks! ... View more

Hi, We had a similiar problem, but not exactly what the OP mentioned. On a major upgrade, the required vc8 runtimes (and other Winsxs friends) were not upgrading. We now have a solution that has been working well over our last few releases: Basically, we are abandoning the minor/major upgrade functionality of msi and using the power of commandline msiexec to uninstall the previous product if it's detected. Here we go: instructions done in IS 2008 / Basic MSI 1. Create a new Media\Upgrades entry: I called ours MajorUpgradeDetection upgrade code: {00000000-0000-0000-0000-000000000000} min ver include min ver: no max ver: Include Max ver: no Language: Exclude specifc langs: No Detect Only: YES Detect Prop (ours is still set to): ISACTIONPROP3 Only remove ..: Continue on failure: no migrate feature states: (probably should be no): yes 2. create custom action MSI Type Number: 98 ours is named: UnInstallPreviousVersion working folder: SystemFolder Filename and command (ISACTIONPROP3 contains the GUID of previous product that was detected): msiexec.exe /x[ISACTIONPROP3] /qb /passive return proc: synch (ignore) in-script exec: Immediate exec Execution Scheduling: Always execute (all are "absent from sequence") 3. Onto the User Interface\dialogs... ReadyToInstall dialog's behavior link.. Click InstallNow control Add a new event as follows: event: Do Action - Argument: UnInstallPreviousVersion - Condition: ISACTIONPROP3 The downside of this method is that it only works in the UI sequence (will not work in silent installs). You can change this, but our company had a requirement to display the version dialog to user as well as a warning that thier previous version would be removed. For directions on the warning message to users.. here it is: On User Interface\Dialogs\InstallWelcome dialog: a. Create a text box with the text you want to display if a major upgrade will be performed, .. ours is named "MajorUpgradeWarning". b. Navigate to this dialogs behavior page... then click the 'conditions' tab at the bottom of the screen. Click on MajorUpgradeWarning c. We have a Show action with ISACTIONPROP3 d. We also have a hide action: Not ISACTIONPROP3 As I mentioned, this only works in the UI sequence, not silent installs. So we then had a requirement to block major upgrades during silent installs.... a. Navigate to Behavior and Logic\Custom Actions b. I created a MSI Type Number 19 action as follows: We named it: SILENT_INSTALL_ABORT_ON_MAJOR_UPGRADE Error Msg (Probably should be translated text though): "A version of this software is already installed, please uninstall before attempting a silent install." Return Proc: sync (check exit code) In-Script: Immediate Exec Execut Scheduling: always execute Install Exec Sequence: After ISPreventDowngrade (if you dont' have that,.. it's basically after the "FindRelatedProducts" CA) Exec condition: ISACTIONPROP3 And UILevel=2 ... View more