![avast error message about endpoint avast error message about endpoint](https://www.antivirussupporthelpdesk.com/blog/wp-content/uploads/2021/01/How-to-troubleshoot-Avast-Error-Code-7005.jpg)
- #AVAST ERROR MESSAGE ABOUT ENDPOINT PRO#
- #AVAST ERROR MESSAGE ABOUT ENDPOINT DOWNLOAD#
- #AVAST ERROR MESSAGE ABOUT ENDPOINT WINDOWS#
![avast error message about endpoint avast error message about endpoint](https://i.pcmag.com/imagery/reviews/019nOSIdfbjFzRmSdC7Ce5C-32.fit_scale.size_760x427.v1641511250.png)
There are many other identically-configured machines on which the problem never occurred during a 15-day period while Version 8.x EndPoint clients became available and before I turned off automatic program updates on the console. The problem was seen on workstations with either of the OSes listed, and any of the email clients listed, when connecting to any of the three POP/SMTP servers. There is no consistency in terms of which OS or email clients were used.
#AVAST ERROR MESSAGE ABOUT ENDPOINT DOWNLOAD#
When it did not work, the Avast! “Mail Shield Security Exclusion” window would reappear when a user tried to download or send email using one or more of the three possible POP/SMTP servers, as soon as on the next attempt, or as late as 2-3 days later, after several successful attempts. And finally, pressing the button to record the exclusion worked permanently on some workstations but not others. Also, the problem did not always occur on first use of an email client after the EndPoint update. I emphasize that this problem occurred only for SOME, not all, workstations that were updated to EndPoint version 8.x.
#AVAST ERROR MESSAGE ABOUT ENDPOINT WINDOWS#
I believe that all of the certificates were in fact valid.įor Thunderbird clients, these messages always caused a Windows Program Error, and in one case, a C5 crash error. Even if the LAN server certificate was questionable, the other two could not be. The third was hosted by Time Warner Cable (“RoadRunner”), a widely-recognized major ISP. A second was external and hosted by a fairly small, but reputable, email service provider.
![avast error message about endpoint avast error message about endpoint](https://static.avast.com/support/kb/images/v2021/avkb86/en/v1_and_apps.png)
One server was internal and hosted on my LAN. I do not know what criteria Avast! uses to assess certificate validity, but the certificates of three different sets of POP/SMTP servers were reported as “invalid” and “not trusted” within seconds of each other, so I strongly suspect that those criteria are bogus. When the actual certificate is viewed using the option available in the “Mail Shield Security Exclusion” window, it is always UNexpired. If that button is pressed, another Avast! window appears saying that Avast! has a “new way” to scan SSL emails, and advising the user to turn on SSL email connections in the email client. However, pressing this button does not always permanently stop these messages from appearing. ” The window also says, “This site attempts to identify itself with invalid information,” and “The certificate is not trusted.” This window contains a button whose label indicates that pressing it will permanently record an “exclusion” for the certificate. OBSERVED BEHAVIOR: After workstation EndPoint clients were updated from version 7.x to version 8.x, some users began seeing Avast! “Mail Shield Security Exclusion” windows, which displayed a message that “Avast! has identified a problem with site certificate. Avast! was administered on a network using an “administration console” (type/version is irrelevant) that was set up to push EndPoint client Program updates automatically. The servers do not require or support SSL/TLS connections. All email clients are set to connect to these servers WITHOUT SSL or TLS.
![avast error message about endpoint avast error message about endpoint](https://media.cybernews.com/images/featured/2021/12/Avast-2.png)
Three different sets of POP/SMTP servers are used.
#AVAST ERROR MESSAGE ABOUT ENDPOINT PRO#
Although the entire post is less than 10,000 characters, including spaces, the Forum software insists it exceeds the 10,000 character limit.Īfter dealing with this issue for nearly a month, and finding an interim work-around with much effort, I’m summarizing the issue here.ĮNVIRONMENT: Workstations running 32-bit Windows XP Pro or Windows 7 Ultimate (with and without SP1), using any of these email clients: Outlook Express 6 Eudora 5.x, 6.x, 7.x Thunderbird 2.x.