avast! free 6.0.1000 error 80004003 on send/receive email

I am getting error 80004003 when i send or receive email. Here is what happened.

  1. On my windows 2000 pro SP4 system I updated the avast! Free program to version 6.0.1000. I did the requested reboot. Then i tried to receive email using Outlook 2002 SP3. Up came a dialog that said:
    “”"
    avast! cannot scan the message body.
    Error code is 80004003.
    Invalid pointer
    AavmCheckFile failed.
    “”"

  2. I closed and reopened Outlook. The avast plugin splash screen showed up when Outlook reopened. I tried to send an email. The email wouldn’t go until i noticed that the same dialog as before came up. I clicked OK on the dialog and the email got sent successfully.

  3. I tried to log into support to write a ticket but it said I couldn’t.

  4. I searched this forum for ‘error version “6.0.1000”’ The only even mildly related hit was here http://forum.avast.com/index.php?topic=72300.msg602964#msg602964

Does anybody have any ideas. I am depending on avast! to scan my emails.

Thanks for the help in advance.

Love and peace,

Joe

Each time I send or receive an email with an attached file using Outlook 2000, I get a message similar to yours : “avast!: Cannot scan a message attachment. Error code is 80004003 Invalid pointer”.
Did you ever get an answer or resolve this issue?

:cry: No. I reinstalled 6.0.1000 from a fresh download and still had the problem dialog come up when i tried to send or receive email:
“”"
avast! cannot scan the message body.
Error code is 80004003.
Invalid pointer
AavmCheckFile failed.
“”"
I am trying to find a copy of the 5.1.889 download so i can reinstall this, but when i click on it at CNET, what comes down is the 6.0.1000 version. :stuck_out_tongue:

I hope someone is moderating these posts. You are the only responder so far.

DOES ANY ONE OUT THERE HAVE ANY IDEAS? :slight_smile:

I hope that gets their attention. :slight_smile:

Love and peace,

Joe

I just submitted a ticket to Support referring to this thread.

Ticket ID: XFB-100915
Department: [ENG] Technical support
Priority: Medium
Status: Received
Created On: 01.03.2011 20:38

I’ll try to remember to post back to this thread anything i hear from Support.

Love and peace,

Joe
:slight_smile:

Thanks, Joe. It’s hard to believe that you and I are the only ones having this issue. And it is a very annoying problem.
Please let me know if you get a response from Avast.
Thanks.
Bob

Dear Bob and All :slight_smile:

I got this answer from the Ticket that I submitted:

Tomas Zajic
Posted On: 02.03.2011 15:41
Hello,

unfortunately this is kind of issue that we are not able to fully fixed because this issue could be cause by outlook settings, configuration or various add-ins that can be installed into outlook. You can try this work around and if it is not help you can try disable / test add-ins in your outlook if there is some interference.

Here is the work around:

  1. uninstall avast6 - you should use our removal utility
    ( http://files.avast.com/files/eng/aswclear6.exe )

  2. restart

  3. Turn off Windows firewall

  4. then clear all off-line content and cookies form your web browser, clear/delete temp files and download our new release
    http://www.avast.com/download-software

and install it.

After successful installation could you double click on you license file to register your copy of avast.

  1. Turn on Windows firewall

Best regards,

ALWIL Software a.s. support team

========================================
joe’s reply to the ticket response

jdorocak
Posted On: 05.03.2011 21:36
Thanks Tomas,

It is working right now, with version 5.0.677 which i installed. I’ll try to get around to doing your workaround soon.

By the way, any idea why when trying to download version 5.1.889, 6.0.1000 came down instead?

Thanks for the help, Tomas.

Love and peace,

Joe

I’ve been having this problem too, ever since I upgraded to v6.

It seems that the trouble is that Avast v6 no longer supports Win 2K (look at the System Requirements here).

I’ve reverted to 5.1.889 and this works OK.

Joe- Please let me know how you make out with Tomas’s work around if and when you try it out.
Thanks.
Bob

rrtash, I did try that process (uninstall, clear cookies etc, reinstall) and no success.

I too am using Windows 2k/Outlook 2k like the o.p. As Avast say that 6.1 does not support Win 2k, I do not think they will fix this problem for me.

Same set up, same problem.

Not very happy with the ‘Fix’ from technical support that doesn’t work!

Can we have an answer on Windows 2000 support?
There’s still a lot of people out there using it.

You can download Avast Free from http://www.filehippo.com/download_avast_antivirus/9090/

The ‘fix’ is, apparently to remove Avast Anti-Spam - either from the add-in on Outlook (depending on your version) or by disabling it as a custom option on a re-install.

I’ve not tried this, as I tried it in 'Change/Remove program and the option was not available to me, which may be down to this being another bit of duff advice from tech support or because it is only an option on a re-install.

Initially, tech support did not answer (understand?) my questions so I had to repeat them:

“Is it possible to explain a procedure that works for Office XP - Outlook 2002 SP3”?

“Will the next version of Avast incorporate a fix”?

  • most probably not on Windows 2000 as it is quite old operating system.

There you have it.

The alternative is to just disable e-mail scanning from within the Avast control panel.

I too am using W2000 SP4 (only 1 user) and Outlook 2003 and have been keeping up with the latest avast upgrades. After doing the avast latest upgrade yesterday (one where I had to reboot), I also started getting the 80004003 error.

I don’t think that I should now have to start making changes to security policies. While looking up what version of Outlook I’m using, it seems to have crashed in the process. It’s very annoying to have this error keep coming up with every send & receive.

Your web site show that the v6 system requirements are only W 7, W Vista, and W XP. Is there a simple to work around this problem without having to upgrade to W XP?

I’ve upgraded to Windows XP Pro (SP3) and no longer have this issue.