Thank you for updating…what is the workaround that you mention in your post?
I attempted to log in today and I keep receiving the error “…compliance requires full system scan…” from our Juniper.
Of course, complete scan (no exclusions), AV up to date, Windows patch up to date etc, etc.
One of our firewall admins sent me the “approved vendor list” and Avast! 7.x appeared therein but none of us using the product can get past Juniper.
Any recommendations?
Juniper Host Checker version 7, 1, 0, 20169
Avast! version 7.0.1456
WindowsXP Pro SP3
@mtaylor - the thread history of avast is stored in several files in the ProgramData directory. We provided a way how to get this info to Opswat guys who are certifying the product(s). Juniper only takes the list of certified programs and the OESIS framework from Opswat. Therefore there might be some time between the certification and the update which contains the changes. OTOH, I don’t have any replies from them from the time when we provided it to them…
Looks like ESAP 2.2.3 might have improved some things.
Haven’t tried it yet, but at least this note is encouraging:
FSRTP status for avast! Free Antivirus 7.x will not be detected until user
manually configures FSRTP status at least once. That is, user should turn off
“File System Shield" and turn it on. (785223)
This notification is still an issue in 2.3.0
From the releasenotes for ESAP 2.3.0
FSRTP status for avast! Free Antivirus 7.x will not be detected until user
manually configures FSRTP status at least once. That is, user should turn off
“File System Shield" and turn it on. (785223)
Any status update possible from Avast since this issue is over a year now?