Description: I can not install LibreOffice_6.2.1_Win_x64.msi on Win7 and my previously working installation was deleted without warning. Steps to Reproduce: 1. Begin with version 6.2.0 installed 2. Run LibreOffice_6.2.1_Win_x64.msi Actual Results: Installation appears to proceeds normally until the installation wizard reports being interrupted before it could be completed. It also claims the system has not been modified. No other errors reported. //Previous working installation of version 6.1.2 is deleted without warning.// Expected Results: Version 6.2.1 running. Reproducible: Always User Profile Reset: No Additional Info: Attempting to revert to LibreOffice_6.2.0_Win_x64.msi fails in the same manner. Downgrading to LibreOffice_6.1.2_Win_x64.msi works. Thankfully %APPDATA%\Roaming\LibreOffice\4\user was preserved. This might be due to Windows Update being required per: https://wiki.documentfoundation.org/Faq/General/General_Installation_Issues_(Windows) I have Windows 7 and unfortunately updates can not be enabled because my CPU is unsupported. I can understand if a change to the installer has made it impossible to operate without Windows Update enabled and thus I can not install 6.2.1, however having the installer remove the previously working version, fail, then claim the system was not modified is a serious problem.
Three different problems here. 1. Installer fails when Windows Update failed. This is handled in 6.3, where it will only warn that the installation of pre-requisite KB2999226 failed, and proceed. See tdf#121987. 2. Upgrade removes previously installed LO. This is tdf#117492. 3. Windows Update cannot be enabled on a specific system. Well - this is possibly not that hard limitation, since there's no requirement that the system be connected to Internet - the required update is bundled in the MSI itself; one could disconnect from Internet, enable WU, install LO, disable WU back, and connect the Internet. Marking as duplicate of bug 117492, since it's indicated as the main problem here. *** This bug has been marked as a duplicate of bug 117492 ***