Bug 56563 - Update install leaves relicts of old version
Summary: Update install leaves relicts of old version
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
(earliest affected) release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2012-10-30 02:09 UTC by Lenge
Modified: 2014-11-16 17:58 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Lenge 2012-10-30 02:09:44 UTC
The LibreOffice website recommends to update an existing LibreOffice installation on Windows by just over-installing the new version. This usually works, but I experienced that the update does not thoroughly clean up some relicts of the old version. For example, if you updated from 3.5 to 3.6, the following 3.5 relicts will persist:

1.) The old installation directory (such as %ProgramFiles%\LibreOffice 3.5") is not deleted.

2.) If you had configured autostart for the old version, the corresponding "Startup" start menu entries are not removed.

3.) Several registry entries still point to the old LibreOffice installation. When you search the registry for "LibreOffice 3.5", you still find a bunch of according entries even after the update. You find even more when searching for "3.5" alone, but this will also yield some "false positive" entries that do not belong to LibreOffice.

While this is probably not a bid deal in practice, I like installers to be thorough. An uninstall should clean ANY AND ALL relicts of the application, and an update install should do the same for the respective old version.
Comment 1 Pedro 2013-06-21 11:20:34 UTC

*** This bug has been marked as a duplicate of bug 32112 ***
Comment 2 Lenge 2013-06-21 11:33:13 UTC
Bug 32112 only refers to the installation folder not deleted (part 1 of this bug) while parts 2 and 3 are not addressed. So this bug is more than just a duplicate of bug 32112.
Comment 3 Joel Madero 2014-11-06 22:05:13 UTC
Needs independent confirmation - moving to UNCONFIRMED.
Comment 4 Buovjaga 2014-11-16 17:58:35 UTC
Could not find traces of Libo 4.1 or 4.2 on my Windows machine, setting to WFM. If original reporter notices the problem with the 4.x series, they can change to UNCONFIRMED.