This has been at least the second time I have brought up this matter. If I go to view an .AVI file EKRM will go to 99% CPU usage and stay there for over 2 minutes. This will of course raise my CPU temperature almost 20 degrees F. This has existed in the last two updates and has been brought to your attention by people other than me. Now that I have gone back to 3.0.650 everything is satisfactory again. If I fo to play an AVI file EKRM will use 99% CPU bot only for about 20 seconds. If this problem continues to exist when my subscription expires. ESET will simple be pulled from my machine as well as all of my clients. I can not send you any settings from 3.0.672 as I have already cloned my machine back to .650. But I merely updated over the old version with all the old settings. Suggestions?
Hello, If you go to the Advanced Setup > Real-time file system protection > Setup button > Extensions > the top Default button > Yes > OK, that will no longer be an issue. BFG
Could you please provide me with a link to such an avi file that is causing problems? Avi files should not be scanned at all, maybe it's in an unusual format that the scanner doesn't recognize, and thus it's trying to scan the avi file.
I am sorry Marcos but I can't. These were not obtained from a site. All I have are the AVI files which are of course huge. Why should AVI files not be scanned? Thanks for your help.
We'll definitely need to get such a file for analysis. Maybe someone knows of a url on the web from where we could download such an avi file?
Hello, If you cannot upload an .AVI to ESET then perhaps you could mail it on CD or DVD? Another possibility is that problem may have something to do with the particular codec being used to play the video. A program like GSpot Codec Information Appliance to identify with which codec the video was compressed, combined with a program like Mark Liron's SHERLOCK - The Codec Detective to help identify which codecs are installed on your computer might give you enough information to try searching for a different codec to use which does not exhibit the same problems with ESET Smart Security. Regards, Aryeh Goretsky