ashMaiSv.exe adds itself to startup a lot

Hello everyone. I’m another new convert to avast! from AVG. I’ve been using avast! 4.8 professional for two days. I’ve explored the menus, configured options, solved problems, and I’m pretty happy. I’m running Windows 98, POPFile, ZoneAlarm, and Eudora. Avast! is one of the few good antivirus programs that still supports Windows 98. Thanks!

I use a small free program called Startup Monitor that lets me approve or deny a program’s attempt to add itself to the startup list. I allowed ashMaiSv.exe to add itself to startup and it works fine. It is scanning both incoming and outgoing mail.

The problem is that ashMaiSv.exe keeps adding itself to the startup list even though it’s already there. It has added itself at least nine times in two days. I always allow it. Running msconfig and looking at the startup list shows ashMaiSv with a check mark. Everything’s fine except it keeps adding itself.

During installation, in the email configuration wizard I checked the box that said I wanted avast! to scan the mail in any new mail accounts I add. (The default was unchecked.) I suspect setting that option causes avast! to check for new accounts periodically. Could that be causing this strange behavior? I’m hoping. :wink:

I might go for years before I set up another mail account, so if checking that box is causing this problem is there a way I can turn that option off?

Is there a line I can change in avast4.ini to stop ashMaiSv from repeatedly adding itself to startup?

Thanks.

Jon

You are right that it is caused by the option to protect future accounts. You can start the wizard again from menu Start->Programs->avast! Antivirus and let the option unchecked.

I made the change about 8 hours ago and ashMaiSv has not tried to add itself to startup. Mail is still being scanned properly. Thank you, vojtech!

vojtech,

may it be assumed that this could only be an issue for users of Win9x systems?

Yes, it is related to Win9x only. Normally it’s not even an issue because avast creates the same registry value every time so nothing is growing. Just that the Startup Monitor is reporting it.