Product release information for VIPRE Cloud Agent Custom Build version 13.1.8521, released on December 19, 2023.
What's New
We are releasing a custom build of the VIPRE Cloud Agent to address an issue causing Malicious URL Blocking for HTTPS to create two VIPRE URL Inspector processes that were not closing on their own.
If you were instructed to disable Malicious URL Blocking for HTTPS in your policy as a temporary workaround to this issue, you can re-enable it once you've deployed this custom agent build.
Special Instructions
Custom Build Codes
We occasionally provide Custom Build Codes to grant early access to upcoming agent releases. These builds are typically used to test new features or verify fixes for specific issues before they reach General Availability (GA). Use the table below to find a custom build code.
Update
2026 March 09: VIPRE Cloud Agent for Windows version 13.4.8857 Early Access is available with a custom build code below.
| Build | Custom Build Code |
|---|---|
| VIPRE Cloud Agent for Windows v13.4.8857 Early Access | 464F48CBEA5A08F6DA081B7D4056FB8C |
Step 1: Retrieve the Build
The following steps assume you are already logged in to your VIPRE Cloud web console.
- Navigate to SETUP > Deploy Agents
- On the right side of the window, under Retrieve Custom Build, click the button that says Enter Build Code
- Enter the build code that was provided to you and select Retrieve
Once the Custom Build agent is retrieved, it will appear under the current version.
Step 2: Deploy to Devices
There are two options to deploy the agent once you have the custom build.
Option 1: Update Devices (Strongly Recommended)
Use this method to remotely update agents that are already installed on your endpoints. This is the fastest and most efficient way to test a new build on existing machines.
- Next to the Custom Build, click Update Devices
-
Select the checkboxes next to the endpoints you would like to update to this custom build
- We recommend starting with your dedicated test machines
- Click Update Selected—a remote task is sent to the selected agents to perform the update
Option 2: Create Policy Installer (Fresh Installs Only)
This is more of a manual installation option, allowing you to create a policy-based MSI file for individual endpoints. This is only recommended for fresh installations on devices that do not currently have a VIPRE agent.
- Next to the Custom Build, click Create Policy Installer
- Select your desired policy, then click Select
- Allow some time for the policy-specific agent installer to be created, then click Download Installer
Your browser will then download the vipre_private_agent_yoursitename_yourpolicyname_versionnumber.msi file. Use your preferred method to get this MSI file to the endpoints you've chosen for installation.
|
|
 |
Congrats! You have successfully retrieved and installed a custom agent build.
System Requirements
Click here to review the most recent VIPRE System Requirements.
Bugs Fixed in this Release
- VPBAGENT-41620: A combination of Domain Exclusions was causing Malicious URL Blocking for HTTPS to produce two VIPRE URL Inspectors per lookup but was not automatically closing them.