The VIPRE server is not updating definitions with the error similar to the following being logged in the Enterprise service logs or the VIPRE mirroring logs:

MD5 does not match for 

Note:The EnterpriseService.log can be located in the Console's Volatile Data folder:


  • VIPRE Business
  • VIPRE Business Premium
  • VIPRE Endpoint Security
  • All Supported Operating Systems


Verify the FIPS is not enabled on the server. 

Open regedit
Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\fipsalgorithmpolicy

If the value is set to 1 FIPS is enabled. 

Set the value to 0 and reboot the server. FIPS is usually off by default. 

If fips was not and and the error still occurs investigate to see if there is any Firewall, Proxy, or ISA Server or another device that could modifying the downloaded packet. The following article explains in detail what is required for the updates to be allowed through without issue: What is required for the VIPRE server to update properly


The file being downloaded does not match the file that was sent from our update servers. Something between the VIPRE server and the update servers has modified the files being downloaded. Most common cause is an edge device that does AV scanning or packet inspection. 

Having FIPS enabled will also cause MD5 errors.