http://bugs.winehq.org/show_bug.cgi?id=27987
--- Comment #14 from Anastasius Focht focht@gmx.net 2012-01-05 15:45:16 CST --- Hello,
CA_RollbackHelpTransaction.3643236F_FC70_11D3_A536_0090278A1BB8 -> ActionType=3329
msidbCustomActionTypeBinaryData (1) msidbCustomActionTypeRollback (256) msidbCustomActionTypeInScript (1024) msidbCustomActionTypeNoImpersonate (2048)
"Rollback Custom Actions"
http://msdn.microsoft.com/en-us/site/aa371369
--- quote --- A rollback custom action is an action that the installer executes only during an installation rollback, and its purpose is to reverse a custom action that has made changes to the system.
A rollback custom action is a type of deferred execution custom action, because its execution is deferred when it is invoked during the installation sequence. It differs from a regular deferred custom action in that it is only executed during a rollback. A rollback custom action must always precede the deferred custom action it rolls back in the action sequence. A rollback custom action should also handle the case where the deferred custom action is interrupted in the middle of execution. For example, if the user were to press the Cancel button while the custom action was executing. ... --- quote ---
"Deferred Execution Custom Actions"
http://msdn.microsoft.com/en-us/site/aa368268
"Installation Phases and In-Script Execution Options for Custom Actions in Windows Installer"
http://www.installsite.org/pages/en/isnews/200108/index.htm
--- quote --- If the installation is cancelled by the user or aborted because of an error during script execution, the rollback script is executed to undo any changes that have been made to the target system. This is when the rollback custom actions are executed.
The rollback script is processed from bottom up, i.e. most recent actions are undone first.
When the installer has finished to process the installation script without interruption, the rollback script and all backup files are deleted, and any commit custom actions are executed.
If Rollback has been disabled on the target computer, no rollback script is created, and no backup copies of replaced files are made. --- quote ---
As I understand it, this special type of (deferred) custom action should not be executed at all in normal use case (no error -> no execution of rollback script).
Regards