Hi Jeff,

> Do you think it's possible that an SB "support" dll could cause this
> stuff if the support.dll loads other DLLs dynamically (that exist in
> the installation target folder)?
>
> One of those DLLs that gets loaded dynamically is protected by
> Armadillo.
>
> This missing file stuff is really hitting us hard.

No, I don't think that a SB "support" DLL causes this.

Are you sure that the installer copies the DLL files at all? Do you see the
new DLLs (with the new version/time stamps) in the uninstall .log? In most
cases, the AV systems make use of heuristic analysis. If it would be caused
by your support DLL then the AV would only "remove" that specific support
file and not the other dynamically loaded DLLs or dependency files.

BTW, did the installer ask for a reboot (would be an indicator for a
locked/in-use file scenario). Or do you check for an "active" application
(e.g. check if the app is running and ask the user to shut it down to avoid
a reboot request)?

Friedrich