msi package is called up after replacing a dll

[Voigti]

Hi all,

I created a setup with 3 features. Each of the features creates registry entries with default values which must be changed by our customers. I set the flags to "Automatic". If I understood this right the registry entry will just be created if it doesn't exist.

We use a third party application for scanning for which we did extensions by processing a dll the third party made available.
Some extensions for the third party application we install with my setup.

Actually it works fine.

But now we had to change this dll installed with my setup and we had an update of a second feature.

We did that manually because we needed to do some work in the third party application after replacing the dll what we can't do during an update.

In most cases that worked fine. But in some cases the msi package was called up for installing some modules.
Doing this causes the registry entries to be overwritten with the default value.

I don't understand why the msi package is called up again.
I thought if I install all features local all needed functions and modules are available.
Can anyone explain why this happens and what I can do for protecting the registry entries against being overwritten ??
Do I need to use another flag ??

Thanks for all help,
Voigti

[JeffClark]

It may be detecting that the DLL component has been changed, and thinking it is corrupt, is trying to "fix" it to the original.

You say you made this change manually? So the regisrty still says this component should have the old version of the DLL.

You may want to create a patch for the original installation.

[Voigti]

Hi Jeff,

that make sense but one more question: why does that just happen on some pc and not on all ??

Thanks,
Voigti

[JeffClark]

I'm afraid you've stumped me on that one. Maybe someone else can answer that.

[Voigti]

Hi Jeff,

no problem, but thank you for your help.

Voigti