Note:  For the context of this article, the following terms apply:
  • An UPDATE refers to moving from an older software version to a newer software version. For example, an update from VIPRE 7.5 > VIPRE 10.0.
  • An UPGRADE refers to moving from one edition of VIPRE to a more enhanced edition. For example, an upgrade from VIPRE Antivirus Business > VIPRE Endpoint Security. 


IMPORTANT: When upgrading agents, you must create an EXE installer package instead of an MSI installer package. Using the MSI installer package to upgrade an agent will cause the upgrade to fail. See Possible Issues During Update/Upgrade below (this also applies to updating an agent during the upgrade).


  1. New features in version 10.0
  2. System requirements
  3. Upgrade notes
  4. Bugs fixed
  5. Known issues and workarounds
  6. Helpful articles
  7. Product changes
  8. Download product

1. New features in version 10.0

VIPRE Endpoint Security

  • NEW! Health Summary Report - A special report that provides an at-a-glance overview of your site's 'vital stats'. This report has a new look and feel with engaging, clean visuals. The main content of the report is an embedded HTML for instant viewing in your email. A PDF is also attached for forwarding on to other parties within your organization. This also provides a quick notification to the Console administrator regarding agents that are outdated and need to be updated.
  • NEW! Stealth Mode - Admins can now enable Stealth Mode on agents, which blocks outgoing ICMP unreachable and TCP reset messages for a port when no application is listening on that port.
  • Upgraded Device Control - New version of Device Control library offers better stability.
  • NEW! Color coding on agent version - Console admins now have quick visibility to which agent versions are out of date.
  • Various performance and bug fixes

2. System requirements

Management Console and VIPRE Site Service

  • Windows Server 2016
  • Windows Server 2012 (excluding Server 2012 Core)
  • Windows Small Business Server 2011, 2008 and 2003
  • Windows Server 2008 SP2 and 2008 R2 (excluding Server 2008 Core)
  • Windows 10 All editions (32- & 64-bit)
  • Windows 8 (32- & 64-bit)
  • Windows 7 (32- & 64-bit)
  • Windows Vista SP2 (32- & 64-bit)

Note: Embedded operating systems are not supported


  • Dual core processor or higher
  • 1 GB free disk space(up to 20 GB could be required for Endpoint Security versions for caching of patches)
  • 2 GB RAM
  • 1024 x 768 monitor resolution


  • MDAC 2.6 SP2 or later
  • Internet Explorer 8 or later
  • Microsoft .NET Framework 4.6 (if not already installed, .NET will automatically install during installation)

VIPRE Business Mobile Security


  • Android 2.2 and above

  • iOS 5.1.1 and above

VIPRE Agent for Mac


  • OS X Mountain Lion (10.8)
  • OS X Mavericks (10.9)
  • OS X Yosemite (10.10)
  • OS X El Capitan (10.11)
  • macOS Sierra (10.12)

