https://bugs.documentfoundation.org/show_bug.cgi?id=164043
--- Comment #10 from V Stuart Foote <[email protected]> --- (In reply to Dennis Roczek from comment #9) > (In reply to Mike Kaganski from comment #8) > > No there is nothing (unless we are willing to mess with the Windows > > Installer-managed registry settings, which IMO is not a nice thing to do). > > Well, it would only update the version number field and simply remove the > version number from the name field. Well maybe could write the string for DisplayName and DisplayVersion, but could be more troublesome. > Mozilla is acting no different at this > place, and we're actually using their system... everything would actually > still the same in that list / registry entries. Except that Mozilla uses an .EXE installer and lays down links in registry to its uninstall\helper.exe and a full key for its uninstalls. And other than the Display Name & Version, the LibreOffice MSI based install uses a GUID ProductID that is unique for each LO build. The ProductIDs between release builds will not match, e.g. 25.2.4.2 is {8E3F0870-B678-46C6-A14C-069F300ABD41} 25.2.4.3 is {E67DBA3B-4C2A-44AC-BC4D-86EA56550BB3} The MSI installation *and uninstallation* explicitly use the ProductID! Effectively, after the MAR update(s) apply, the appwiz.cpl uninstall can fail as components associated with the ProductID are not correct in the Windows registry. At present you almost have to install the MSI package to bring the registry up to matching release level to be able to uninstall a MAR updated instance *reliably* using the appwiz.cpl--or risk leaving more "garbage" behind in FS and the Win registry. Leading to dependency on utilities like revo or ccleaner. -- You are receiving this mail because: You are the assignee for the bug.
