Your welcome. 
Had the same problem but right clicking on the avast icon > program settings> exclusions
browse to Program Files/Comodo directory to exclude the Comodo directory from scanning by avast seems to have corrected the problem.
Maureen
does it correct the slow initialization problem with CPF? if so, i’ll try it.
sadly it didn’t work on mine. i’ll just have to wait for another version i guess. all i can do now is just close out and re-start the firewall after a cold boot, which is when this seems to occur most of the time for me.
It works everytime for me… just make sure you are excluding the whole Comodo Directory.
You may also want to exclude any other trusted application directories that load on startup because Avast is scanning these on startup
See my reply above regarding excluding other trusted apps in avast that run on windows startup.
Please make sure you are excluding the apps whole directory and not just the exe.
HTH Maureen
C:\Program Files\Comodo*
C:\Program Files\Spyware Terminator*
C:\Program Files\Cobian backup*
C:\Program Files\Rainlendar*
Check the way your path is displaed!
These are the way the directory paths under Exclusions in Avast should be displayed.
Maureen
Good call Maureen.
I did this yesterday and as of yet have not seen this problem reappear.
Philbee are you sure you are putting this in the correct exclusions list ?
Just asking as I know that some people mistakingly put things in the scanning exclusions list rather than the program settings exclusion list.
I know that I did this myself when I first started using Avast, so thought I would mention it just in case.
Luxor
Thanks Luxor… glad it’s working for you
i did put it in the program settings exclusion list, and it didn’t work. maybe you can elaborate a little more where that list is in avast.
strangely enough, i find that the problem with comodo seems to have improved once i set avast for manual updates only! this is a very weird problem, because it seems completely random, with no predictibility whatsoever. the problem on my computer was unaffected by excluding comodo from scanning by avast in the program settings.
i did put it in the program settings exclusion list, and it didn't work. maybe you can elaborate a little more where that list is in avast.
Sure though it is probably the very steps you have taken yourself.
Right click on the Avast icon in the task bar.
Select On-Access Protection Control
On the screen that opens select Standard Shield
Then click on Customize on the next window select Advanced.
Click on ADD and insert C:\Program Files\Comodo*
Then click on OK and that’s it done.
Luxor
thanks! i’ll try it.
okeedokee i made the change. now we’ll see what happens. i was using the wrong exclusion list. the one in program settings, rather than for standard shield. this might be a good workaround until they come up with a version of CPF that doesn’t have the bug.
does it affect manual scans of avast? if comodo ever contracted a virus, i would want it detected, at least in a manual scan by avast.
Hi Philbee
Wrong exclusion list, easy mistake to make. Been there done that.
No this will not (should not) have any affect on your manual scans.
You will still be well protected.
Hope it has the desired effect for you.
Luxor
so far so good! after such a long time with no workaround for this, we might have finally discovered one that works till they come up with an update without this problem. thank u so much, maureen and luxor!
just wanted to say that i haven’t had the slow initialization problem at all since folllowing luxor’s and maureen’s workaround. while i am hoping it will be corrected completely in the next version, in the meantime i am glad to say everything is working perfectly! thank u, maureen and luxor!
just wanted to say that i haven't had the slow initialization problem at all since folllowing luxor's and maureen's workaround. while i am hoping it will be corrected completely in the next version, in the meantime i am glad to say everything is working perfectly! thank u, maureen and luxor!
(:CLP)
Glad to have helped. But most of the credit goes to Maureen.
Luxor
thank u maureen also!
Sorry to resurrect this, but I just noticed this message this morning
(never really looked for it before, so I can’t tell you if it used to happen)
I’m using WinXP Home, all latest patches.
I am NOT using Avast - still using AVG
I saw the message stuck on a reboot immediately following the latest Auto Update to 2.4.17.183, although the system ‘seemed’ to be performing normally anyway.
No significant Log messages during boot time. Just a couple of ICMP Medium alerts ‘around’ that time, but not until about 5 minutes after boot.
Restarting Comodo Firewall manually made the message go away.
Is anybody else still seeing it?