I am having no success in modifying a Windows Installer MSI to run a batch file after the primary output has been installed. I have searched for this and found many suggestions, but nothing that works.
- Add a Custom Action
- Custom actions can only be executable files. A batch file is not executable.
- Create a Windows Scripting Host executable that runs the batch file
- Many people have tried to do this, including on SO, and no one has been able to get this to work.
- Use WIX or InstallShield
- I do not have the time or authority to change company installer technology.
- Edit the .msi with Orca and add a custom property, then a custom action, then edit the InstallExecuteSequence, …
- I have been trying this for hours and have only created installers that throw a system error when I run them.
What you said above is incorrect:
Custom Actions (even without tools like InstallShield) can be .EXE, VBScript, JScript, or DLL based. If you write a DLL, you can write whatever code you want to call a batch file or make any changes you want to the system — there is no limit.
Update: an example that worked for me: (entry in CustomAction table)