The VSA 9.5.25 feature release (build 9.5.25.7442) includes enhancements and fixes described in the following sections. For minimum system and agent requirements, refer to Kaseya Server Minimum Requirements & Configuration and Agent Minimum Requirements.
Release schedule
- SaaS deployment started: Saturday, November 15, 2025
- SaaS deployment completed: Saturday, December 6, 2025
- General Availability (on-premises customers): Wednesday, December 11, 2025
Note: SaaS customers will be informed of their maintenance window via status.kaseya.com.
Dates are subject to change at short notice. On-premises customers are advised to check this page again before attempting an upgrade.
Last Update: December 11, 2025: Passly Deprecation reminder.
Important security update
This release includes important security updates. We recommend that on-premises customers upgrade as soon as possible after the General Availability (GA) release date. (No action is required for SaaS customers, as updates are automatically applied).
Reminder: Passly Deprecation
Passly will be deprecated Dec 31st, 2025. For details on potential impacts to VSA9 and guidance on next steps, please review our FAQ here.
Dependencies
| Agent |
This release requires agent version 9.5.0.50. After upgrading from an earlier VSA version, you must update your Windows, macOS, and Linux agents using the automatic or manual update process from the agent module. Note: this version cannot be installed to some End-of-Life macOS versions. Please reference the "Updates to macOS and Linux agent supported versions" section below for further details. |
| Live Connect Application | When starting a Live Connect or Remote Control session for the first time after installing this release, you will be prompted with a link to download the latest Live Connect build. You must complete the installation before proceeding with the session. |
| Software Management |
This release includes updates to the Software Management client code. Each managed machine will download 120 MB of file updates during the first patch scan or deployment cycle after installing the VSA update. The files will be sourced from the VSA server or a peer endpoint machine on the local network that already has the files. Recommendations to mitigate the impact on network bandwidth:
|
Support policy for prior releases
Kaseya recommends that customers update their environments to the latest patch release as soon as possible after the GA release date.
Our policy is to provide support for the current GA release, one prior Feature Release, and any interim Maintenance Releases. After the 9.5.25 GA date stated in the release schedule, the minimum supported version will be the 9.5.24 Feature Release.
Product lifecycle updates
VSA FIPS certification - November reminder
VSA 9 will no longer be FIPS compliant after March 8, 2026. It is recommended that if you require FIPS compliance that you start planning your migration to VSA 10 as soon as possible. Click here for more information.
3rd-Party Software 2.0: July-August updates
New titles
-
Malwarebytes 5
Refer to VSA 9 Software Management application catalog.
Bug fixes and other improvements
Agent App
- Fixed an issue where Agentmon.exe would crash with null pointers on Windows Server 2019 and 2022 when running Exchange.
Discovery
- Fixed issues related to special character restrictions in Azure SSO display names and user creation in VSA by sanitizing display names before user creation, with administrator logging added to track sanitization processes and duplicate checks performed post-sanitization.
Endpoint Protection
- Fixed an issue where EDR agents installed in a previous VSA version do not update correctly after a VSA patch update.
Installers
- Fixed an issue where offline installer upgrades failed for VSA version 9.5.22, specifically due to license file download errors.
Logs
- Fixed an issue where intermittent issues occurred during the archiving process in a VSA environment due to timeout-related failures.
System Module
- Fixed a bug related to the Pending Approvals feature not correctly adhering to user scope restrictions. The issue was resolved by implementing scope-aware filtering for agent procedures, ensuring only authorized users can see and approve procedures within their scope.