Product release information for VIPRE Cloud Agent 10.1.7341 released on July 19, 2018.

Improvements

• VPBAGENT-3474 - Improved VIPRE crash recovery in the situation where a corrupted definitions file is received 
• VPBAGENT-3501 - Updated VIPRE Advanced AP engine functionality

Bugs Fixed

• VPBAGENT-2582 - Some non-malicious URLs were blocked by the Malicious URL blocking feature
• VPBAGENT-2607, VPBAGENT-2386 - A conflict between a network driver and the VIPRE Firewall could sometimes cause the firewall to crash
• VPBAGENT-3253 - Under certain conditions, exclusions with wildcards could incorrectly be ignored by VIPRE
• VPBAGENT-3283 - Under certain conditions, the Windows Defender Security Center would incorrectly report firewall protection is off
• VPBAGENT-3253 - Under certain conditions, Advanced Active Protection exclusions with wildcards could incorrectly be ignored by VIPRE
• VPBAGENT-3286 - On lengthy scans (over 24 hours), the “scan time” clock would not show an accurate scan time when completed
• VPBAGENT-3396 - Under certain conditions, VIPRE could quarantine a file that is supposed to be excluded
• VPBAGENT-3421 - When waking up a computer from "Sleep", the VIPRE agent may attempt to send a hello call to the console before the network connection is active
• VPBAGENT-3470 - Under some conditions, toggling IDS in the Firewall on the agent could cause the agent to crash
• VPBAGENT-3472 - Email Protection was causing email body to be blank
• VPBAGENT-3494 - An Agent could occasionally enter a loop state and continually request the same definitions from the console until it crashes
• VPBAGENT-3500 - Internal improvements to log collection
• VPBAGENT-3516 - VIPRE Agent could incorrectly remove files, causing a BSOD condition
• VPBAGENT-3543 - Certain XML files with embedded malicious content could fail disinfection properly
• VPBAGENT-3596 - In certain situations, scans could cause a machine to hang or become unresponsive
• VPBAGENT-3600 - When performing a Deep Scan with a CD-ROM disc present, the Agent could hang