we don't see any run time errors.  when we click on installer, mouse is in busy mode for few minutes. after that nothing happens. in Event viewer we see this error. I tried the command in the article for log file . but we are not getting any log file at all. Command we tried is . D:\SharedFolder\claritiUniversalInstaller.2.4.0-beta.1_18.exe /v"/l*vx \"D:\SharedFolder\package.log\""   In Event Viewer, we consistently get this message.   Event viewer Messsage : Faulting application name: _is4811.exe, version: 2.4.0.1, time stamp: 0x5906bdf7 Faulting module name: Setup_UI.dll, version: 23.0.0.511, time stamp: 0x5906be93 Exception code: 0xc0000005 Fault offset: 0x0004176c Faulting process id: 0x25fc Faulting application start time: 0x01d716a51b1a0f54 Faulting application path: C:\Users\KBOXA1~2\AppData\Local\Temp\{A6456011-6339-40E7-B3E7-564C520B4315}\_is4811.exe Faulting module path: C:\Users\KBOXA1~2\AppData\Local\Temp\{7CC80D53-1E18-4D64-B761-641F7D583D65}\Setup_UI.dll Report Id: 2ff7091e-0fa0-42b9-9a0b-f15b41144b43 Faulting package full name: Faulting package-relative application ID:   in Azure machine , only nuget packages related to the application we are getting from nuget store. rest of the files are in system itself.    ... View more

Hi @ragava28,   You need to configure the correct executable which wait for the entire uninstallation process, you can get the executable details and its command line parameters from the registry for what is configured for the installed application while uninstalling from the Add/Remove programs( Programs and Features) . As well check the command line parameter if any needed to wait the executable for the complete uninstallation, you can get this information from the task manger while uninstalling the application.  ... View more

Hi ragava28, Were you able to get this working using Jennifer's post? I think you were looking for an 'OnUninstall' event and there is no such thing. ... View more

@ragava28  :  Suite/Advanced UI Project do not know about the functionality of your configured executable package, whether it executes batch file or powershell script.  As per the information you have updated here, it looks like your executable package extracts the files and trigger the batch file, then immediately it returns (non zero value) without waiting for the batch file to complete. So, here you have to modify your executable to wait for the batch file/powershell script execution completion. Inherently, Installshield Suite/Advanced UI Project also wait for the execution of your executable package configured in your 3rd and 4th steps. And you have mentioned your setup ends the execution without completing all the packages ("Set up shows a error saying "Looks like installer failed . do still want to continue." and setup finises").  This behavior you can control by changing the values in the Package  Properties under the "Common" tab-> Operation->Install->Exit Behavior.  And see whether you can make the exe to wait by passing command line parameter, then you can configure the command line parameter at "Common" tab-> Operation->Install->EXE Command Line. So, ensure your executable wait for batch/script  execution.                      ... View more