(EDIT: changed question.)
I have an installer product that was created by InstallShield 2010, and it appears on all accounts to install just fine, like a "new" installation.
From time to time, I make changes to the contents of the installation, as I update one or another component with bug fixes and so on. At that time, I am trying to change the version numbers in the metadata of files that have been updated, but there are components for which this is not possible. Of course, they always end with later dates of change. I also change the version number of the product in the MSI data. However, I did not change the package code every time.
When some users run the installer on a system where my product is already present, they are requested using the update mode interface ("do you want to update?", Etc.), and the installer seems to shut down. However, updated files do not always overwrite old files until after a “repair” installation is completed, especially if the version number has not changed, and now there is evidence that marking the contents of the component with “overwrite force” Do not modify this behavior.
What's going on here? Is there any way to get a better result? Is it necessary to change the package code when I update a product or update a component? (Edit: The package code changes every time I create a release, so this is not the cause of the problem.)
: , - , .