Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index

Which version did you install 32-bit or 64-bit?
Since 99% of the XP systems are 32-bit, that is important.

I would uninstall it at the Control Panel / Programs menu and then restart the system. Then download/install 4.4.5 to see if it works for you. If so, then make sure you are downloading the 32-bit version of 5.0.1, if you still want to upgrade to the 5.0.x line.
The direct link is . . .

You will need to download - - LibreOffice_5.0.1.2_Win_x86.msi

and if you are using USA English, download - - LibreOffice_5.0.1.2_Win_x86_helppack_en-US.msi

If you are getting the same error[s], then it may be that Win XP does not like to run LibreOffice 5.x.x

On 09/12/2015 05:32 PM, Serguti wrote:
I installed LibreOffice 5.0 in my HP laptop (Windows XP Home_SP2). When I try
to start any of the programs in the suite, I get this message:
The procedure entry point "GetLogicalProcessorInformation" coiuld not be
located in the Dynamic Link Library Kernel32.dll
The file Kernel32.dll is in the folder System32 in Windows. I do no have any
similar problem with any other program.
Does anybody have an idea what is this problem, and how to solve it?

View this message in context:
Sent from the Users mailing list archive at

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.