Windows upgrade installation does not upgrade (Bugzilla Bug 562)

[albbas]

This issue was created automatically with bugzilla2github

Bugzilla Bug 562

Date: 2007-10-26T10:16:44+02:00 From: Sjur Nørstebø Moshagen <> To: Knowledge Concepts/Peter Beinema <> CC: borre.gaup

Last updated: 2007-12-11T18:27:08+01:00

[albbas]

Comment 2166

Date: 2007-10-26 10:16:44 +0200 From: Sjur Nørstebø Moshagen <>

When installing the proofing tools on top of an existing installation in Windows XP, the user is given three choices:

• modify
• repair
• remove

The most logical choice is 'modify' (nothing is damaged, and nothing should be removed).

But after the installation is finished, nothing is installed, and the old version remains. This can be verified with the trigger string nuvviD (older versions) or nuvviDspeller (newer and present versions).

Also, when choosing components to 'modify', the dialog says 0kb to install.

Steps to reproduce:

1. download the windows installer, or burn a cd with the installer
2. run the installer WITHOUT UNINSTALLING the previous version

Actual result: The proofing tools are not updated, and nothing is installed

Expected: The new files to be installed, and the proofing tools to be properly updated.

Versions of the tools used in this test:

old spellers: Julevsáme, public beta 2, 2007-09-27

new spellers: Julevsáme, public beta 2, 2007-10-24

[albbas]

Comment 2194

Date: 2007-11-02 09:58:17 +0100 From: Sjur Nørstebø Moshagen <>

Confirmed also for the zip version of the installer (as opposed to the CD version, for which the original report was made).

The ideal solution would be to provide the user with an 'Upgrade' choice, but I don't know whether that is possible, and if so, how. By using some sort of version string/number which is automatically incremented?

The not so ideal but still workable solution is to document the proper upgrade procedure in the README files, which, according to my findings, should be one of two options:

Either:

1. remove and install anew Or:
2. when installing over an existing installation, make sure that one selects the 'Repair' alternative

[albbas]

Comment 2228

Date: 2007-11-21 08:52:55 +0100 From: Sjur Nørstebø Moshagen <>

Comment from Polderland:

"Installer update does not update - caused by (hardcoded, embedded) version ID of the installer. If the version ID is the same, InstallShield decides that a re-installation is not necessary. For the final version we will re-send the installShield installer with a new version number."

[albbas]

Comment 2229

Date: 2007-11-21 08:55:47 +0100 From: Sjur Nørstebø Moshagen <>

This implies that a proper solution (ie always increase the installer version number each time a new version is released) requires us to get a copy of the InstallShield software, so that we can do this on our own, without having to disturb Polderland to get a minimal change required to give the correct installer behaviour.

[albbas]

Comment 2337

Date: 2007-12-06 19:31:07 +0100 From: Sjur Nørstebø Moshagen <>

Latest comment from Polderland:

re-installation issue is not solved: when installing a new version, the installer reverts to the saved version - irrespective of the version numbers of either installers or DLLs. We've been trying all kinds of settings in InstallSHield today, but we can't get it to work as we would like, which is: install from the new installer in stead of from the old one. Only solution I can think of is an instruction for the user: de-install old version first, then install new version.

[albbas]

Comment 2338

Date: 2007-12-06 19:32:55 +0100 From: Sjur Nørstebø Moshagen <>

This issue needs to be documented in the user doc.

[albbas]

Comment 2360

Date: 2007-12-11 18:27:08 +0100 From: Sjur Nørstebø Moshagen <>

This is now included in the user documentation. Nothing more to do at the moment.

Case closed.