Bug 33829 - COMODO Internet Security blocks Installation of Win x86 en-GB Helppack
Summary: COMODO Internet Security blocks Installation of Win x86 en-GB Helppack
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
(earliest affected)
3.3.0 release
Hardware: x86 (IA32) Windows (All)
: medium major
Assignee: Not Assigned
Depends on:
Reported: 2011-02-02 02:56 UTC by mattcarr
Modified: 2011-02-06 20:42 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Windows Installer msiexec dialogue box which interrupts installation (17.83 KB, image/png)
2011-02-02 22:49 UTC, mattcarr

Note You need to log in before you can comment on or make changes to this bug.
Description mattcarr 2011-02-02 02:56:17 UTC
When I run the LibO_3.3.0_Win_x86_helppack_en-GB.exe on Win XP SP3 (this is the recommended help file as autodetected by http://www.libreoffice.org/download/), the installer proceeds normally (extraction of temporary installer files) but then it shows a dialog showing what appears to be instructions for using the Windows installation framework:

>Windows ® Installer. V 3.01.4001.5512 
>msiexec /Option <Required Parameter> [Optional Parameter]

When this dialog is dismissed, the installer seems to abort without installing the help files. If the installer exe is run again, it will bring up a number of warnings as the temporary installation preparation files still exist.
Comment 1 mattcarr 2011-02-02 03:05:57 UTC
The setup.exe within the temporary files still works if ran manually, however. (I'm assuming it's supposed to be triggered automatically, as is the case with the main LibreOffice installer exe.)
Comment 2 Rainer Bielefeld Retired 2011-02-02 08:36:58 UTC
NOT Reproducible with "LibreOffice 3.3.0 RC4 - WIN7  Home Premium (64bit) German UI  [OOO330m19 (build 6 / tag]".

I downloaded "LibO_3.3.0_Win_x86_helppack_en-GB.exe" (8.944.610 Bytes) from
Started installation in my "C:\Users\Public\Ressourcen\LibO\33RC4" by double click on "LibO_3.3.0_Win_x86_helppack_en-GB.exe" from WIN Explorer (without frills like "with admin permissions"), extracted  to custom folder 
<C:\Users\Public\Ressourcen\LibO\33RC4\LibreOffice 3.3 Help Pack (English (United Kingdom)) (4d37040d) Installation Files> (what really is a horrible name for a folder), and installation to my LibO program file system has been done without any problems. 

Please contribute 
- detailed information concerning your WIN

- whether your installation .exe might have been damaged

collect error messages and contribute them, if yo do not want to type them all you might collect parts of screenshots with comments in a DRAW document.
Comment 3 mattcarr 2011-02-02 22:49:06 UTC
Created attachment 42883 [details]
Windows Installer msiexec dialogue box which interrupts installation
Comment 4 mattcarr 2011-02-02 22:49:46 UTC
I couldn't immediately reproduce the error after completely uninstalling and reinstalling LibreOffice and the helppack. I downloaded the helppack again from both http://www.libreoffice.org/download/ and ftp://ftp.rz.tu-bs.de/pub/mirror/tdf/tdf-pub/libreoffice/stable/3.3.0/win/x86/LibO_3.3.0_Win_x86_helppack_en-GB.exe, but I couldn't reproduce it immediately with either exe. (A bit strange.)

I believe I have traced the error I reported down to the configuration of my firewall/security software. (My bad, sorry.)

I'm using COMODO Internet Security which has a module called 'Defense+', which by default is set up to automatically sandbox executables based on heuristics. Because the unpacking process for the LibreOffice helppack attempts to create and execute a second executable, the Defense+ identifies this as suspicious behaviour and sandboxes it. I think that this is what causes the 'Windows Installer, msiexec...' error dialog I mentioned to appear.

If I disable Defense+ entirely or add the newly extracted Installation Files setup files to its whitelist, the complete installation process works as it should (extraction of Installation Files directory to desktop, execution of installer, installation of helppack).

Conversely, if I add the extracted Installation Files setup files to the Defense+ blacklist or set the Defense+ to its most strict setting, then I can readily reproduce the problem as described in my original comment.

I suppose that users using security software should just keep in mind that this kind of thing can happen with installers.
Comment 5 Rainer Bielefeld Retired 2011-02-02 23:38:10 UTC
Thank you for your investigations. May be you can contribute some additional hints on <http://wiki.documentfoundation.org/Releases/3.3> or elsewhere?
Comment 6 Rainer Bielefeld Retired 2011-02-06 20:42:03 UTC
Currently it seems that there is nothing that can be fixed by LibO