When the new Avast was released (Avast 4.8 was installed at the time) I downloaded it on my parent’s computer and had difficulty with email connection. (Dual core, Vista OS) There did not appear to be any solution to the problem on the horizon, so I removed the “new Avast” and reinstalled Avast 4.8.
Today, many months later, I removed Avast 4.8 and downloaded the current version of Avast and have experienced the same problem with email connection.??? After all of this time I had hoped that this problem had been resolved.
Can you please be of assistance or will I, once again, have to remove the current Avast installation.
Your assistance with this problem would greatly be appreciated.
Thank you!
Error Message!
Unable to send or receive messages for the shawmail.ed.shawcable.net account. An unknown error has occurred.
Server Response: ready
Server: ‘shawmail.ed.shawcable.net’
Windows Live Mail Error ID: 0x800CCC93
Protocol: POP3
Port: 110
Secure(SSL): No
Please Note:While searching this forum it appeared that someone else had a similar problem. It was suggested that they download aswclear5 to the desktop, reboot in Safe Mode, run aswclear5 to remove all traces of Avast, reboot and then reinstall Avast from the provided link.
I did so and the result remained unchanged-- still no email connectivity? However, if I disable, the Mail Shield, I do get connectivity and can send and receive email?
I’m not sure if this will help but I noticed you followed the correct procedure for using Avast5 removal tool and then reinstalling however I believe when you run the removal tool there is a choice for Avast 4.8 and Avast 5. When you uninstalled your v.4.8 did you choose that option in the process. I think (unless I’m mistaking…wouldn’t be the first time)you have to chose corrisponding version to clean up that versions reminents…I think :-\
Don’t worry, schmidthouse. You’re right about this…
As there are some installs/uninstalls of both versions involved, best is to run the uninstall tool for both versions and do a clean install afterwards.
asyn