[Bug 41269] MSI uninstaller does not clean up Registry's UpgradeCode, ProductCode

wine-bugs at winehq.org wine-bugs at winehq.org
Tue Oct 30 12:32:46 CDT 2018


https://bugs.winehq.org/show_bug.cgi?id=41269

Reinhold <reinhold.hoffmann at hotmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|FIXED                       |---
             Status|CLOSED                      |REOPENED
            Version|1.9.18                      |3.19

--- Comment #49 from Reinhold <reinhold.hoffmann at hotmail.com> ---
This bug was fixed in Wine greater 2.0.3 and was OK in Wine-3.0 a year ago.
But it is open again in Wine-3.19. 

Scenario:

(1) A Windows app with version e.g. 3.1.7 is installed
(2) An new version of this app e.g. 3.1.21 gets installed with same UpgradeCode
but different Product- and PackageCode and with the directive
"RemoveExistingProducts" in the installation sequence BEFORE the new
installation.

PROBLEM:
The new 3.1.21 does not get installed automatically. In the installation
process the windows comes up again whether the former 3.1.7 should be Repaired
or Removed.
After Repair or Remove the former version gets uninstalled and the installer
terminates without installing the new 3.1.21.

BUT teh installation of 3.1.21 needs to be started again.

Two years ago (Nov. 2016) we ran through a long and somehow painful discussion
and fixed the scenarion in Wine greater than 2.0.3. Also, Wine 3.0 worked fine.

But the bug is open again in Wine 3.19

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.



More information about the wine-bugs mailing list