Hello, I’ve been using avast! free (version: 10.3.2225) on a Windows XP desktop running Outlook 2010.
I experience some bad bad behavior from avast!, namely it will rename attachments to: “Untitled attachment NNNNN.ext” where NNNNN is a 5-digit number (prefixed with zeros if needed) and .ext it’s the original file’s extension (phew!).
Example case:
Suppose, I expected to receive an e-mail containing many PDF attachments one of which would have been something like MonthlyReport.pdf. Unfortunately I would have to find out, using certainly non-productive means, which file is which thus rendering the use of !avast if this goes on, inappropriate.
I’ve tried to disable the e-mail protection from within !avast which did not work and I think that for now I will disable Outlook’s add-in permanently.
Is this something that this is how it was designed to be?
Am I missing some combination of options?
Plus the previously mentioned dll is registered to Class ID:
{B342E21B-AD7E-4568-AE3F-D0D844537A7A}
and the registration date matches the date of !avast’s installation.
I’ve posted a SHA1SUM of the .dll in question.
I’ve also added that the .dll in question, has been registered the same date !avast free was installed, to which you reply again, that this is not part of the normal !avast free installation, suspecting this .dll is malicious I’ll proceed to a complete uninstallation and re-installation of !avast free and keep detailed installation logs which I will post back here.
A screenshot of what?
There are numerous settings for e-mail protection in !avast’s settings.
Namely in: Settings → Active Protection → E-mail Shield.
Is it possible that you could supply a SHA1SUM of your .dll or at least could you confirm it matches the one I’ve posted?
Not sure about how to generate a SHA1SUM (but willing to try with guidance). For what it is worth, the file asOutExt.dll is digitally signed by Avast and reports size as 462,328 bytes, with size on disc as 462,848 bytes. As in your case, the time and date stamp is consistent with the other files in the directory. My memory - which is very fallible - is that there has always been an Avast add-in in my Outlook.
Did the file asOutExt.dll reappear when you reinstalled Avast free?
Do you still have problems with attachments being renamed? You will remember that wasn’t a problem that I have here. I wondered if the new version of the file asOutExt.dll on your system was the same SHA1SUM as the old, or whether the previous one might have been corrupted? If it was corrupted my SHA1SUM wouldn’t match yours.
I do, and what is odd is that I still experience this even after disabling that particular Outlook add-on.
You haven’t yet confirmed that SHA1SUM or posted your own.
After ruling out it was anti-virus software’s fault and a series of tests conducted with various names on attachments, I have concluded that the reported behavior is not valid.
Therefore, cease the alarm, and thanks to everyone who has participated in this thread and helping me out.