Hello and welcome to our forums,
From your description it seems you selected the correct custom action according to your project specs (the EXE application file must not be saved on target machine).
As "ans" suggested, the issue here might be the code your application (your EXE file) returns to the Windows Installer. A
custom action return code 0 means the application completed with success. Any other return code Windows Installer will interpret as failure.
So, in order to address the issue you can use one of the following solutions:
1. On your “Launch attached file” custom action properties page you uncheck the “Wait for return code at the end of the sequence”, in this case Windows Installer will ignore the exit code returned by your application.
2. You can rebuild the application you run in custom action to return code 0 on success, so Windows Installer doesn't throw any error.
If you have any questions let us know.
All the best,
Daniel
FOLLOW US
Get the latest news in Application Packaging