Apache OpenOffice Community Forum

I can open both programs but when I try to do anything, even just a click on the file, I get "not responding" with a blue circle going round and round. These are not large files. I then installed version 4.1.5 and get the same result. I am running Windows 10 version 1709 32 bit. The program had been running fine for a long time, and then suddenly is not usable. Please advise.

Majorcfo

Reset your user profile by doing the following. Shutdown OpenOffice. Open any file folder and type
%appdata%\openoffice\4
in the address box near the top. That will take you to a folder containing a folder called user. Rename that user_old and restart OpenOffice. Is it stable now?

No, not stable. Will not even open an existing file.

Start Taskmanager (Ctrl Shift Esc) and kill all soffice or openoffice processes shown on TM's tabs.

Any security application that could interfere? Have you tried to switch it off?

Nothing there. I rebooted and tried CAlC again - file loads but same result - program not responding. Tried TM again and nothing there.
Only security application is Avast antivirus. I have never had problems with Open Office that I have used for years.

Start Windows in Safe Mode and see if the problem persists when Windows runs in that mode.

It worked okay in safe mode. I rebooted, and tried the program after disabling each start menu item, and the problem still exists. Is there a known compatability problem in OO 4.1.5 and Win 10 v1709?

I ran the OO repair tool and got the following message: "Program c:\programfiles\openoffice4\program\unopkg.exe R6034 Application has made an attempt to load the C runtime library incorrectly." I then uninstalled 4.1.5, rebooted, and installed 4.1.4. The same problem still exists.
Any further ideas?

majorcfo wrote:I ran the OO repair tool...

What is the "OO repair tool"? Google didn't find it.

Open Office Repair is one of the choices in setup.

1. Close AOO
2. Uninstall AOO
3. Rename C:\Users\xxxxxxn\AppData\Roaming\OpenOffice\4\user to C:\Users\xxxxxx\AppData\Roaming\OpenOffice\4\user-OLD. You may need to show hidden files to see it
4. Download AOO from http://www.openoffice.org/download/index.html
5. Install AOO.

Your problem will be solved so please view your first post in this thread and click the Edit button (top right in the post) and add [Solved] in front of the subject.

I did all that and my problem is still not resolved. When I try to open the program from the task bar, I get "Program c:\programfiles\openoffice4\program\unopkg.exe R6034 Application has made an attempt to load the C runtime library incorrectly." When I try again, the programs open. Writer seems to be okay now, but Calc still is not responding after I open a file. I really need to get Calc to work.

Did you do all 5 steps exactly as asked?

YES I DID.

Is Windows defender running?

No, I use Avast. See message Thu Feb 01, 2018 5:17 am. I disabled all startup programs one at a time and still have the problem.

Just in case, please check for Windows Defender. There have been reports that a recent Win10 upgrade installed (or enabled?) it, causing OO access problems.

No, it is turned off!!

Well, in fact, it seems to be a widespread issue, just google "Application has made an attempt to load the C runtime library incorrectly" and you'll see plenty of similar issues with other software.
See also: [Solved+Issue] OOo Won't Start - Error Loading VCRT Library.

Googling attempt to load the C runtime library incorrectly gets 287,000 hits suggesting it is a general Windows problem and not just AOO.

Have you just installed something? or just updated something? or had a Windows update? Use System Restore to go back to before you saw the problem - if it is fixed, it was one of the updates, installs or changes made. iTunes and its accompanying software has been shown to be a cause.

I uninstalled iTunes and it did not solve the problem. I then completely uninstalled Open Office, ran through the complete Microsoft solution for R6034, and installed Open Office 4.1.5. It now appears OO is working properly. Thanks for all your help.

Please mark this as complete.

I rebooted a couple of times and it works like a charm.