Bug 129087 - Can not uninstall 6.3.2.2
Summary: Can not uninstall 6.3.2.2
Status: CLOSED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
6.3.2.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-28 20:20 UTC by Dirk Munk
Modified: 2019-11-30 10:51 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
logfile uninstall (95.27 KB, application/x-zip-compressed)
2019-11-30 08:40 UTC, Dirk Munk
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Munk 2019-11-28 20:20:19 UTC
I’m trying to uninstall 6.3.2.2 so that I can install the 6.3.3 version. However when I use the uninstall from Windows apps, I will get a small window to confirm that I want to uninstall Libreoffice, and when I click Next nothing happens.  When I click Cancel after a few minutes, nothing happens either. The same happens with the Help package.

How can I uninstall 6.3.2.2 in a proper way?
Comment 1 Julien Nabet 2019-11-28 20:33:49 UTC
V Stuart: thought you might be interested in this one.
Could it be some antivirus, a corrupted registry which could prevent the user to uninstall LO?
I think I've already seen a comment from you providing several hints but I don't remember which bugtracker.
Comment 2 V Stuart Foote 2019-11-28 23:49:29 UTC
Find the MSI installers for the prior (6.3.2.2 build); donwload them again [1] if 
you'd deleted from your system. Bet sure to get the correct installer for your locale and prior install.

First though restart the computer. 

Then launch a Windows Command prompt, or PowerShell, 'run as administrator' to get an admin level prompt.

Next change directory for the command window or powershell to where you downloaded the msi installer packages.

Want to first uninstall the LibreOffice Help, then the main LibreOffice program. But in case things go wrong again you'll want to capture a verbose log of the uninstall.

Enter these commands one at a time (adjust the package name):

msiexc.exe /X LibreOffice_6.3.2.2_Win_x64_helppack_en-US.msi /L*v uninstallHelpLog.txt

msiexc.exe /X LibreOffice_6.3.2.2_Win_x64.msi /L*v uninstallLog.txt

And, if uninstall still goes wrong, the logs will have some details on what happened. Zip them up and attach--we'll have a look.

Hope that clears things up and you can proceed to install 6.3.3 or 6.3.4, or even the pending 6.4.0rc.

But you may have to reset the installer cache--but that is something more involved.

=-ref-=
[1] https://downloadarchive.documentfoundation.org/libreoffice/old/
Comment 3 Dirk Munk 2019-11-29 11:15:48 UTC
I still had the original .msi files, so I was able to use those.

This is the log file form my first unsuccessful attempt to uninstall the help files:

=== Verbose logging started: 29-11-2019  11:55:38  Build type: SHIP UNICODE 5.00.10011.00  Calling process: c:\windows\system32\msiexec.exe ===
MSI (c) (A0:4C) [11:55:38:693]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (A0:4C) [11:55:38:693]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (A0:EC) [11:55:38:708]: Resetting cached policy values
MSI (c) (A0:EC) [11:55:38:708]: Machine policy value 'Debug' is 7
MSI (c) (A0:EC) [11:55:38:708]: ******* RunEngine:
           ******* Product: LibreOffice_6.3.2_Win_x64_helppack_en-GB.msi
           ******* Action: 
           ******* CommandLine:  REMOVE=ALL
MSI (c) (A0:EC) [11:55:38:708]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (A0:EC) [11:55:38:708]: Grabbed execution mutex.
MSI (c) (A0:EC) [11:55:38:788]: Cloaking enabled.
MSI (c) (A0:EC) [11:55:38:788]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (A0:EC) [11:55:38:790]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (3C:E0) [11:55:38:803]: Running installation inside multi-package transaction C:\Users\Munk\Downloads\LibreOffice\LibreOffice_6.3.2_Win_x64_helppack_en-GB.msi
MSI (s) (3C:E0) [11:55:38:803]: Grabbed execution mutex.
MSI (s) (3C:A4) [11:55:38:807]: Resetting cached policy values
MSI (s) (3C:A4) [11:55:38:807]: Machine policy value 'Debug' is 7
MSI (s) (3C:A4) [11:55:38:807]: ******* RunEngine:
           ******* Product: C:\Users\Munk\Downloads\LibreOffice\LibreOffice_6.3.2_Win_x64_helppack_en-GB.msi
           ******* Action: 
           ******* CommandLine:  REMOVE=ALL CURRENTDIRECTORY="C:\Users\Munk\Downloads\LibreOffice" CLIENTUILEVEL=2  CLIENTPROCESSID=5280 
MSI (s) (3C:A4) [11:55:38:810]: Machine policy value 'DisableUserInstalls' is 0

So even as administrator I wasn't able to uninstall the help pack.
Comment 4 V Stuart Foote 2019-11-29 15:03:41 UTC
Unfortunately that summary log provides no insight into the issue--beyond the policy value 'Debug' is 7. Would need a Verbose log, i.e. with an "/L*v <logname.txt>" flag. And thus far not clear as to the Windows build and install type, physical or VM. We'll assume in either case there is no lack of disk space or a quota issue. 

Otherwise, lots of steps to manually recover from a MSI Installer\InProgress hang and follow with manual cleanup. 

