Showing results for 
Show  only  | Search instead for 
Did you mean: 
Level 2

How to prevent registry values to be changed during major upgrade?

I am using Installshiled 2016 (MSI).

I am trying to create a major upgrade package. Everything works well excluding that registry values are always changed back to their default values after the upgrade.

The scenario is:

  • Installing fresh first installation.
  • User modified some of the registry values (such enable logs, servers URL etc.).
  • Performing a major upgrade.
  • Registry values that were modified by the user are changed back to their default value (set up by the installer).

    I already tried to set "Permanent" to yes, as well as "Never Overwrite" to yes in the components tab (this works well for files but not for registry values).

    Another thing worth to mention is that the original package (fresh install) was not set with "Permanent" and "Never Overwrite" to yes. I fixed it up only on a newer package. So I understand that the first upgrade will not work as I expected, however from the second upgrade it should work well, but it doesn't (it works well from the second upgrade for files).
    When I install the upgrade package (with "Permanent" and "Never Overwrite" set to yes) as fresh installation and trying to upgrade it, it also not working well for registry values, only for files.

    What am I missing?
  • Labels (1)
    0 Kudos
    (1) Reply
    Level 2

    The transform can apply your changes after installation. We use them mostly for modifying the current vendor .msi for customization.
    0 Kudos