Hi everyone,
I am using Advanced Installer to create an MSI installation package for an internal desktop application. During the configuration process, I added a custom action (PowerShell script) to perform operations such as creating folders, logging installations, and adjusting registry values.
The strange thing is: when running the normal installation with the interface, everything works as expected. However, when switching to silent install mode with the /qn parameter, the script does not seem to be executed at all.
Additional information:
The custom action is set to "Install Execution Stage → Deferred".
Tried running with the “Run under System Account” and “Deferred with no impersonation” options.
The MSI log does not show any signs that the script is being triggered.
Execution Condition: I used NOT Installed AND UILevel=2 (also tried removing the UILevel condition).
Question: Has anyone encountered similar issues? Does Advanced Installer have any limitations when processing PowerShell scripts in silent mode? Are there any additional permissions or UI condition adjustments that need to be made to get the custom action to work in /qn mode?
Thanks in advance, everyone!
FOLLOW US
Get the latest news in Application Packaging