I have a machine that is now experiencing what others here have, where ESET startup scan will run with 25% cpu load, and the memory will creep up from 50k, to max memory over a period of time. Memory usage ramps up about 200bytes per second. I disabled and then removed the "auto startup scan when machine starts up" scheduled job from ESET. Restarted machine, and EKRN.exe process is once again running 25%. After about 3 minutes of a user logging in, the memory usage is nearing 600megs of a 2gig ram machine. And, according to ESET main screen, it is scanning files. Watching it this time, it does not seem to be going over 600megs. I have now disabled the "auto startup scan upon virus definition update" scheduled scan. Will reboot and see how that fares. After a restart, and not having any startup scans in the scheduler, the computer started scanning files again. CPU usage of EKRN.exe process at 25-30%. Memory at 730meg. Can see on ESET status page that files are being scanned slowly. Memory usage seems to be holding firm around 730meg this time. But why? Why so much cpu usage when the initial installation scan of files does not even use more than 5% cpu cycles? Why is there a startup scan when nothing is scheduled to occur at startup? Set scheduled scan of files occurs at 6pm. this is occurring at noon. Running Eset Endpoint v5.02. I am domain admin and enterprise admin, and users are local admins.