Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: warlock on February 27, 2012, 11:14:55 PM
-
After a reinstall from scratch (ran aswclear) I can't get Mail Shield to run even after several reinstalls. The shield status is showing: Please run the avast! service first to run this shield. Of course the service is running (and all the other shields too). The Mail.log file contains only:
27.2.2012 22:41:39 000006F4: Started, Log = 1
27.2.2012 22:41:39 000006F4: Build 7.0.1407
27.2.2012 22:41:39 000006F4: OS Windows 7 Workstation (Service Pack 1)
27.2.2012 22:41:39 000006F4: tdi.Initialize failed
27.2.2012 22:41:39 000006F4: Stopped
27.2.2012 22:41:40 000006F4: CATCH (...) in MainLoop
27.2.2012 22:41:40 000006F4: CATCH (...) in DeInitApp
Weird thing is the setup log contains this:27.02.2012 21:39:36.000 1330375176 (null) Service avast! Mail Scanner uninstalled even though it is the log for the install run. This is the only mention of the Mail scanner in the whole log file.
-
I forget which topic it was in, but I found a solution that worked.
Run aswclear again, then before you restart, open C:\Windows\system\drivers and look for any leftover files starting with "asw" and ending with ".sys". Deleting those, restarting and installing once more fixed this for me.
-
I've unstalled and reinstalled three times without success. No aws* files in the driver directory. Same problem. Click on FIX ON does nothing. Any other suggestions? Thanks.
-
Same problem here.
This is from the log Mail.log.
2/27/2012 7:22:14 AM 00000774: Started, Log = 1
2/27/2012 7:22:14 AM 00000774: Build 7.0.1407
2/27/2012 7:22:14 AM 00000774: OS Windows 7 Workstation (Service Pack 1)
2/27/2012 7:22:14 AM 00000774: tdi.Initialize failed
2/27/2012 7:22:14 AM 00000774: Stopped
2/27/2012 7:22:14 AM 00000774: CATCH (...) in MainLoop
2/27/2012 7:22:14 AM 00000774: CATCH (...) in DeInitApp
2/27/2012 6:35:38 PM 00000790: Started, Log = 1
2/27/2012 6:35:38 PM 00000790: Build 7.0.1407
2/27/2012 6:35:38 PM 00000790: OS Windows 7 Workstation (Service Pack 1)
2/27/2012 6:35:38 PM 00000790: tdi.Initialize failed
2/27/2012 6:35:38 PM 00000790: Stopped
2/27/2012 6:35:38 PM 00000790: CATCH (...) in MainLoop
2/27/2012 6:35:38 PM 00000790: CATCH (...) in DeInitApp
This happens when I install from Safe mode. I can never get a successful install in normal windows mode. Gets stuck on installing the firewall NDIS driver.
Definitely serious problems with Avast's install process. Perhaps the project was to ambitious for the resources at hand.
-
Hi guys, thanks for your logs. It seems to me that the line: Tdi Initialize failed. is going to be the rpoblem. I will look at the code a try to find out what might be causing it - as soon as the sun rises.
lukas
-
Hi
Mail Shield down and real time shield not working. Please fix this very urgently.
-
Same problem here.
I solved this by installing avast 6 and an upgrade to avast 7. After that, avast 7 is running fine...
-
I got the same problem here with Windows 7, but I didn't install it on Safe Mode.
-
Same problem. Windows 7 Professional x64 SP1 Russian. Uninstalled avast 6 in safe mode using Avast Uninstall Utility (was having problems with auto update hanging). Rebooted in normal mode, downloaded installer, installed and mail shield won't start.
Thought it could be related to the problem with the update hanging, so I downloaded the fix released yesterday but it returned error 11 which means that there is no problem for that fix to fix.
I don't have real need in mail shield but it's a bug that should be fixed :)
-
After aswclear under Windows Safe Mode, search for possible remnant folders "avast*" or "alwil*" and delete them.
Also look into "C:/windows/system32/drivers/" for avast drivers left starting with "asw*", specially "aswdrd2.sys. Delete them.
Now reboot into Normal Mode and install avast.
A new program update will also come soon.
-
Success on 10th try. Didn't change anything or deleted anything manually (on first try I checked the drivers folder, but there was nothing there, even checked the driver keys in registry, but there were no orphaned avast entries), just did install -> uninstall (+ aswclear) 9 times and on 10th install everything started working, so no clue what the issue is.
-
Hi guys,
we have finally found the problem that is causing this bug.
One driver that is needed for correct startup of MailShield (and also for correct operation of WebShield) is incorrectly installed. (on Win7 only)
It is caused by the aswclear ver. 6, that is unaware of the fact, that it has been renamed in Avast7 for Win7 OSs to aswrdr2.sys and leaves it there on the system, which again (and this is probably a bug) causes setup not to install it correctly next time.
We will fix it in the next build, for now, please use the following .reg file to import the missing settings into the registry. (please note, you will have to disable Avast Self-Defense features before the import and re-enable it after).
Steps:
1) Go to settings/troubleshooting and uncheck "Enable Avast! Self-defense module"
2) Download the following link and open it - click on it. The message box appear informing you that this will change registry. Click Yes.
http://public.avast.com/~rypacek/aswrdr/aswrdr-win7-installation-fix.reg
3) After successful registry import, you should see another message box confirming it. It it shows an error, probably you haven't gone through the step 1.
4) Re-enable avast! self defense, similary to step 1
5) reboot
Lukas.
-
lukor, no issues here for me with the mail shield on a completely clean install of the latest 7 installer so would there be any benifit in myself running this fix - or not needed ? more so for the reason that you say this affected the webshield as well.
-
I also can't start Mail shield.
EDIT: Finally fixed. Thanks
-
Danny96, thanks for the edit, I was a little surprised that the fix did not help for you.
Lukas.
-
Danny96, thanks for the edit, I was a little surprised that the fix did not help for you.
Lukas.
I think he originally posted before running the fix.
Is this fix worth running even if there are no noticable problems Lukas?
-
If posted before fix, that it has no value.
This fix only installs aswrdr driver, if it was not installed correctly. Works only on Windows7, where the problem is found - or more precisely it *SHOULD NOT* be run on other system. Also, if you don't see such problems (e.g. Mail Shield is started, Web Shield shows scanned URL) there is no point of running the fix - it won't do a thing.
-
No worries, thanks for the reply :)
-
So there wili be an update to fix that available via autoupdate? I don't need to fix that immediately but I don't want my current avast installation to be corrupted in any way.
-
I don't understand the question. Is your avast installation corrupted?
-
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?
-
We will fix it in the next build, for now, please use the following .reg file to import the missing settings into the registry.
-
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 :)
-
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?
-
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,
For some drivers, special registration in other places is needed (e.g. NDIS driver) but this is not the case here.
that is actually the part I was wondering about. Thanks for your explanation!