I'm not sure where this difference comes from. In order investigate the problem, please send me all the resources and the steps that I need to take in order to reproduce it.
I can't because I don't understand the difference between the system where the installer works and the ones where it doesn't work.
edit If you want, we can do a remote assistance session on one of the affected machines.
As a workaround, you can use the Folder Removal operation in order to remove the application's folder before installing the new version.
That will not work, unfortunately (once again, it's because of history: some users have some custom modules implemented as additional executables in that folder and, a long time ago, the application user to place several config files in that folder that contains important information. We can't force users to move them. Or rather, we could, but we can't do that in the installer).
FOLLOW US
Get the latest news in Application Packaging