Hi,
AV doesn't use the Windows installer ... it uses InnoSetup from
http://www.innosetup.comPersonally I have seen this type of issue before with MS Office and it was to do with a corrupt registry.
Here's one of the many examples I pulled from Google Groups:
The installer will start if any files that were installed with the app are
missing or replaced with older versions or if it needs to run a first-pass
for the current user to initialize registry settings for whatever is being
loaded. Chances are that something you are referencing or installing shares
components with office and the system is repairing or completing the
installation. Normally the installer runs once to "repair" whatever it
detected was wrong and then doesn't repeat and there isn't too much that you
can do about it.
So I recon a reference counter on one of the OCX's that AV ships is bad since the InnoSetup installer checks for date/version before overwriting an existing file.
The one's AV uses are:
comctl32.ocx
comct232.ocx
mscomctl.ocx
richtx32.ocx
Fortunately the new version of AV gets away from all that VB/shared component rubbish.