On MS-Windows 7, 'LibreOffice_4.1.1_Win_x86.msi' systematically complains that it needs to update files which are opened by 'Microsoft Windows Search Filter Host'. On 2 different computers, I requested to ignore this issue : - On a powerful computer running MS-Windows 7 PRO, 'LibreOffice_4.1.1_Win_x86.msi' installed LibreOffice version 4.1.1.2, which seem to work correctly. - On a slow computer running MS-Windows 7 HOME, 'LibreOffice_4.1.1_Win_x86.msi' displayed an error code (I apologize, but I do NOT remember its value).
On the slow computer running MS-Windows 7 HOME : - The failed installation of LibreOffice 4.1.1 seems to have cleanly uninstalled LibreOffice 4.1.0 - When I tried again to run 'LibreOffice_4.1.1_Win_x86.msi', it installed LibreOffice version 4.1.1.2, which seems to work correctly. So the problem seems to appear only when trying to upgrade LibreOffice.
I have got the same problem on a windows 7 laptop : only with the newest version 4.1.2.3 the installation process complains that the "Microsoft Windows Search Filter Host" uses a file that needs to be update this is probably the "searchProtocolHost.exe" programm stopping this programm in the task manager and re-trying installation gives a new error : giving only a process ID, but which points to SmcService, which is a Symantec management Client. I actually have upgraded since the last LibreOffice installation my antivirus to Symnatec Endpoint protection V 12.1.3001.165 And I guess that this is what is causing the problem. I tried several times to stop the "searchProtocolHost.exe" and retry installation, and after several trials it worked and installation continued. Cheers Oliver
Hello Reproduced (fr-user) with 4.0.6.2 Error : "microsoft windows search filter host (process id 4116)" The user found this workaround : - disable "Windows Search" via "Control Panel \ Programs \ Programs and Features" - install LibreOffice - reinstall "Windows Search" Regards Pierre-Yves
I got the same message according search filter host process. I ignored this message (Click on "Ignore") and continued the installation and LibreOffice was installed - at least in my case - correctly. As far as I know, the search filter host process is a background process that is used to update the index for Windows Search. It may take hours (or even longer) until the index is updated, but it should not effect the system performance significantly. It seemed to me that an installation or deinstallation of LibreOffice triggers the update of the index.
(In reply to comment #4) > It seemed to me that an installation or > deinstallation of LibreOffice triggers the update of the index. More likely it's related to Bug 56035, which was fixed towards 4.1.4. So hopefully you won't see this bug when upgrading *from* 4.1.4.
On upgrade to version 4.1.4.2, this bug did NOT show up.
Issue reappeared when upgrading from 4.1.5.3 to 4.1.6
Sorry, I forgot to mention: I'm running Windows 7 64 bits.
I got the same error in Windows 8.1 Pro 64 with the installation file: LibreOffice_4.2.6-secfix_Win_x86.msi. However, this seems to be intermittent as after a restart it failed then succeeded after hitting retry in the error dialog box.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.0.1 or preferably 5.0.2.2 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-10-14
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20161108
In order to find out if this bug is still a problem, I searched for duplicates in Bugzilla. The latest one is bug 94282. According that bug report the latest version where this bug occured is 4.4.5.2. I did not find any complaints respective later versions. So it seemed that this bug has been solved meanwhile. Hence I tend to close this bug with RESOLVED WORKSFORME. Other suggestions?
This happened when I installed 5.2.3.3 on a Windows 10 laptop, so it is not fixed. The installer warned me that (approximately) The application Microsoft Windows Search Filter Host was using one of the files and invited me to close it. That's a system service. I used Task Manager > Processes, clicked (v)More details to show additional processes, found Microsoft Windows Search Index, and right-clicked on it to end task. ([sic], that's what I have in my notes, install reported Search Filter Host but for some reason I killed Search Index.) I am not using any antivirus beyond Windows Defender, the default in Windows 10. To reproduce you would probably have to copy a lot of random files into your Documents folder before starting LibreOffice install; or in the control panel Indexing Options > Advanced, click [Rebuild] and then start the LibreOffice install. Even then that might not be sufficient to trigger the conflict if particular operations in the installer and Microsoft Windows Search service have to overlap. You might have to do something else in Task Manager such as run as System Administrator to see the Microsoft Windows Search service(s). Thanks for all y'all do for LibreOffice!
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
*** Bug 94282 has been marked as a duplicate of this bug. ***
If I understand it correctly, the problem discussed here is specific to the warning issued by installer that some files required to be updated are in use by Microsoft Windows Search Filter Host. This is not a bug. Since LibreOffice provides an Explorer extension (a DLL) capable of providing data to the Windows Search, it's normal that at times the Windows Search indexing service is active, the shell extension is used. When it's used, it naturally can't be updated without a restart. And this is not a bug or error. This is not something that might or should be changed. The warning tells that reboot would be required if user doesn't shut down the process, and suggests rebooting if used does not stop the service. The installation errors mentioned in comment 1 might be an unrelated, or specific to some old version of installer (I doubt the latter, actually). Despite use of Windows Restart Manager was included in LibreOffice Windows installer, the Restart Manager can only automatically restart processes owned by currently logged on user, so it cannot restart services. I propose to close it NOTABUG.
Dear Etienne URBAH, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Etienne URBAH, 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 MassPing-UntouchedBug
It could be fixed, actually. We could add an action to stop the Windows Search service when managing the ooofilt component. For that, we need to add "ServiceControl" table [1] to our MSI; it should look like this in our generated IDT directory: ServiceControl Name Event Arguments Wait Component_ s72 s50 i2 S50 I2 s72 ServiceControl ServiceControl StopWindowsSearchService WSearch 34 1 auto_winexplorerext_lib_ooofilt__libreofficedev7_program_shlxthdl The "auto_winexplorerext_lib_ooofilt__libreofficedev7_program_shlxthdl" is the ID of the component installing ooofilt.dll, which implements the indexing of ODF files. Since this ID is generated dynamically, this table also should generate dynamically: similar to Component, etc. See solenv/bin/modules/installer/windows/component.pm and solenv/bin/modules/installer/windows/featurecomponent.pm for examples. The requirement to stop the "WSearch" service needs to be in some SCP file, possibly in scp2/source/winexplorerext/registryitem_winexplorerext.scp. This would incidentally mean that the component on which the ServiceControl entry depends would be registry_g_m_o_winexplorerext_libreofficedev76. The change would introduce a new key added to respective SCP item, which would define the service name, and what to do with it (stop, on install and uninstall, in this case). The value should be handled in a new .pm file, to generate the IDT file dynamically. [1] https://learn.microsoft.com/en-us/windows/win32/msi/servicecontrol-table