Release Notes for VIPRE Cloud Agent - Sept 18, 2019

Written By Marissa Fegan (Super Administrator)

Updated at June 17th, 2020

Product release information for VIPRE Cloud Agent 11.0.7633, released on September 18, 2019. 

This article contains information on what's new in this release. There are also special instructions for removing the workaround that may have been applied while waiting for this hot fix. Previously known issues are listed here along with suggestions on how to work-around the issue, if applicable.

What's New

The following bug has been resolved with this release.

  • VPBAGENT-4608 - Outlook freezes opening some PDF attachments

Special Instructions

After installing this agent hotfix, review your policies to ensure the Active Protection - High Risk Extensions setting has the pdf extension selected. Some customers may have temporarily removed the PDF extension as a workaround to this issue.

Known Issues and Workarounds

This section lists issues that are known at the time of release. In some cases, these are bugs that 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, should you experience an issue.

If you have questions about a specific issue, please provide the issue ID (if applicable) when contacting our Technical Support team.

At this time, there are no new known issues with this release.

Previous Known Issues

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.

  1. Open the VIPRE Agent
  2. Navigate to the Advanced Exceptions screen:
    1. Click Firewall > View Settings
    2. Under the Firewall section, click Exceptions...
    3. 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.

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

  1. On the Agent machine, open the Windows Local Security Policy
  2. Add the required user account to the "Local Policies" > "User Rights Assignment" > "Shut down the system" policy
  3. 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 computer 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.

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.

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.

Microsoft Windows Defender continues to run even if the 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:

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.

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 the removal.

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

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.

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.