Hi everyone,
I'm David and I've been using Advanced Installer Professional to build MSI packages for our internal Windows applications. One feature that I think would be really useful is a built-in option to verify the SHA-256 hash of existing application files before an upgrade starts.
We occasionally have users who manually replace or patch files in the installation folder. The upgrade usually continues without warning, and if one of those modified files can't be overwritten correctly, we end up with support tickets that are difficult to diagnose. Right now we're handling this with custom actions and PowerShell scripts, but it feels like something that could be integrated into the installer itself.
It would be great if Advanced Installer could compare the current file hash with the expected one, then let us choose an action such as continue, prompt the user, repair the installation first, or write a clear message to the installer log. Having this available as a standard installer action would simplify many enterprise deployment scenarios and eliminate a lot of custom scripting.
Would anyone else find a feature like this useful?
FOLLOW US
Get the latest news in Application Packaging