I have an MSI from a software company that only has Merge modules contained. The rest of the application is run centrally from a shared area. The problem is that it constantly loads when you start other applications that presumably use the same DLL's contained in the merge modules. None of the merge modules have any HKCU keys so there is no need for it to be repairing its install (correct me if im wrong).

The merge modules are MSWINSOCK, MSCOMCTL, COMCAT, OLEAUT32, AND COMDLG32. Any suggestions ony why or how to stop this msi from repairing would be greatfully revieved as it loads itself automatically when using around three or for other apps.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Hi Dan,
If you open those msm and search for HKCU keys and find none doesn't mean they don't create those keys when install,
assure it by repackaging or regviewing its installation, then act consequently.
I tell that because I've found many msm with Custom Actions and self-regs that can drive to mistakes and confusions.

Hope it helps!

Answered 02/09/2007 by: KrisBcn
Purple Belt

Please log in to comment