Performance Problem: Build 3.0.657

[grunf]

did not tweaked anything, allways used and installed NOD and now ESS with standard default settings

[jhuk]

I dont see how Eset staff need info to replicate this error.

Simply running your PC is next to impossible.

I updated to this new build and I am not sure if it was actual build or a Definition Update because it only started to act up in last 24 hours.

My PC locks both CPU Cores at 70-100% for the Eset Service randomly, it pauses my PC for a few seconds when I open a Window in Explorer/Web/WMP, infact anything.

I dont really fancy removiing this build to then clean up in safe mode to then install older build.

I think Eset need put out a quick fix A.S.A.P, then a proper fix afterwards.

Oh, BTW, my Eset settings are all defaulted I do not mess with them apart from Splashscreen disabled, and any I did change at any time did not cause issues before this update.

[Marcos]

I've installed version 3.0.657 on my office computer today, enabled all options in the real-time protection and so far have not noticed any slowdown or other problems.

[jhuk]

Nor did I and it was fine for days from release of .657 till the 26th, so it may be the Definition or simply take time to act up.

There is far too many peeps reporting this, it is a REAL issue and needs some sort of fixing.

Im on Vista64 Ult btw and right now I feel like throwing my PC against the wall when it pauses randomly due to Eset taking 100% CPU on both Cores.

[wrathchild]

Originally Posted by Marcos

I've installed version 3.0.657 on my office computer today, enabled all options in the real-time protection and so far have not noticed any slowdown or other problems.

Well...now I understand why end-users have the problems (because developers don't have problems at all...never)

[Bunkhouse Buck]

Originally Posted by Marcos

I've installed version 3.0.657 on my office computer today, enabled all options in the real-time protection and so far have not noticed any slowdown or other problems.

My machine has 100% CPU usage for about 8 minutes and then calms down. This started with the invention of the Eset Security Suite, but is more pronounced with the latest build.

In addition, ESS does not like Prevx 2.0 and makes it inoperable. Having used computers since 1969, this is disconcerting to say the least. I have used Eset software for several years, but uninstalled it about a week ago.

[jhuk]

How soon till a FIX, Im sick of PC today.

If not fixed in 2-3 days I will need remove it and put on older build (PIA).

[appster]

Originally Posted by Marcos

I've installed version 3.0.657 on my office computer today, enabled all options in the real-time protection and so far have not noticed any slowdown or other problems.

Marcos~ Which OS is that office PC running - XP or Vista (x86 or x64)?

I'm also seeing unusually high CPU utilization with build 657 on Vista Home Premium SP1. The same PC didn't have that issue with build 650.

[Marcos]

Originally Posted by appster

Marcos~ Which OS is that office PC running - XP or Vista (x86 or x64)?

I'm also seeing unusually high CPU utilization with build 657 on Vista Home Premium SP1. The same PC didn't have that issue with build 650.

Hi Appster, Windows XP and Vista 32-bit. Do you use default settings?

[the_sly_dog]

Mine is the same pc is nearly unusable i unistall eset security pc back to normal.. takes forever when i logon in all the icons on screen goes white then the taskbar icons take forever about 2-3 minutes later they all load then pc is soooooo slow

[swante]

We have also had similar problems, that is when starting the computers ekrn.exe starts using cpu-power to the max, and this doesn't stop for a very long while.
When I ran the Process Monitor-tool I could see that .msp-files located in C:\Windows\Installer were constantly processed by ekrn.exe.
So what I did was to add this folder to the exclusion option, and it seems to work....
We use swedish XP Pro/SP2, with Nod 3.0.657.
Not a very good solution, but a quick work-around.
Haven't had these problems before 3.0.657 wich was installed 3 days ago

[Teraclips]

Originally Posted by knacki99

I am no IT pro Marcos but thx anyway.

I uninstalled ESS and switched to Avira PE. In this state I can not use and will not recommend ESET to my friends and colleagues.

I need a good performing and working Security Solution working out of the box. I have not the will nor the time to hassle with Tech Support.

It tool ESET 5 days to answer my question why the license info was not showing up in GUI after purchase. That was enough tech support for me.

Bye Bye

Hahaha and I changed to ESET SS from Norton 360 v2.0(Iwas using version 1.0 and no problem with performance but when I changed to version 2.0 this happened) cause of the same problem hes describing, well I wasted $ 60 for Norton and I had cover for 366 days than changed to ESET SS and cough another $ 60 (and this is just 1 pc) for ESET SS hahaha man well Im gonna keep with the same build 650 so I wont make the same mistake.

[appster]

Originally Posted by Marcos

Hi Appster, Windows XP and Vista 32-bit. Do you use default settings?

Yes, default settings. I have now removed 657 and reinstalled 650 - and the problem is gone!

[mkret]

Originally Posted by Marcos

Please provide more details as how to replicate the problem.

Certainly you are kidding. If you read the whole thread you will have enough details up the Gazoo.

Thanks NOT for the standard software company reply.

[ingber]

I also have the problem of CPU being maxed out by ESS ekrn.exe 657 (which I did not see under 650) for close to 10 mins every time after booting up my Thinkpad A31p running XP Pro SP3.

The procedure I followed was:
I exported my settings from 650.
I uninstalled 650, and followed up with ccleaner and jv16.
I installed 657 and rebooted (immediately suffering the delay described).
I imported my settings from 650 into 657. It's good I saved the settings, as there was no option when uninstalling 650 to save my settings? I still suffer the delays on every reboot.

Lester

[PizzZak]

I was also getting high CPU usage with ekrn.exe and using process monitor noticed that it was scanning *.msp files in the C:\windows\installer directory. Added the directory into the exclusion list and it fixed the issue. I have this issue on a handful of computer in my domain. Other computers work just fine without the exclusion.

As it seems some people have problem with specific folder/file extensions , as a general recommendation can be to set the real-time file system protection's extensions to the default list