Bug 51651 - INSTALLATION: MSI issues
Summary: INSTALLATION: MSI issues
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
(earliest affected)
3.5.4 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Installer-Windows
  Show dependency treegraph
Reported: 2012-07-02 05:45 UTC by Olivier Hallot
Modified: 2023-07-13 03:14 UTC (History)
5 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 Olivier Hallot 2012-07-02 05:45:22 UTC
Observed in version, but may be valid in 3.6.

Maybe this is just a cleanup, but I have the feedback of a windows skilled sysadmin who reported this:

*** MS properties that don't work

*** An extension association does not exist or is incorrect in the register

"HKLM\SOFTWARE\The Document Foundation\LibreOffice\%VERSÃO%\Capabilities\FileAssociations"

*** Another  extension association does not exist or is incorrect in the register


*** icon path of xmergesync.dll does not exist in HKCR\CLSID


*** On uninstall, some folders and register entries are left behind.

@SET CHAVE=HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Folders
"%REG%" DELETE "%CHAVE%" /V "%PASTA%\program\\"
"%REG%" DELETE "%CHAVE%" /V "%PASTA%\program\python-core-2.6.1\\"
"%REG%" DELETE "%CHAVE%" /V "%PASTA%\program\python-core-2.6.1\lib\\"
"%REG%" DELETE "%CHAVE%" /V "%PASTA%\program\python-core-2.6.1\lib\encodings\\"
"%REG%" DELETE "%CHAVE%" /V "%PASTA%\share\\"
"%REG%" DELETE "%CHAVE%" /V "%PASTA%\share\extensions\\"
"%REG%" DELETE "%CHAVE%" /V "%PASTA%\share\extensions\dict-en\\"
"%REG%" DELETE "%CHAVE%" /V "%PASTA%\share\extensions\dict-en\pythonpath\\"
"%REG%" DELETE "%CHAVE%" /V "%PASTA%\share\extensions\dict-hu\\"
"%REG%" DELETE "%CHAVE%" /V "%PASTA%\share\extensions\dict-hu\pythonpath\\"
"%REG%" DELETE "%CHAVE%" /V "%PASTA%\share\extensions\dict-ru\\"
"%REG%" DELETE "%CHAVE%" /V "%PASTA%\share\extensions\dict-ru\pythonpath\\"


*** Need to create in the HKLM\SOFTWARE\LibreOffice\"default" key, the current version of the application, and also the package and product keys, either in MSI for the package and for the Help. The following example should be for version

Comment 1 Andras Timar 2012-07-02 06:20:49 UTC
These are multiple issues, nevertheless thank you very much, it is a very good bug report. I wanted to review this part of installer anyway.
Comment 2 João Mac-Cormick 2012-07-05 10:53:18 UTC

To analyze the Windows registry, I use the program "CCcleaner" 3-19-1721 (May 24, 2012) and the program of Piriform "fixer dll-files.com" 2-7-72-2072 (January 3, 2012) of Dll -FIles.Com.

1) Before installing, first do the cleaning with these programs.

2) I install of LibO (custom or not) and then analyze the changes in these programs.

3) I make the necessary adjustments.

4) I uninstall and then analyze the changes in these programs.

Usually more than 90% point of problems.

If you want, you can pass a tip on how to use the dllfixer. Send an email to joao@sisejufe.org.br.

Inté +V,



Para analisar o registro do Windows, eu utilizo o programa "CCcleaner" 3-19-1721 (24 mai 2012) da Piriform e o programa "dll-files.com fixer" 2-7-72-2072 (3 jan 2012) da Dll-FIles.Com.

1) Antes de instalar, primeiro faço a limpeza com estes programas.

2) Faço a instalação do LibO (personalizada ou não) e depois analiso as alterações com estes programas.

3) Faço os ajustes necessários.

4) Faço a desinstalação e depois analiso as alterações com estes programas.

Costuma apontar mais de 90% dos problemas.

Se você quiser, posso te passar uma dica de como usar o dllfixer. Manda um e-mail para joao@sisejufe.org.br.

Inté +V,

Comment 3 tommy27 2014-11-20 06:15:57 UTC Comment hidden (obsolete)
Comment 4 Xisco Faulí 2018-02-13 11:34:00 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2019-02-14 03:49:42 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2021-07-12 03:42:50 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2023-07-13 03:14:00 UTC
Dear Olivier Hallot,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team