[Avast 7] Mail Shield won't start

I mean the mail shield not starting. As far as I understood from discussion it is caused by v6 uninstall and v7 install done slightly incorrect so that some v6 files were left and v7 did not overwrite them and thus I think it’s legit to call my current v7 installation corrupted.

So the question was if this issue is going to be fixed by updates available via autoupdate?

Yes, thank you, I’ve read it already when you first posted this. I did not understand what the “next build” stands for. So I’ll repeat my question once more - will it be available via autoupdate?

Answer “yes” or “no” would suffice.

Yes. autoupdate updates to the next build.

Lukor,

Like everyone else, I had the no update issue. Uninstall and re-install in safe mode worked but left the mail shield unable to start. Your link and reg fix worked like a charm. All is well with 7 now and the auto updated worked this morning as well. Many thanks!

Thanks Dreamchick for the info.

Thanks for the information, lukor!

thankyou Lukor, after auto update my system was lagging very slow, I did a clear then manual install but mailshield could not turn on… but the registry fix worked! and mail shield now displays as working i.e. system fully protected.

I do have some questions though. I use online email services only via firefox browser (no outlook or anything like that on my netbook). Does the mailshield have any benefit for me, or can it be disabled to free up resources (and if so, is it possible to do this without invoking a permanent alert exclamation on the tray icon - which if I ignore might hide other problem alerts if they occur. Hope this makes sense.

my spec
windows 7 Starter, 1gb ram, dell netbook, starving student

slonje, if you never use mail clients on your computer, mail shield (and spam shield as well) will not do you any good. It would never be trigered. It might be in effect only randomly, while some other apps you use conect via mail protocols.

If you choose to turn it off, go to settings / status bar and deactivate MailShield monitoring. This will hide the exclamation point from the notification area icon.

Thanks for clarifying that mailshield question for me, much appreciated :slight_smile:

Hi lukor,

are you sure the .reg file will fix the problem in any case? When we first analyzed the problem in the German forums before we recommended the workaround to delete the aswRdr2.sys here, the user who reported the problem, also returned the list of installed filters to us. It seems he was also missing a properly registered filter, not only the service. Check the filters.xml output here: http://forum.avadas.de/threads/4011-avast!-7-Web-Schutz-funktioniert-nicht?p=36140&viewfull=1#post36140 (the topic was related to the web-shield, which uses the same service/redirection filter). Or does the filter autmatically get registered by the service spinning up?

Either delete aswrdr2.sys and reinstall, or install it via the supplied reg file and reboot.

Hi lukor,

I know how to fix this, the question was more technically related. As far as I understand, not only a service is registered, but also a filter needs to be registered (also listed in the device manager / hidden devices). My questions was, if those entries are made when the service is starting, in other words by the service itself, because the .reg just seems to create the service entry.

What do you mean by “service is registered” and “filter is registered”? Could you be more specific? Please.

L.

Just a question here. I have not had the problem but I downloaded the reg fix file just to compare it’s contents to what is actually in my registry. Everything is the same except for one entry. On my system, Win 7 Home premium 64 SP1, the entry DependOn Service just says tcpip with none of the hex and numbers shown in the fix file. Everything is working perfectly though.

This is simply the way how regedit export REG_MULTI_SZ fields. Try to export yours and compare both files.

2 avast.de> you must be confused. The driver is installed by the registry entries in .reg file (this is one of the ways). No other installation is necessary if you reboot afterwards (since the registry is loaded on system startup). There are other ways of installing drivers/services but all eventually lead to the following entries written into the registry. For some drivers, special registration in other places is needed (e.g. NDIS driver) but this is not the case here.

Won’t it be good to upgrade to the latest beta?

Since I’m having no problems, I’m waiting until the release. I do like what VLK said though about the Ask mode in the auto-sandbox being changed back to how it worked in v6. I don’t care about the gadget fix since I never use any gadgets and don’t even have the Avast one at all.

Hi lukor,

that is actually the part I was wondering about. Thanks for your explanation!