Product release information for VIPRE Cloud Agent 11.0.7627, released on April 2, 2019.
Bugs Fixed in this Release
The following bugs have been resolved with this release of the product.
- VPBAGENT-3981 - 16-bit commands issued on the command prompt cause a Virtual Device Driver error
- VPBAGENT-3777 - Outlook "flickers" several times when sending emails
- VPBAGENT-3657 - Windows Defender Security Center reports "your device may be vulnerable" if the VIPRE Firewall is disabled
- VPBAGENT-3656 - Outlook 2016 users with VIPRE Email Protection enabled may experience email messages with a blank email body
- VPBAGENT-3652 - Microsoft OneDrive users could encounter a VIPRE service crash when attempting to access OneDrive documents
- VPBAGENT-3646 - VIPRE definitions do not fully update after a few days
- VPBAGENT-3612 - Accessing Windows VirtualDisk Service is slow when Device Control is enabled
- VPBAGENT-2894 - When VIPRE scans for available software patches, it can cause the avcproxy service to crash
- VPBAGENT-2767 - Incompatibility issues with TPM Bitlocker encryption chip causes VIPRE to crash
- VPBAGENT-2609 - Advanced Active Protection shows excessive traffic
- VPBAGENT-2469 - AVCProxy service causes agent to take longer than expected to start
- VPBAGENT-1978 - Agent reports incorrect IP address of a virtual NIC
- VPBAGENT-1097 - Some laptop devices are incorrectly reported as workstations
- VPBAGENT-113 - If users mark a network as untrusted in the firewall, they are unable to change it back to trusted, or remove it
Known Issues and Workarounds
This section lists issues that are known at the time of release. In some cases, these are bugs in which we are working to resolve with a subsequent release. Other items may be due to causes outside of our control, such as bugs with other vendors' software. In all cases, we have tried to provide a workaround for you to consider, in case you should experience the issue.
ISSUE: Agent-created simple firewall port exceptions do not block as expected [VPBAGENT-4209]
When simple firewall port exceptions are created, VIPRE does not block as expected.
Workaround: Create an advanced firewall exception
Navigate to the Advanced Exceptions screen in the VIPRE Agent, then select Help for detailed instructions.
- Open the VIPRE Agent
-
Navigate to the Advanced Exceptions screen:
- Click Firewall > View Settings
- Under the Firewall section, click Exceptions...
- Click the Ports tab > Add Advanced....
You can add Advanced Exceptions from this screen. For detailed steps on adding Advanced Exceptions, click the Help button on this screen.
ISSUE: Agents running Windows Server 2019 do not reboot when clicking "Reboot Now" on a VIPRE Reboot Required condition [VPBAGENT-3920]
This is a condition that occurs due to changes in Windows Server 2019 security settings.
Endpoint devices running Windows Server 2019 will not reboot when the "Reboot Now" button is selected unless the user account is added to a specific Windows Local Security Policy. The default "Administrators" group cannot restart the Agent using this method.
Workaround 1: Add the user to the "Shut down the system" policy
To add a user account to the "Shut down the system" policy
- On the Agent machine, open the Windows Local Security Policy
- Add the required user account to the "Local Policies" > "User Rights Assignment" > "Shut down the system" policy
- Sign Out and Sign In to the machine (or reboot) for the policy change to apply
The next time VIPRE requires a reboot, the modified user will be able to reboot the machine using the "Reboot Now" button.
Workaround 2: Restart the Agent manually
Instead of using the Reboot Now button, users can manually restart the Agent through the Windows Start menu.
ISSUE: Firewall trusted zones defined with IPv6 address ranges do not work [VPBAGENT-3187]
The VIPRE Agent does not recognize IPv6 trusted zone ranges, and treats any IPv6 traffic as non-trusted. Therefore, any firewall rules for non-trusted traffic will still apply.
There is no known workaround at this time.
ISSUE: Logging into a Citrix device with Active Protection enabled fails [VPBAGENT-275]
This is a known conflict between VIPRE Active Protection and Citrix User Profile Management (UPM). Attempting to login to a Citrix device with both services enabled causes the login to hang and eventually fail.
Workaround: Temporarily disable Active Protection for Agents that need to access Citrix devices.
Previous known issues
ISSUE: On some systems, Windows Defender's Smart Screen blocks the agent installer [VC-1279]
This appears to be an error in Microsoft's software registration process which we are tracking down.
Workaround: Select More Info from the Windows Defender popup and then select Run Anyway.
ISSUE: Microsoft Windows Defender continues to run even if policy has Disable selected
For policies applying to machines running Windows Server 2016 or higher, selecting "Disable Windows Defender" does not actually disable Windows Defender.
Workaround: You may manually disable Windows Defender on these machines. Refer to these articles for more information:
- Disabling Windows Defender Antivirus on Windows Server 2016
- Microsoft TechNet article: Windows Defender Overview for Windows Server
ISSUE: When changing Active Protection settings within a VM environment, the changes take up to 15 minutes to apply
This is normal, as communication between the Console > VM takes some time to propagate.
ISSUE: When VIPRE scans an email archive, files are not quarantined properly
Workaround: Through your email client, perform a manual cleanup of the email archive containing the infected email. Once the infected email has been removed, re-scan the endpoint to confirm removal.
ISSUE: Anti-Phishing does not work if Outlook is open during agent install
If Outlook is running when enabling Anti-Phishing in the VIPRE Console before pushing an agent installation, it will not function properly until Outlook is restarted.
Workaround 1: Shut down Outlook during agent installation when enabling Anti-Phishing
Workaround 2: Restart Outlook after agent install when enabling Anti-Phishing
ISSUE: Outdated Citrix drivers may cause BSOD on Windows 7 agents
Updating a Windows 7 agent to VIPRE Endpoint Security 9.6 or earlier can cause a blue screen state on systems with older versions of Citrix drivers on them.
Workaround: Updating the Citrix driver should resolve the issue.