I tried to upgrade libreoffice from version 6.0 to 6.1.5 and the installation proceeded as expected until about 60%-70% complete then I receieved a message ‘rolling back…’ and then a message saying that the installation couldn’t complete and I should try again. I subsequently tried with higher versions but these exhibited the same behaviour. Something in the installation appears to have wiped the old version of libreoffice 6.0 including the icons etc. I have hundreds of odt files but now cannot access them. Can anyone help? My system is Win 7 home premium x64
Update orig+22hrs
I have tried to install version 6.1 again today ( 4 or 5 times) with a new download from the official download site.
I have observed that the process fails at the second creating folders stage i.e. after copying files and updating registry etc.I have given permission to the installer to 'make changes etc. so I don’t think it’s a permissions issue. The same message occurs “rolling back…” There are no windows errors flagged it is the installer that fails everytime.
Before someone re-posts the ‘see the faq’ I have enabled windows update downloads and I have checked and the update required in the FAQ is already present. My system already has the Windows2015 c++ distributable.
I found an old installer for 6.0 in my archives and have reinstalled this version without any problems. I would still like to use an update to a newer version but at least I can get at the old files now.
I downloaded the msi file again; this time from the archive as per the faq and ran the log file. The final entries in the log file are shown here. Obviously I have the whole log if this helps but I am puzzled why Rootdrive property is set to E:. [Solved MSI looks for the disc with the largest free space.}
update 31/05/19
I’ve tried the install again and have created the logfile which can be found here. https://drive.google.com/file/d/1g5_g96A98jDISJir59SKlEkd1WQVSL3t/view?usp=sharing
I have had a cursory look but the only glaring error I can see is wusa.exe failing. However this is puzzling as the update service is active and running and the temporary directory that it uses exists and has the correct permissions. Of course this may be a red herring…