Try copying the file yourself via a custom action. Here's an example: 1. Delete the large file from "Files and Folders" view. 2. Add the large file to "Support Files | Advanced Files | Disk1" 3. Create a custom action "New VB Script | Stored in Binary File". Name it "InstallBigFile" or something like that. I used this code to copy the file: szInstallDir = Session.Property("INSTALLDIR") szSetupExeDir = Session.Property("SETUPEXEDIR") + "\File.xxx" set filesys=CreateObject("Scripting.FileSystemObject") If filesys.FileExists(szSetupExeDir) Then filesys.CopyFile szSetupExeDir , szInstallDir End If 4. Sequence the custom action to suite your needs. I used "After InstallInitialize" for my test. 5. Condition it to you needs. I used the Install Exec Condition: NOT Installed AND NOT PATCH 6. Create a custom action "New VB Script | Stored in Binary File". Name it "DeleteBigFile" or something like that. I used this code to delete the file: szInstallDir = Session.Property("INSTALLDIR") + "\File.xxx" Set filesys = CreateObject("Scripting.FileSystemObject") If filesys.FileExists(szInstallDir) Then filesys.DeleteFile szInstallDir End If 7. Sequence the custom action to suite your needs. I used "After InstallBigFile" for my test. 8. Condition it to you needs. I used the Install Exec Condition: REMOVE="ALL" 9. Build and run. File is installed without error. 10. Uninstall. File is uninstalled without error. ... View more

Use the Install button instead of the Finish Button. Details: 1. Set "Finish" button to: No 2. Set "Install" button to: Yes 3. Set "Cancel" button to: Yes 4. Set "Install" button text to "Continue" 5. Set "Install" button action to: {Open MY_INSTALL_EXE} ... View more

I ran a quick installation with standard logging, -x, and -v. Here were items I noticed in -x that were not in the standard or verbose logs. This was a very basic setup so there may be more information captured for more advanced setups: MSI (c) (34!8C) [18:14:55:444]: Creating MSIHANDLE (4) of type 790531 for thread 12428 MSI (c) (34!8C) [18:14:55:444]: Closing MSIHANDLE (4) of type 790531 for thread 1242 MSI (c) (34:84) [18:14:55:472]: Baseline: Sorting baselines for {B8D9B7B2-1898-4A27-9443-03A6DAC53049}. MSI (c) (34:84) [18:14:55:472]: Baseline: New baseline 1.0.0 from transaction. MSI (c) (34:84) [18:14:55:472]: Baseline: Sorted order Native: Order 0. MSI (c) (34:84) [18:14:55:472]: Baseline Data Table: MSI (s) (FC:24) [18:15:08:164]: Enabling baseline caching for this transaction since all active patches are MSI 3.0 style MSPs or at least one MSI 3.0 minor update patch is active MSI (s) (FC:24) [18:15:13:992]: Delta compression fallback method for this product transaction is 'MSI 2.0 legacy obsolescence' MSI (s) (FC:24) [18:14:59:264]: Setting cached product context: User assigned for product: 54DF169F4A250394DB51781E9401C12A MSI (s) (FC:24) [18:14:59:264]: Using cached product context: User assigned for product: 54DF169F4A250394DB51781E9401C12A MSI (s) (FC:24) [18:15:16:703]: The file represented by File table key '_4bitdll.dll' has no eligible binary patches ... View more

If you want to call a function in a 3rd party dll, use the custom action "New Standard Dll". See this link for details: Calling Functions in Standard .dll Files ... View more

This sounds like it could be a feature of the operating system. You might want to visit these links for more info: Clear lists on the Start menu and taskbar Kill New Program Highlighting in Any Start Menu ... View more

By default, InstallShield checks the return code of the 3rd party application you are running. To change this, go to the "Return Processing" property of the custom action. Change it from "Synchronous (Check exit code)" to "Synchronous (Ignores exit code)". Now whenever a user cancels the 3rd party application, InstallShield will continue with the installation and your second application should now launch. ... View more

I just tested this and it worked ok for me. InstallShield 2012 Spring, Windows 7. Here are the steps I took: 1. Create a new basic MSI project. 2. Add a file. 3. Add a "New Kill Process" custom action. 4. name the custom action: KillThis 5. Set the "In-Script Execution" to: Deferred Execution 6. Set the "Install Exec Sequence" to: After InstallInitialize 7. Create a new propery named: KillThis 8. set the property name to: notepad.exe Note the process name must appear exactly as it does in Windows Task Manager. "Notepad" would not work here. 9. Launch notepad. 10. Build and run the setup. notepad.exe silently terminates. I tried an alternate method of killing a process and this worked as well: 1. Create a new basic MSI project. 2. Add a file. 3. Add a "New Exe | path referencing a directory" custom action. 4. Set "Working Directory" to: SystemFolder 5. Set "File Name & Command Line to: taskkill.exe /f /im notepad.exe 6. Set "In-Script Execution" to Deferred Execution 7. Set the "Install Exec Sequence" to: After InstallInitialize 8. Launch notepad. 9. Build and run the setup. notepad.exe silently terminates. ... View more