Created attachment 118775 [details] Screen grab of unhelpful dialogue During installation I got the attached dialogue Now whilst I don't doubt that every word of it was true, it was not what one might call helpful. Task manager does not show process ID numbers, and in any case is a poor way to close programmes. But it also did not show a single thing called "Microsoft Windows Search Filter Host" or any rearrangment of those words. All I had to do to continue installation was to close the windows explorer window (from which I had launced the MSI file)[1], and tell it to retry. But nothing about the dialogue would suggest doing that to the less than initiated. I thought you might want to think about that. [1] I suspect that if I had had more than one explorer open I would have had to close all of them, of course
Related to bug 69066
This did not happen on my recent update from version 4 to version 5, nor on the subsequent update for 5.0.4.2. Both of those were on Windows 10, my original report was on Windows 8.1 That does not alter my opinion of the wording of the dialogue, of course, but it might affect the project's prioritising of it.
I agree that dialog is not informative. Unfortunately Files in Use is a Windows Installer feature, and what is displayed there is up to Windows, and not the installed application. For your information, "Microsoft Windows Search Filter Host" is a system service, that's why there was no such name among tasks in Task Manager, however showing PIDs can be enabled in View/Select Column, and system processes can be included with "Show processes from all users" button. Alternatively there's a Services tab, which lists PIDs for running services. Apparently, Windows Installer has a Restart Manager feature to make updating files in use more convenient, but I have no information on how LO's installer is set up.
@Bob has this issue appeared again during 5.1.x or 5.2.x upgrades? status NEEDINFO set it back to UNCONFIRMED if issue is stil present or WORKSFORME if bug is gone
It hasn't gone wrong during V5 installs, so I don't know if it is fixed or not.
let's label this as RESOLVED WORKSFORME revert it to NEW if the bug appears again.
*** This bug has been marked as a duplicate of bug 69043 ***