You are here

LibreOffice 4.0.2 fails to start

4 posts / 0 new
Last post
paww
Offline
Last seen: 9 years 7 months ago
Joined: 2013-04-19 02:39
LibreOffice 4.0.2 fails to start

I'm trying to launch LibreOffice 4.0.2 (but the same problem existed on this computer since updating from the 3.x version, current OO portable is running just fine), but the error mesage appears:

"Microsoft Visual C++ Runtime Library

Runtime error!
Program "[my path to libre offce]

R6025
-pure virtual function call"

Earlier I was getting the same message regardles if I ran the program from usb drive or porable apps installation in desktop folder.
My operating system is Windows XP pro, SP3.

John T. Haller
John T. Haller's picture
Online
Last seen: 11 min 51 sec ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Bad Local VC++ runtime

I believe this can happen if you have a bad copy of the VC++ runtime locally as LibreOffice could use that instead of the included one. OO is very out of date and doesn't use the modern VC++ runtimes.

Sometimes, the impossible can become possible, if you're awesome!

paww
Offline
Last seen: 9 years 7 months ago
Joined: 2013-04-19 02:39
Problem solved unexpectedly :)

Althouth the problem descibed above was still occurring after I installed updates 4.0.1 and 4.02 of LibreOffice using the PortableApps platform updater, I followed one solution found on this forum - I have reinstalled Libre Office using manually downloaded packege. And everything seems ok.

Is there any difference using the update method from the platform and manually updating apps? I thought that in both situations the files downloaded and installed should be the same.

John T. Haller
John T. Haller's picture
Online
Last seen: 11 min 51 sec ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Same

They function the same and use the same installer. The only possibility is that something was removed from LibreOffice by antivirus mistakenly or some drive corruption occurred. Unless you uninstalled and then re-installed, which means it could have been some settings file corruption.

Sometimes, the impossible can become possible, if you're awesome!

Log in or register to post comments