Before that worth a run with Microsoft's "Program Install and Uninstall troubleshooter" [1], simple to use but maybe find a tutorial. The Windows10Forums article [2] seems complete.

Give that a go and see if it clears the MS Installer hang.

=-ref-=

[1] https://support.microsoft.com/en-us/help/17588/windows-fix-problems-that-block-programs-being-installed-or-removed
[2] https://www.tenforums.com/tutorials/86975-program-install-uninstall-troubleshooter-windows.html
Comment 5 Dirk Munk 2019-11-29 19:10:18 UTC
I used Microsoft's "Program Install and Uninstall troubleshooter", and it worked. It takes forever, but it did uninstall the help pack and the main program. 

Thanks!
Comment 6 Julien Nabet 2019-11-29 19:24:20 UTC
Thank you Dirk for your feedback.

Thank you V Stuart for hints (I'll put in my local notes :-) )
Comment 7 Dirk Munk 2019-11-29 23:11:33 UTC
Some additional information.

Installing 6.3.3. showed the same problem, nothing happened. 

The first time I tried it, it waited for a very long time, and then all of a sudden it started to install. Unfortunately it ran across the Program directory problem, so the installation could not finish.

After a reboot the Program directory was gone, and I tried again to install 6.3.3. It didn’t work, so after a very long time I got a message that the install had not started, with the question if I wanted to continue to wait. I did, and it still did not install. 

After a third attempt to start the installation, the installation finally started after avery long wait. The Help pack installed at the first attempt, but also after a very long wait.

So it appears as if the Windows Installer doesn’t want to start during uninstall an install. Why? I have no idea.
Comment 8 V Stuart Foote 2019-11-30 00:07:47 UTC
Dirk,

The LibreOffice Windows builds are pretty standard MS Installer configurations, with reasonable defaults and custom actions. 

The Verbose logging really is needed to judge if issues are with our packaging--or due to some oddity in Windows environment or even the installing account privileges.

Fine to Close this => WORKSFORME, but we still don't know details of your system configuration and why you might be getting such delays/latency during MS Installer uninstall & install attempts.

Your choice, but if you could provide the verbose logs, we can at least render a comment.

Regards,

Stuart F.
Comment 9 Dirk Munk 2019-11-30 00:46:18 UTC
I'm not trying to suggest that it has anything to do with Libreoffice, it's far more likely a Windows problem.

This is my system info:

OS Name	Microsoft Windows 10 Pro
Version	10.0.18363 Build 18363
Other OS Description 	Not Available
OS Manufacturer	Microsoft Corporation
System Name	THEBEAST
System Manufacturer	CLEVO
System Model	P170EM
System Type	x64-based PC
System SKU	Not Applicable
Processor	Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz, 2601 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date	American Megatrends Inc. 4.6.5, 24-1-2013
SMBIOS Version	2.7
Embedded Controller Version	255.255
BIOS Mode	Legacy
BaseBoard Manufacturer	CLEVO
BaseBoard Product	P170EM
BaseBoard Version	Not Applicable
Platform Role	Mobile
Secure Boot State	Unsupported
PCR7 Configuration	Binding Not Possible
Windows Directory	C:\WINDOWS
System Directory	C:\WINDOWS\system32
Boot Device	\Device\HarddiskVolume5
Locale	Netherlands
Hardware Abstraction Layer	Version = "10.0.18362.387"
Username	TheBeast\Munk
Time Zone	W. Europe Standard Time
Installed Physical Memory (RAM)	32,0 GB
Total Physical Memory	31,9 GB
Available Physical Memory	21,3 GB
Total Virtual Memory	36,6 GB
Available Virtual Memory	24,8 GB
Page File Space	4,75 GB
Page File	C:\pagefile.sys
Kernel DMA Protection	Off
Virtualisation-based security	Not enabled
Device Encryption Support	Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and the device is not Modern Standby, Un-allowed DMA-capable bus/device(s) detected, Disabled by policy, TPM is not usable
Hyper-V - VM Monitor Mode Extensions	Yes
Hyper-V - Second Level Address Translation Extensions	Yes
Hyper-V - Virtualisation Enabled in Firmware	Yes
Hyper-V - Data Execution Protection	Yes

I will try to uninstall the Help pack tomorrow, and see if I can get a usable log.
Comment 10 Dirk Munk 2019-11-30 08:40:49 UTC
Created attachment 156197 [details]
logfile uninstall

This is the important part of the log of the successful uninstall of the help pack, Notice the 8 minutes delay !!
Comment 11 Mike Kaganski 2019-11-30 09:04:11 UTC
Obviously, the system takes 8 minutes for "Calling SRSetRestorePoint API" - i.e., creating a restore point [1]. Funny, but that's not a LibreOffice's fault.

But possibly we should disable creation of restore points in our installer [2], since we don't install low-level system components that may make system unusable and thus requiring restore points?

[1] https://docs.microsoft.com/en-us/windows/win32/msi/system-restore-points-and-the-windows-installer
[2] https://docs.microsoft.com/en-us/windows/win32/msi/msifastinstall
Comment 12 Mike Kaganski 2019-11-30 10:51:23 UTC
https://gerrit.libreoffice.org/84113 is implementation of proposal from comment 11. I don't think it's a "fix" for the issue, which is actually a user system issue; but it's inspired by this.