1 reply to this topic

[cgilley]

I have a package with multiple features and components.  For illustration, let's say we have feature A, with components A1, A2 ... and feature B with components B1, B2, etc.  After installation, we remove component A2.  Then, we launch the program which is feature B.  Although feature B is not associated with component A2, windows installer immediately tries to "fix" the problem of the missing component  - if the msi file is available, it reinstalls the component.  This also happens sometimes when we don't remove, but rather manually replace an installed component with a different version (in this case, an OCX).  
Is there a way to override this behavior, so that Windows Installer won't meddle with changes we make manually?
Further info:  this happens on W2K; we have not as yet observed it on NT4.  The package is built in IPWI.

Thanks in advance for any help.
Craig

[cgilley]

never mind, I found the answer.  For anyone else looking for similar info, just do a forum search on "repair" or "autorepair".