Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: anon125 on June 13, 2017, 12:03:40 AM

Title: The procedure entry point GetLogicalProcessorInformation could not be located in
Post by: anon125 on June 13, 2017, 12:03:40 AM
The procedure entry point GetLogicalProcessorInformation could not be located in the dynamic link library Kernel32.dll
this is what I get when I try to install avast in XP.
does anyone know of a free antivirus that will work in XP? probably 32 not 64 bit
thanks all
Title: Re: The procedure entry point GetLogicalProcessorInformation could not be located in
Post by: Pondus on June 13, 2017, 12:08:48 AM
Quote
does anyone know of a free antivirus that will work in XP? probably 32 not 64 bit
Panda antivirus free (Windows XP (32-bit) SP3 or later)
Title: Re: The procedure entry point GetLogicalProcessorInformation could not be located in
Post by: Eddy on June 13, 2017, 12:17:07 AM
It means your cpu doesn't support the SSE2 instruction set.
About all av's nowadays need it.
Title: Re: The procedure entry point GetLogicalProcessorInformation could not be located in
Post by: DavidR on June 13, 2017, 12:50:40 AM
The procedure entry point GetLogicalProcessorInformation could not be located in the dynamic link library Kernel32.dll
this is what I get when I try to install avast in XP.
does anyone know of a free antivirus that will work in XP? probably 32 not 64 bit
thanks all

It certainly works on this system, see my signature, but it has XP Pro SP3 and the CPU supports SSE2.
Title: Re: The procedure entry point GetLogicalProcessorInformation could not be located in
Post by: Eddy on June 13, 2017, 12:55:19 AM
The OP's CPU doesn't support SSE2.
https://forum.avast.com/index.php?topic=203597.msg1399776#msg1399776
Title: Re: The procedure entry point GetLogicalProcessorInformation could not be located in
Post by: DavidR on June 13, 2017, 01:08:19 AM
The OP's CPU doesn't support SSE2.
https://forum.avast.com/index.php?topic=203597.msg1399776#msg1399776

Yes I only found that topic after posting in this one.
Title: Re: The procedure entry point GetLogicalProcessorInformation could not be located in
Post by: anon125 on June 13, 2017, 01:13:31 AM
thanks all
I still have sp2
Title: Re: The procedure entry point GetLogicalProcessorInformation could not be located in
Post by: Eddy on June 13, 2017, 01:22:05 AM
You should have installed SP3 and all (at least the security ones) updates after that.
But fact remains that you CPU is too old.
Title: Re: The procedure entry point GetLogicalProcessorInformation could not be located in
Post by: REDACTED on February 22, 2018, 11:56:09 PM
It means your cpu doesn't support the SSE2 instruction set.
About all av's nowadays need it.

Actually it means the procedure entry point cannot be found.

I'm using an intel D525 processor on WinXP SP2. My processor does support SSE2 and I have the very same error.

Just thought you might like to know that.
Title: Re: The procedure entry point GetLogicalProcessorInformation could not be located in
Post by: igor on February 23, 2018, 01:48:03 PM
The mentioned error has nothing to do with CPU capabilities.
It simply means that the new(er) version of Avast you are trying to install needs XP SP3 - it won't work on XP SP2 (because the specific procedure is not available there).
Title: Re: The procedure entry point GetLogicalProcessorInformation could not be located in
Post by: REDACTED on February 28, 2018, 07:36:03 PM
Which poses a problem for those of us who couldn't get XP with SP3 to run on a particular motherboard.