Author Topic: ERROR message #10022  (Read 5864 times)

0 Members and 1 Guest are viewing this topic.

farleyland

  • Guest
ERROR message #10022
« on: January 04, 2006, 02:39:27 AM »
just recently, after an Avast! update, I started receiving these messages...
       ERROR: 10022 Avast! will not be able to protect incoming mail (IMAP protocol);
       ERROR: 10022 Avast! will not be able to protect news (NNTP protocol);
       ERROR: 10022 Avast! will not be able to protect outgoing mail (SMPT protocol); and
       ERROR: 10022 Avast! will not be able to protect incoming mail (P0P3 protocol)...

all come when I turn on the computer and all at the same time... as I am new to all this, I have no idea where or how to begin... I have a Dell Dimension 2400 with 256k celeron processor, dial up and use both Outlook Express & Incredimail, and have McAfee (came with computer) as well.

any help would be appreciated

Offline TedNelly

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 1538
  • Trust No-One!
Re: ERROR message #10022
« Reply #1 on: January 04, 2006, 11:24:45 AM »

Welcome to the Avast forum farleyland

Do you have another AV  installed? Maybe McAfee if you do you would need to remove it prior to Avast Install
Error 10022 means:  invalid argument  supplied (WSAEINVAL)

Have a look here
http://forum.avast.com/index.php?board=2;action=display;threadid=4279
http://forum.avast.com/index.php?board=2;action=display;threadid=2760
http://forum.avast.com/index.php?board=2;action=display;threadid=5595
« Last Edit: January 04, 2006, 11:26:38 AM by p3t3rb0nn »
Windows 10 Pro | Intel I7 CPU | 16 Gig 2133 RAM | Avast beta 17.5.2295 | Firefox 54 b9(64-bit) | Cyberfox 52.1 | T-Bird 52.1.1 | SpyWareBlaster 5.5 | MalwareBytes 3.0.0.865 | WinPatrol 35.5.2 | GlassWire 1.2.100 | Cybereason Ransomfree 2.2.7 |  Pulla-dePlug Final!

farleyland

  • Guest
Re: ERROR message #10022
« Reply #2 on: January 09, 2006, 12:51:15 AM »
thanx for the welcome and for the info/links!

problem still there but muddling through...

yes, have McAfee... both worked well together until recent update in Advast!...

in addition, have now noiticed issues with receiving e-mails through MS Outlook Express... may have been there all along, don't know!  Incredimail works fine!

if nothing else, will dump them all and reinstall!

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 89116
  • No support PMs thanks
Re: ERROR message #10022
« Reply #3 on: January 09, 2006, 01:38:48 AM »
Having two resident AVs is not advisable, there really is more chance of conflict rather than twice the protection. avast when installed on occasion wouldn't completely install if it detects another resident AV to avoid conflict and potential lock-up of the system. I'm surprised that you have managed to co-exist for so long.

I would recommend you uninstall both as you suggest, reboot and install whichever one you decide on. If nothing else it is likely to make any troubleshooting easier.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.3.6108 (build 24.3.8975.762) UI 1.0.801/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Lemon

  • Guest
Re: ERROR message #10022
« Reply #4 on: February 14, 2006, 11:36:19 AM »
I also got those error messages #10022 at startup. I found this solution, which worked for me.

In my Firewall (McAfee Personal Firewall Plus) I changed the Application rule for avast! e-Mail Scanner Service ashMaiSv.exe to Allow Full Access (was: Outbound Access Only). Now the error messages don't show up again, and the mail scanner is working fine (with Thunderbird btw).

So, maybe you could try change settings in your firewall too.
Good luck,'


CharleyO

  • Guest
Re: ERROR message #10022
« Reply #5 on: February 14, 2006, 06:20:07 PM »
***

Welcome to the forums, Lemon!    :)

Thanks for the post as it may well help someone.

Please come back often, learn more, and maybe help someone else.    ;)


***