I have a basic MSI project. While investigating why one particular non-versioned file was not updated from the previous version, I found that its hash in the table MsiFilehash was outdated, i.e. it was the hash of the version of this file several releases ago. Since then the source file has changed, and the installation had the new version of this file, but the hash did not change, so Installer did not update the file during the update.

The table MsiFilehash in the ism file was populated. I deleted all records from it in direct editor hoping that this would force Installshield to re-populate it, and re-built the installation.

Now the resulting MSI does not have the table MsiFilehash at all. I guess it's probably not a big problem, but I wonder what's going on, and if there is a way to have MsiFileHash to update its records basing on the current content of the source files. The properties of all non-versioned files in the ism file still have the checkbox "Use File Hash" checked.