;)I was making some investigation and it could be possible that the problem appears when avast tries to make the rootkits analysis on startup in old versions.
turn off on troubleshooting-- rootkits analysis when start system
I will try I hope it could solve the problem. It is not an ideal solution but could be a temporary solution.
I love you two, edialechu and DavidR for those informations !
I reinstalled Avast 9 without rootkit scan activated, and it works just fine for the moment.
Is it safe to do a VPS update + boot scan with sensibility at maximum + disable the rootkit scan if nothing is detected?
I guess a new rootkit would be detected by the File agent and/or the Web agent before it could infect the system?
I can’t say if it is safe to do a VPS update as it isn’t only virus definitions that get updated but also Engine updates. I also don’t know how the Engine and definitions update function in avast 9.
As for a new rootkit, well the reason for the anti-rootkit scan is rootkits by their nature can be well hidden and may not be found by conventional resident scanners.
Hello guys, could you please reproduce the issue, collect and share with us the performance logs?
The description how to get those performance logs is available on this forum post: https://forum.avast.com/index.php?topic=237567.0
Thank you.
hi thanks i created an account just to say i was trying hard to figure out why my cpu fan was working so hard constantly 100% cpu utilization on 1 core. thanks for creating this post making me feel that im not the only user that is facing this weird issue.
Windows 7 sp1 with avast 9.0.2021 and 10.4.2233
even after using avastclear and reinstall avast 9.0, upgraded to avast 10.0 didnt fix the issue.
disable rootkit scan fixed it thanks! most likely something in that 25AUG update triggered something else why have we been using it no issue for years?
couple of days ago i disabled rootkit scan, now i tried to enable rootkit scan again on my desktop, i cant seem to reproduce the issue!
i have a laptop my dad uses that has rootkit enabled all along and does not have cpu hog issue, not sure why?
Hey there.
First of all, thanks for having considered our problem on “old machines” and ancient Avast versions.
I’m using Avast 2014.9.0.2016 on Win7 SP1 with rootkit scan disabled for 3 days and it went ok.
I just updated to VPS version 210903.8 and rebooted : CPU goes up to 50% (= 1 core) after ~10 minutes like the initial problem i had but now it peaks at 99% from time to times. A full scan with everything maxed out (sensibility, whole file testing etc) still hangs at 0%.
Three boots later, Avast 2014.9.0.2016 on Win7 SP1 with rootkit scan enabled, everything seems fine.
I guess the issue’s been corrected for me.
Thanks a lot to edialchu for having alerted on the rootkit scan, to DavidR for the 8 minutes root kit scan delay, and to jaroslav.nix + gmer + the avast team for having considered our troubles !