3.5.4 installer failure

[wagtail]

This is effectively a repeat of a FAQ that has elicited no detectable responsive answer. The basic question is: WHAT SHOULD ONE DO NEXT when the 3.5.4 windows installer, running on a win7 machine, first says that one should exit LO 3.5 and the 3.5 quickstarter, when these ARE NOT EVEN INSTALLED on the machine, and are thus certainly not running, and then crashes with the message that the “wizard” was “interrupted”. In the instant case, no other versions of LO are, or ever have been, installed on the machine in question.

Presumably, the “interruption” was caused by the installer itself, which suicidal behaviour is beyond any but the author’s control.

An “answer” saying to uninstall programmes that have never been installed is of no help. The notation that an unanswered question has been “closed” because it is “not a question” is simply baffling.

For those of us who have hit this brick wall - and we seem to be legion - Libreoffice effectively does not exist, since it cannot be installed or used.

[timar]

LibreOffice installer checks, if there is a running soffice.bin process. You may have OpenOffice.org or other derivative installed, and it is running in the background. Exit the Quickstarter (find it on system tray).

[wagtail]

From the original questioner: many thanks to Andras Timar who pointed me in the right direction, even though i never did achieve success by “exiting the Quickstarter”. i went the task manager route even before vojo posted, and that worked.

[vojo]

go to task manager and shutdown the soffice.bin process. The restart the install

[vojo]

BTW…this is another example of the long way to go with open office / libre office. It should have been obvious that this would be a problem…and frankly, pretty simple to launch msg saying so and even asking the user does he want to stop the running OO process. Heck even a boiler plate

[wagtail]

From the original questioner: I would say that vojo has the definitive answer to this plague. I had no idea that soffice was running all the time (and I still don’t know why it was…it doesn’t load any faster than when brought up cold), but task manager will both show it and kill it.

[wagtail]

What a lapse in documentation. Nothing that I have seen in the official writings mentions this roadblock, and when the installer crashes it gives no hint of why it did itself in. Previous “answers” have missed the point too. (Original questioner here again)