VIPRE Agent for Windows


  • Windows 10 All editions (32- & 64-bit)**
  • Windows 8 (32- & 64-bit)
  • Windows 7 (32- & 64-bit)
  • Windows Vista, Vista SP1+ (32- & 64-bit)
  • Windows Server 2016**/***
  • Windows Server 2012 and R2(excluding Server 2012 Core)
  • Windows Small Business Server 2011, 2008 and 2003
  • Windows Server 2008 and 2008 R2 (excluding Server 2008 Core)
  • Windows Embedded for Point of Service (WEPOS) platforms
* VIPRE Endpoint Security is not supported on Windows XP or Server 2003.

** VIPRE Endpoint Security is not supported on these Operating Systems with Microsoft's Device Guard enabled. See this article for more information.

*** Windows Server 2016 currently does not support policies using VIPRE's Device Control feature.



  • Dual core processor recommended
  • 1 GB free disk space
  • 2 GB RAM or better recommended


  • Internet Explorer 8 or later


  • Microsoft Outlook 2003+
  • SMTP/POP3 (Thunderbird, IncrediMail, Eudora, etc.)
  • SSL supported in Outlook only

Product and company names are trademarks and registered trademarks of their respective owners.

3. Upgrade notes

  • If you deploy this console update without turning off automatic updates, your console may automatically update your existing VIPRE Windows agent software. Read below for more information.
  • When upgrading agents, you must create an EXE installer package instead of an MSI installer package. Using the MSI installer package to upgrade an agent will cause the upgrade to fail. See Possible Issues During Update/Upgrade below (this also applies to updating an agent during the upgrade).


If you DO NOT wish to automatically update your existing agents, you can temporarily change your policies by doing the following prior to installation:

  1. Open the Management Console.
  2. Locate the policy for a set of agents you do not want to be updated, and select the properties for that policy.
  3. Navigate to Updates.
  4. Uncheck Check for agent software updates periodicity in hours.
  5. Repeat as necessary for each additional agent group and associated policy.
  6. Wait 24 hours after the policy change before performing the console update.

The agents that use the modified policies will retrieve the policy update and cache it locally, thereby preventing them from attempting to automatically update. The final step above ensures the edited policy propagates to all agents before the console is updated.

Upgrading the VIPRE Business Console

See the following Support article: How to upgrade the VIPRE Business Console

Upgrading VIPRE Business Agents

The following support article has been updated to include special instructions for this release, and is highly recommended: How to configure agent software updates for VIPRE Business

4. Bugs fixed

The following issues have been resolved in this release:

VIPRE Console

  • Not all agents set for deployment from the Console would deploy on the first attempt.

  • Attempting to perform a password reset from the agent would fail, as the Console would not properly process the event. 

  • In some cases, attempting to remove users from receiving email alerts would fail.

  • Console could become very slow due to database purging issue unless the service was restarted.

  • Certain software patches would still show as outdated after being updated.

  • Scheduling many (70+) reports caused the Report Viewer to run very slowly.

  • When changing configurations from one network to another, the reporting server address was unable to be edited in the UI, but still appeared to be in use.

  • Certain web filter events could cause the XML processor to fail, causing a buildup of unprocessed XML data.

  • Server storage for definitions was not being properly purged, causing potential disk space issues.

  • Certain email items quarantined on an agent did not show up in the Console; had to be manually released from the agent side.

  • Users with over 2000 deployed agents had to manually purge firewall statistics in order to remove unresponsive agents.


  • Certain database applications running on the same network as a VIPRE agent could cause increased bandwidth usage between the agent and the database.

  • Agent upgrade process failed because certain services were unable to be automatically stopped before the upgrade could occur.

  • MS Office file types being saved to a network location would trigger a delay in the writing of the file.

  • Enabling Edge Protection could drastically reduce upload/download speed on certain machines.
  • VIPRE Email Protection reported incorrect user on Windows terminal services environments when multiple users were logged in. 
  • Enabling Device Control could cause many extra information messages to be written to the system log.

  • Outlook email protection could sometimes remove all email headers from a message.

  • On certain devices, Outlook would hang when the VIPRE plugin was loaded.

  • If the Windows Store application was quarantined, it could not be properly restored.

  • Some roaming agents calling in to the VIPRE Site Service were unable to update their licensing information, causing definition updates to fail.

  • Some agents running on virtual machines would not always check for software updates before each scan.

5. Known issues and workarounds

•   Microsoft Windows Defender continues to run even if policy has Disable selected

For policies applying to machines running Windows Server 2016, 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:

•  VIPRE Business or VIPRE Business Premium agents on version 9.3 or earlier that are scheduled to upgrade to VIPRE Endpoint Security will not fully upgrade on the initial install.

VIPRE has added multiple driver updates that are included with this release. Depending on the version of the drivers on your system and which features are enabled in your policies (e.g. Device Control), installation may require two or more reboots to complete the agent upgrade.

Make sure any required reboots are completed: For the corresponding agent, check the Console > Agent Details > Agent Environment tab and verify the "Needs Reboot" column is not marked with an "X".

•  Color coding of agent version in console does not appear to be consistent for all out of date agents

In the Protected Computers tab of the console, the agent version field is shaded orange for those agents that need to be updated to the latest agent software version. However, some agents that appear to be out-of-date are not shaded. Those agents include VIPRE Business or VIPRE Business Premium agents that do not have the highest build available. Agents that are not actively communicating are also not shaded but may be out of date. 

Workaround: The agents will update with the correct status upon the next communication. You may note VIPRE Business or VIPRE Business Premium agents reporting incorrectly. We recommend these agents be upgraded to VIPRE Endpoint Security to match your VIPRE Endpoint Security 10 console. This will give you our best protection for these devices and correct the reporting issue. If you are not currently licensed for VIPRE Endpoint Security, please contact your sales representative (+1 855-885-5566 or Contact Sales) for more information on how you can upgrade. 

•  .NET error when version 10 console connects to VSS version 9.6 (or prior) and accessing Site or Policy properties

Due to changes introduced with VIPRE Business Endpoint Security version 10, including the update to .NET version 4.6, accessing version 10 consoles and resources from an older version of VIPRE Business is not supported. Likewise, using a version 10 console to access older consoles and resources is not supported. 


•  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.

WorkaroundThrough 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.

•  When managing over 500 agents, a full SQL database should be implemented.

It is recommended that when managing over 500 agents, a full SQL database (versus SQLite) will provide the best performance. 

See the following support article: Recommended SQL Server settings for a VIPRE Business Database

•  VIPRE Endpoint Security agents cannot run on Windows XP or Windows Server 2003.

The software limitations of these older platforms do not provide the resources necessary for some more robust agent features. VIPRE Endpoint Security requires a minimum OS version of Windows Vista or Windows Server 2008.

•   Attempting to launch more than one instance of the administration Console (via terminal services) causes agent > Console communication to fail.

This is a product design safeguard that prevents one administrator from overwriting a different administrator's settings without notification. Only one instance of the admin Console should be running at a time.

•   Advanced Active Protection cannot operate on machines with Device Guard enabled.

Due to some of the constraints that Device Guard puts on running processes, Advanced Active Protection cannot provide its detailed and comprehensive monitoring of potentially malicious processes on platforms with Device Guard enabled.

See the following support article: Does VIPRE’s Advanced Active Protection work in conjunction with Microsoft’s Device Guard feature?

•   Push agent installations do not work if Simple File Sharing is enabled.

Simple File Sharing prevents installation through the push option. You must manually create the MSI installer package and deploy the installer to the workstation. 

See the following support article: Minimum Requirements for Agent Push Deployment

•   Without proper firewall configuration, agents are unable to contact the Console.

An incorrectly configured firewall can prevent communication between the agent and the console.

See the following support article: Minimum Requirements for Agent Push Deployment

•   Using a Remote Admin Console running VIPRE Business 9.3 in conjunction with a VIPRE Business 9.6 Console can overwrite the VIPRE Business 9.6 Console settings.

If your primary VIPRE Business Console is running version 9.6, policy changes made on a Remote Console running version 9.3 could potentially overwrite the "Use VIPRE for Updates" setting on the 9.6 Console. 

Workaround: Discontinue policy updates on the 9.3 Remote Console until it is updated to version 9.6.


Workaround: After each policy change made from the 9.3 Remote Console, select the "Use VIPRE as Update Server" setting on the 9.6 Console after any 9.3 Remote Console policy changes (below).

To use VIPRE as a (non-local) update server:

  1. In the Policy Properties, open Agent > Communication
  2. Check Use VIPRE as Update Server for definitions and software updates
  3. Click OK.

•  Device Control policy changes may require an agent restart before they take effect.

On Consoles upgraded to 9.6 or earlier, policy changes will not be applied until the agent is restarted.

Workaround: Manually restart the agent to apply policy changes. 

To manually restart an agent:

  1. Right-click on the agent in the grid
  2. Select Issue Remote Restart Command

•  The Database Migration Utility may crash if the SQL Database has any spaces in the database name.

The Database Migration Utility for VIPRE 9.6 or earlier may crash during the migration process if your SQL Database has spaces in the name of the database.

Workaround: Resolution is under development. When created, database names should contain no spaces, no symbols, and no carriage returns.

•   Definition updates fail to load properly.

When running VIPRE and performing a definition update from the Console, the VSS stops updating definitions and reaches an indefinite updating state.

Workaround: Shut down VIPRE and delete the definition folder. This will force a full update.

  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: Shut down Outlook during agent installation when enabling Anti-Phishing.


Workaround: Restart Outlook after agent install when enabling Anti-Phishing.

•   Windows 10 agents may BSOD after updating to agent version 6032.

After updating to agent version 6032 for Windows 10 Anniversary support, some users have reported Windows 10 blue screen crashes. We have identified the cause of some of these occurrences and believe they are fixed with this release.

WorkaroundAs these crashes are difficult to reproduce, we cannot guarantee all are resolved. Occurrences should be rare. If they should happen, please contact Support so we can work with you to identify the cause and resolve the issue. As other causes are corrected, we will publish an agent hot fix to address.

•  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.

6. Helpful articles

Advanced Active Protection & Device Guard
How to setup a VIPRE Business Agent for multiple environments
What is required for VIPRE Business Console to update properly?
Minimum Requirements for Agent Push Deployment
How to configure your Windows Firewall for VIPRE Business
What are Roaming Agents and how do they work?
How to confirm connectivity between a VIPRE Agent & Console
How to setup VIPRE Business Agents for different environment types

7. Product changes

  • Product rebranding - Version 10.0 is the first release of VIPRE Endpoint Security under the VIPRE Security company name.
  • VIPRE Edge Protection technology - This feature has been deprecated and removed from the Console and agent.
  • MST file-type removed as a package option - This feature has been deprecated and removed from the Console.

8. Download product

To begin the update process, download the installer from here: Download VIPRE Endpoint Security Installer

Copyright © 2008–2017 VIPRE Security. All Rights Reserved. VIPRE Security, VIPRE and the VIPRE Logo are trademarks or registered trademarks of VIPRE Security in the U.S. and other countries. Other names may be trademarks of their respective owners.