Product release information for VIPRE Cloud Agent for Windows version 13.5.
What’s New
This release marks a significant milestone in modernizing endpoint protection across diverse IT environments:
- ARM64 Support: The VIPRE Cloud Agent for Windows now has expanded architecture support that achieves feature parity with the x86 / x64 Windows agent, including EDR support, Patch Management, Device Control, Web Access Control, Remote Shell, and more
- Microinstaller: A lightweight installer designed to streamline cloud agent deployments, and is used for manual, per-machine agent installations across all Windows architectures (x86, x64, and ARM64)
- Flexible Token Passing: Enhanced installer flexibility that preserves site enrollment even if install files are renamed or managed via custom scripts
- Full Windows OS Build String Collection: Agents now report complete OS build strings to improve compatibility tracking and support
- System Requirements Change: Windows 7 and Windows Server 2008 R2 are no longer supported
- Platform Compatibility Controls: The installer now actively blocks installation and upgrades on unsupported operating systems
VIPRE Recommends
Keeping all software in your environment as up-to-date as possible is critical. New software releases often fix issues with older product versions that, unless addressed, could leave you vulnerable. As such, VIPRE recommends updating to the most recent version as soon as possible.
Fixes and Improvements
- Version 13.5 also includes improved Windows Defender compatibility on Windows Server, faster scheduled scans, and greater upgrade reliability.
Special Instructions
In this section, we'll detail the installer updates and how to handle the file name, as well as how to access the Early Access build using a custom build code.
Installer Updates & File Name Handling
The new microinstaller embeds your unique tenant enrollment token directly inside the default downloaded filename, enabling double-click simplicity without manual configuration.
Important: Preserving Site Enrollment if Renaming the Installer
If the downloaded installer executable file gets renamed for any reason,(e.g., renaming to setup.exe or vipre-agent.exe), the installer will not be able to parse the token from the file name. In these cases, you must pass your site token using one of the following methods:
Option A: Command-Line Token Argument (Recommended for scripts/RMM)
Run the installer via the command line or terminal using the /token= parameter:
"<installer_file>.exe" /token=<YOUR_SITE_TOKEN>
Example: "vipre-installer.exe" /token=YmV0YS5teXZpcHJlLmNvbS9...
Note: You can copy the command, including your site token, directly from the Download Agent Installer screen.
Option B: Configuration File Deployment (vipre-edr-install.json)
You can drop a dedicated JSON configuration file in the same directory as the renamed installer executable:
- Download the vipre-edr-install.json configuration file directly from your VIPRE Cloud console (Download Agent Installer modal).
- Place vipre-edr-install.json in the exact same folder as your renamed installer file before running the installation.
🔒 Security Reminder: Your installation token allows devices to register with your specific VIPRE site. Treat tokens as sensitive credentials and share them only with administrators and deployment engineers.
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 November 04: VIPRE Cloud Agent for Windows version 13.5 Early Access is available with a custom build code below.
| Build | Custom Build Code |
|---|---|
| VIPRE Cloud Agent for Windows v13.5 Early Access | 01DC4D182DBE81B47C57D9609A822742 |
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.