Bug 69066 - Upgrading LO requires user to terminate Explorer.exe on Windows because of LO Explorer/Shell extensions (Workaround: comment 12)
Summary: Upgrading LO requires user to terminate Explorer.exe on Windows because of LO...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version: 4.1.1.2 release
Hardware: All Windows (All)
: high normal
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard:
Keywords: regression
: 71163 78057 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-09-07 10:15 UTC by Luuk
Modified: 2014-11-22 21:48 UTC (History)
8 users (show)

See Also:
i915 platform:
i915 features:


Attachments
Installation assistent (27.73 KB, image/png)
2013-09-07 10:15 UTC, Luuk
Details
installation wizard error dialog (33.29 KB, image/jpeg)
2014-01-05 02:31 UTC, RobK
Details

Description Luuk 2013-09-07 10:15:36 UTC
Created attachment 85393 [details]
Installation assistent

When upgrading 4.1.0 to 4.1.1.2 i got a notice about a process that was using files and needed to be closed before installing could continue.
See attached screendumps (unfortunatly some are in Dutch

This process is not an application that i can 'normally' close. So, i do think that i should not get this notice

Installation should continue, and a messag (probably about a reboot that is required should follow)   ;(

The information on process 7740 is:
C:\Users\Luuk>tasklist /V /FI "PID eq 7740" /FO csv
"Image Name","PID","Session Name","Session#","Mem Usage","Status","CPU Time","Window Title"
"explorer.exe","7740","Console","1","95.264 K","Running","0:00:13",".NET-BroadcastEventWindow.2.0.0.0.2e0c681.0"
Comment 1 Maxim Monastirsky 2013-11-02 16:54:02 UTC
*** Bug 71163 has been marked as a duplicate of this bug. ***
Comment 2 Kumāra 2013-11-05 06:52:15 UTC
I include here the bug report from Bug 71163, which I think is clearer:

Chris  2013-11-02 14:24:55 UTC 
When I installed the new version of LibreOffice on my Windows 8.1 desktop, it will pop up during the validating install process stating that you have to close explorer.exe to continue. If you tell it to ignore it, it will not proceed until you close it. I had to go to task manager and kill explorer.exe to finish installing. Then, you have to re-launch explorer.exe to be able to use anything in windows 8.1 .

I encountered the same in a recent upgrade with LibO 4.1.2.3 on Windows Home Premium 64bit.

I'm marking importance as high as this stumps novices, and gives LO a bad reputation.
Comment 3 Maxim Monastirsky 2013-11-08 08:24:35 UTC
Might be related to Bug 56007.
Comment 4 Michael Stahl 2013-12-02 19:04:02 UTC
Andras, any idea why this happens?

does it happen only on Windows 8.1 or older versions too?
Comment 5 Kumāra 2013-12-03 02:22:42 UTC
Happens to me on Windows 7 HP 64-bit.
Comment 6 Andras Timar 2013-12-03 10:00:36 UTC
(In reply to comment #4)
> Andras, any idea why this happens?

Unfortunately I couldn't reproduce it. It can be related to shell extensions or indexing service. For example the shell extension is generating a thumbnail of a file which is on a slow drive (reading 1 byte at a time, see bug 56007), therefore Explorer holds that dll during uninstall. Hopefully the bug will not be reproducible with 4.1.4. On the other hand, if user ignores this warning, the uninstaller will ask for a reboot in order to complete uninstall process.
Comment 7 RobK 2014-01-05 02:31:07 UTC
Created attachment 91506 [details]
installation wizard error dialog
Comment 8 RobK 2014-01-05 02:31:47 UTC
I also am having the problem same as described in by Luuk below. Error dialog is also the same (in English though).
I am trying to update from 4.1.3.2 to 4.1.4.2.
My system is Windows 64 HP AMD 64-bit.

While there is a work-around, I really do like to monkey with installations in case there is some secondary effect.
I also give this high importance, as I have not see such a terminal error in other software installation.

I am willing to wait until next version, hopefully this can be fixed.
Comment 9 RobK 2014-01-05 02:35:48 UTC
Sorry, I meant I really don't like to monkey with installations.
Comment 10 RobK 2014-01-05 02:48:04 UTC
Sorry, I also meant Windows 7 HP, AMD 64-bit.
Comment 11 Kumāra 2014-01-06 02:28:46 UTC
(In reply to comment #8)
> I also am having the problem same as described in by Luuk below. Error
> dialog is also the same (in English though).
> I am trying to update from 4.1.3.2 to 4.1.4.2.
> My system is Windows 64 HP AMD 64-bit.

Thank you for reporting. However, please do not "update" the version number. It's suppose to show the earliest version the issue is occurring. I'm changing it back to the original.

The matter seems to be inconstant. When I upgraded to 4.1.4.2, the matter didn't arise at all. The difference I notice is that Explorer is set not to show thumbnails. So, Andras's guess is probably correct.

I wouldn't want to label this "notourbug" though, since the issue don't occur with installations of (most) other programs.

Meanwhile, I encourage affected ones to test. In Windows Explorer, go to Organize > Folder and search options > View tab. Tick "Always show icons, never thumbnails". Then install LO.
Comment 12 RobK 2014-01-09 23:19:16 UTC
I tried the suggestion by Kumara in Comment 11.

"In Windows Explorer, go to Organize > Folder and search options > View tab. Tick "Always show icons, never thumbnails". Then install LO."

Then I was able to install LO without any problems, and applications so far appear to work properly.

So I can recommend this as a possible workaround.

Thanks Kumara.
Comment 13 Michael Stahl 2014-02-03 17:09:55 UTC
given that bug 56007 is fixed and the shell extensions should
be much faster, can anybody still reproduce this problem when
upgrading _from_ LO 4.1.4.2 (or later) to a later version?
Comment 14 Michael Meeks 2014-02-11 13:29:09 UTC
as per mst's question ...
Comment 15 Luuk 2014-02-14 16:57:01 UTC
(In reply to comment #14)
> as per mst's question ...

/me did not have the bug again (as far as i remember), and i'm currently running 4.2.0.5 on Windows 7

I'm asking others, who can reproduce this, to give info.
But i doubt anyone having this problem will be saving enough info in order to post it here when they found this bug.....
Comment 16 Sander Voerman 2014-02-15 17:43:17 UTC
I just experienced the same problem, trying to install the 32bits x86 version of LibreOffice (4.2.0.4) on a 32 bits Windows 7 system.
Comment 17 Sander Voerman 2014-02-15 18:29:09 UTC
(In reply to comment #11)
> Meanwhile, I encourage affected ones to test. In Windows Explorer, go to
> Organize > Folder and search options > View tab. Tick "Always show icons,
> never thumbnails". Then install LO.

This workaround did not help on my system.

(In reply to comment #2)
> I had to go to task manager and kill
> explorer.exe to finish installing. Then, you have to re-launch explorer.exe
> to be able to use anything in windows 8.1 .
> 

This did work on my system (32bits windows 7, Intel Pentium Dual Core E5300). When the installer finished, I logged out of windows using task manager and then logged back in to restart explorer and get my desktop back.
Comment 18 RobK 2014-02-15 19:36:24 UTC
I updated from 4.1.4.2 to 4.2.0.4 and the installation worked correctly. In my case the issue seems to be solved.
Again this is on Win7 64-bit AMD.
Comment 19 Michael Stahl 2014-02-16 21:20:31 UTC
(In reply to comment #16)
> I just experienced the same problem, trying to install the 32bits x86
> version of LibreOffice (4.2.0.4) on a 32 bits Windows 7 system.

which was the installed LO version _before_ the upgrade?
Comment 20 Sander Voerman 2014-02-17 08:23:44 UTC
(In reply to comment #19)
> which was the installed LO version _before_ the upgrade?

None; in my case it was not an upgrade, but rather a fresh install.
Comment 21 Kumāra 2014-02-17 10:48:31 UTC
(In reply to comment #20)
> (In reply to comment #19)
> > which was the installed LO version _before_ the upgrade?
> 
> None; in my case it was not an upgrade, but rather a fresh install.

Hmmm... Shall we mark this as major?
Comment 22 Michael Stahl 2014-02-17 11:40:00 UTC
(In reply to comment #21)
> (In reply to comment #20)

> > None; in my case it was not an upgrade, but rather a fresh install.
> 
> Hmmm... Shall we mark this as major?

that is the _first_ report of somebody claiming to have this problem
on a fresh installation with no older LO installed on the system;
since this bug is about upgrades it's probably a different bug
which would be UNCONFIRMED, not NEW as this one.
Comment 23 Kumāra 2014-02-18 03:59:20 UTC
(In reply to comment #22)
> that is the _first_ report of somebody claiming to have this problem
> on a fresh installation with no older LO installed on the system;
> since this bug is about upgrades it's probably a different bug
> which would be UNCONFIRMED, not NEW as this one.

Please forgive if I'm making a wrong assumption here. It seems to me that it's not a separate bug. The issue is not between the installer program and the installed LO, but between the installer program and Explorer.exe. So, it should make no difference between an upgrade and a fresh install.
Comment 24 Kumāra 2014-02-18 04:13:03 UTC
I've just upgraded to 4.2.0.4 with Explorer's thumbnails on. No hitches. So, it seems the goal post has moved.
Comment 25 Michael Stahl 2014-02-19 14:51:23 UTC
(In reply to comment #23)
> (In reply to comment #22)
> > that is the _first_ report of somebody claiming to have this problem
> > on a fresh installation with no older LO installed on the system;
> > since this bug is about upgrades it's probably a different bug
> > which would be UNCONFIRMED, not NEW as this one.
> 
> Please forgive if I'm making a wrong assumption here. It seems to me that
> it's not a separate bug. The issue is not between the installer program and
> the installed LO, but between the installer program and Explorer.exe. So, it
> should make no difference between an upgrade and a fresh install.

No, _this_ bug is about LO bundled Explorer extensions to view thumbnails
of various documents, which somehow prevents installation of
new LO versions presumably because these Explorer extension files cannot
be overwritten or deleted; naturally on a "fresh" install you won't
have LO Explorer extensions running.

(actually i cannot imagine how there could be a conflict between
Explorer.exe and LO installation without a LO previously installed
on the system, but this is Windows and it's full of mysteries
so what do i know anyway...)
Comment 26 Sander Voerman 2014-02-19 15:13:43 UTC
(In reply to comment #25)
> (actually i cannot imagine how there could be a conflict between
> Explorer.exe and LO installation without a LO previously installed
> on the system, but this is Windows and it's full of mysteries
> so what do i know anyway...)

Just speculating: I did have MS Office 2013 installed, which also has bindings for open document filetypes. In addition to explorer.exe, the LO installer sometimes also mentioned a Microsoft Office document cache process as one of the things it needed to be terminated before proceeding with the installation. So perhaps Microsoft Office causes a similar connection between explorer and the open document filetypes, and thereby a similar conflict for the LO installer.
Comment 27 Cor Nouws 2014-05-25 20:21:02 UTC
*** Bug 78057 has been marked as a duplicate of this bug. ***
Comment 28 Michael Bauer 2014-07-01 12:34:46 UTC
Also seem to be having this problem going from 4.2.4.2 to 4.2.5.2. It brings up the error message that files used by this setup need to be closed, Windows Explorer Process ID 5484. Googling that landed me on this questions page http://ask.libreoffice.org/en/question/27733/libreoffice-4142-install-error-files-in-use/ and some further googling to this bug report.

I have not tried any of the fixes just in case I can help with identifying the problem but I am, at this stage, wondering if it's related to this issue http://ask.libreoffice.org/en/question/16047/error-1303-when-installing-libreoffice-402-on-windows-8-pro/#30099 which made me install LO in a folder outside the default /Programs folders.

I'm on Win 8 (with a Gaelic langpack), 64bit, with Office 2013 also installed.
Comment 29 Michael Bauer 2014-07-07 21:28:00 UTC
Dunno if it helps but I just had an odd solution to this problem. I needed to check something in the localization of OO that I also maintain and remembering the issues with having both installed, I uninstalled LO completely before re-installing LO.
Now before I installed OO I tried to delete the LO folder under C:/Programs and it would not let me with no specific error message. I then installed OO and had to restart. After re-starting, I could delete the LO folder.
Funnily enough I ran into the *same* problem trying to delete the OO folder under C:/Programs before re-start - but again fine AFTER restart.
Seems to me like there's some LO process that just keeps on running even after de-installation that interferers with deleting (in my case) or (in the update case) over-writing. At least that's my guess.
Comment 30 Michael Bauer 2014-07-08 16:06:38 UTC
The saga continues. There is something ... cavalier about the shoddy install process. So after my last report of being able to install it correctly has to get amended. It installs and fires up and I can open documents from the Recents list but har-dee-har-dee-har, if I use a link on my desktop to open an .odr file or if I browse to it using Explorer, I get this error:
"Another program is currently using this file"

So I then uninstall LO and re-install it (a chore in itself, the installer is still mental, how about someone sorting the UI languages *alphabetically*???) on my second hard drive in a non-system created folder E:/Programs/ and suddenly everything works again.

Seems to me LO does *NOT* like being in the default system folders for programs.
Comment 31 Kumāra 2014-07-09 03:10:01 UTC
Michael Bauer, thanks for your reports. However, Comment 29 and 30 don't seem to be related to this bug. Please report them elsewhere.

I've changed platform too All Windows based on comment 16, and added a comment on whiteboard to a workaround.
Comment 32 Michael Bauer 2014-07-09 10:13:27 UTC
I'm not a developer but my gut tells me they ARE related, it's the same chain of installation events the way I see it.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.