title: What causes an MSI update to not update a component in an installer?
body: <p>(EDIT: Question changed.)</p>
  
  <p>I have a product with an installer which was built by InstallShield 2010, and appears by all accounts to be installing just fine as a "new" install. </p>
  
  <p>Periodically, I make changes to the contents of the installation, as I update this or that component with bug fixes and so forth. At those times I try to change the version numbers in the metadata of the files that got updated, but there are components for which that isn't possible. Of course they always end up with more recent modify dates. I change the version number for the product in the MSI data as well. However, I have not been changing the Package Code each time. </p>
  
  <p>When some users run the installer on a system where my product is already present, they're prompted with update mode UI ("would you like to update?" etc.) and the installer appears to complete. However, the updated files don't always overwrite the older files until a "repair" installation is run afterwards, especially if the version number didn't change, and there is evidence now that flagging the component's contents with a "force overwrite" doesn't change this behavior. </p>
  
  <p>What's going on here? Is there any way I can get a better result? Does the Package Code need to change whenever I rev the product or update a component? (Edit: The Package Code is changing each time I build the release, so this is not the cause of the problem.)</p>
  
  <p>Edit: It's an update UI, but maintenance after update is what actually completes the desired installation. </p>