The purpose of a deferred execution custom action is to delay the execution of a system change to the time when the installation script is executed.
This differs from a regular custom action, or a standard action, in which the installer executes the action immediately upon encountering it in a sequence table or in a call to MsiDoAction.
A deferred execution custom action enables a package author to specify system operations at a particular point within the execution of the installation script.
The installer does not execute a deferred execution custom action at the time the installation sequence is processed. Instead the installer writes the custom action into the installation script.
- Should be placed between install initialize and install finalize.
- Does not have access to MSIDATABASE in deferred execution.