129260, I’m reading the last posts… but for sure I can’t help with AOL things… I never used their software (not that famous for being good ones).
Did you submit the files to Alwil team for analysis?
Ya, well I’m getting high speed soon, but other people who use this computer prefer aol, so i leave in installed. yes i did. Email says it was successfully sent 
Still haven’t received any word. I cant send the files because it wont let me submit anything, it wont let me submit what avast calls the infected file…because it doesn’t show up in Avast’s logs to submit. Nothing in the avast log viewer or anything indicate the infection or warning from the message i am getting…I just posted a link to this thread in the email.
I said this in a post :“I sent an email to virus (at) avast.com and in the subject i put false positive? and i gave a link to this thread.” just in case u missed it 
Thanks for your response! I appreciate it!
so any more word yet? And if you someone responds if you read the first page you will know whats going on better. thanks for your time, i am looking forward to a solution to these problems.
anyone have any more ideas?
Unfortunately not the new rootkit module is still a bit of a mystery to the avast users who have tried to help, we too are waiting for some input from those who might know, the Alwil team, we feel your frustration.
thanks I am just glad someone replied. I’m trying to keep my post near the top so hopefully someone from the avast team will see it. Thanks very much.
UPDATE!!: I had a bright idea-As of now, I have selected in msconfig and told it to not allow aol to start with the system. Since then, I have not received the rootkit issue! However, that is a temporary workaround until someone can really find out why avast thinks its a rootkit.
The aol processes that start up with the system (that i now disabled) were:
Aol dial (helps aol dial into the Internet)
Aol host manager (which puts the aol icon in the notification area.)
Maybe that will help. Aol version is 9.0 security edition. Also, The scanning issue still exists, minor issue but should be looked into. Thanks for your reply, and even though were frustrated, at least were frustrated together haha. thanks for your reply!!
so anyone have any more ideas? haha.
I’d suggest updating to the new build 4.8.1195, and when the message comes up next time, check the “Do not tell me about this rootkit anymore” and click Ignore.
That should basically “resolve” the issue…
Cheers
Vlk
Thanks Vlk, I hope that resolves 129260’s problem and frustration.
ok thanks very much. I will if it comes up again. The scanning issue with the go to background has also been resolved with the latest database update…weird. Thanks very much everyone. This issue,(or rather issues,) is now resolved Thanks to everyone so much. This thread can now be closed. WOHOOOOO!! GO AVAST!!
Glad that you stuck with it, worth it in the end.
yes very, I was very patient wasn’t i? lol. I surprised myself a little. haha. I guess because it was just minor issues, i could deal with them and gave patience. haha. Thanks to everyone, avast forever!!
Can you test if the latest 4.8.1195 solve this problem?
I’m about to reboot with the new avast version…BUT Solved which problem? It no longer freezes during scan with the latest virus database update. And as for the rootkit issue, i stopped receiving them when i kept Aol from booting with the system. I said that in a post somewhere, i guess you missed it. The limited user accounts can still use aol without it booting with the system. Everyone wins!!