10104 error on mail shield

Hi

I encounter some trouble with the 4.7.827 version (french one)
At windows start up, I get a message telling it cannot scan pop, smtp, nntp port.
it’s a windows 2000.

It’s not definitely a big trouble as I don’t use a mail client but, I cannot find out why I get that.
I’ve tried to reinstall avast, scan hard disk, eradicate pests, spy and adaware but I still have the same msg.

Do you have any idea ?

thanks


Puppy

This is usually a symptom of another AV or program doing the same task as the avast email scanner.

Have (or did) you have another AV installed in this system, if so what and how did you get rid of it ?

Do you have any other program that also scans emails, firewall, etc ?

It’s not my computer in fact, but I check no other AV installed. I desinstall avast through windows control panel and reinstall it.
No fw, no other mail scanning.

but you may right, it may be a question of pest or even virus (not detected so far) that have blocked access to mail scan.

thanks for your support.

Puppy

but I check no other AV installed
Not just currently installed, but also previously installed, some elements may remain after an uninstall that are detected by avast. So did you have another AV previously installed in this system ?

I doubt it is a virus as it would be strange for it to subjectively select only the email provider and not the main scanning element of avast.

Is the Internet mail provider active, left click the avast icon and check the list of providers if the Internet Mail is greyed out it isn’t active, you could manually start it from here. You will be asked if you want the changes to persist, click Yes.

If that doesn’t resolve it (which I think unlikely) then the only thing I can suggest it to reinstall. Uninstall, reboot, install, reboot.
It would probably be best to download the latest version of avast and save it to your HDD, somewhere you can find it again. Use that when you reinstall.

Edit: Checking a little further if this error is a windows one, 10104 = The procedure call table is invalid. If this is correct it could be a bad install, hopefully a reinstall as above should help.