Description: We installed LibreOffice 6.4 on three different computers that had Microsoft Office 2016 also installed. When we uninstalled LibreOffice 6.4 the windows Office 2016 installation was corrupted and no longer worked. We had one machine with Windows Office 2019 and there was no such problem. Steps to Reproduce: 1. Start with Windows Machine with Office 2016 installed 2. Install LibreOffice 3. Uninstall LibreOffice 4. Try to open an Excel/Word file or the application -> fails Actual Results: Cannot open Office document or application Expected Results: Should be able to open the document or application Reproducible: Always User Profile Reset: No Additional Info: Not messed up Microsoft Office 2016
Created attachment 158000 [details] Dialog that appears when trying to open a Microsoft Office Document
Thanks for filing, if you still have more boxes to test against could you run the LibreOffice uninstall from a command line (or PS) and capture a verbose log. Done using the GUID/CLSID for LibreOffice package: msiexec.exe /x {5DE38E8F-2A6F-44E7-9D24-0C6D056597D6} /L*v lo640uninstLog.txt helppack should be removed first, same syntax. Should be GUID/CLSID {19572391-C01B-469D-9697-92978998771C} You can verify the CLSID to use with regedit search of Windows registry starting at the stanza, and searching for LibreOffice: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall When the uninstall completes, try your launch of Office 2016. If it fails with the same error go ahead and zip up the verbose log and post here as an attachment. Also would help if you have a look in the Windows logs by running eventvwr.msc for more details of the "Preparing to install" error on launch of Office 2016.
FTR: https://ask.libreoffice.org/en/question/229523/ tells about the opposite. Both are absolutely strange.
Created attachment 158048 [details] Verbose log from LibreOffice Uninstall
Created attachment 158049 [details] Details of the "Preparing to install" error on launch of Office 2016 (1 of 3)
Created attachment 158050 [details] Details of the "Preparing to install" error on launch of Office 2016 (2 of 3)
Created attachment 158051 [details] Details of the "Preparing to install" error on launch of Office 2016 (3 of 3)
We tried it again on another computer and saw the same thing. I have attached the verbose log from the uninstall and screenshots showing the details of the "Preparing to install" error on launch of Office 2016 (3 different screenshots).
Sounds more like MS feature/bug, please search for "outlookfiles" and listed component.
Sorry, I don't understand. What is the MS bug? Where do you suggest that we search for "outlookfiles"?
BTW, we have found the same problem with LibreOffice 6.3.4
(In reply to Shimon Shore from comment #10) > Sorry, I don't understand. > > What is the MS bug? Where do you suggest that we search for "outlookfiles"? in 2.jpg the message says "feature 'OUTLOOKFiles'...". I guess search the web, hard drive and registry.
(In reply to Buovjaga from comment #12) > (In reply to Shimon Shore from comment #10) > > Sorry, I don't understand. > > > > What is the MS bug? Where do you suggest that we search for "outlookfiles"? > > in 2.jpg the message says "feature 'OUTLOOKFiles'...". I guess search the > web, hard drive and registry. @Shimon Shore, any update on this ?
Sorry for the delay getting back to this... @Mike K, looking at attachment 158050 [details] MS Office Outlook is looking for the PersistentHandler for ".odt" The verbose uninstall log, cliped below, shows we do clobber the file type. Are we too aggressive? Or is MS's launcher at fault... as with see also bug 130320 MS Office's PersistentHandler "defaults" have caused issues. =-clip from attached verbose log-= MSI (s) (F4:08) [11:14:39:569]: Executing op: RegOpenKey(,Key=.odt,,BinaryType=1,,) MSI (s) (F4:08) [11:14:39:569]: Executing op: RegRemoveValue(Name=Content Type,Value=application/vnd.oasis.opendocument.text,) MSI (s) (F4:08) [11:14:39:571]: Executing op: RegRemoveValue(,Value=LibreOffice.WriterDocument.1,) MSI (s) (F4:08) [11:14:39:571]: Executing op: RegOpenKey(,Key=MIME\Database\Content Type\application/vnd.oasis.opendocument.text,,BinaryType=1,,) MSI (s) (F4:08) [11:14:39:572]: Executing op: RegRemoveValue(Name=Extension,Value=.odt,) MSI (s) (F4:08) [11:14:39:573]: Executing op: RegOpenKey(,Key=.odt\LibreOffice.WriterDocument.1\ShellNew,,BinaryType=1,,) MSI (s) (F4:08) [11:14:39:573]: Executing op: RegRemoveValue(Name=FileName,Value=[INSTALLLOCATION]share\template\shellnew\soffice.odt,) MSI (s) (F4:08) [11:14:39:575]: Executing op: RegOpenKey(,Key=.odt\PersistentHandler,,BinaryType=1,,) MSI (s) (F4:08) [11:14:39:575]: Executing op: RegRemoveValue(,Value={7BC0E713-5703-45BE-A29D-5D46D8B39262},) MSI (s) (F4:08) [11:14:39:576]: Executing op: RegOpenKey(,Key=.odt\shellex\{00021500-0000-0000-C000-000000000046},,BinaryType=1,,)
(In reply to V Stuart Foote from comment #14) I suppose that MSI simply does its job: it removes the keys it wrote when installed. If the correct behaviour of one MS product (Windows Installer) breaks another MS product (launcher), then it's totally MS launcher's fault; especially since it likely breaks at the LibreOffice's native file type. All that said based on the Stuart's comment. I didn't check if the problem is actually that.
@Shimon, Can you describe the install sequence for the systems affected? For the image/scratch install involved, on initial setup was MS Office installed before or after LibreOffice? Not the updates if any, but the initial setup.
(In reply to V Stuart Foote from comment #16) > @Shimon, > > Can you describe the install sequence for the systems affected? > > For the image/scratch install involved, on initial setup was MS Office > installed before or after LibreOffice? Not the updates if any, but the > initial setup. The computers we used had MS Office installed much before LibreOffice. LibreOffice was installed later just for a short time and then uninstalled.
Hello Shimon Shore, A new major release of LibreOffice is available since this bug was reported. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Shimon Shore, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Shimon Shore, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp