9.5.19 Feature Release - 15th June 2024

The VSA 9.5.19 feature release (build 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, June 15th, 2024
  • SaaS deployment completed: Saturday, June 29th, 2024
  • General Availability (on-premises customers): Wednesday, July 10th, 2024 - Available now!

Note: SaaS customers will be informed of their maintenance window via status.kaseya.net.

Dates are subject to change at short notice. On-premises customers are advised to check this page again before attempting an upgrade.


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



Agent This release requires agent version 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.
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:

  • Use distribution windows in scan and deployment profiles to avoid excessive concurrent downloads.
  • On larger networks, schedule a patch scan on a small selection of endpoints in advance of the main scan and deployment windows to leverage peer-to-peer file transfer and reduce the impact on internet 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.19 GA date stated in the release schedule, the minimum supported version will be the 9.5.18 Feature Release.


Product Lifecycle Updates

Termination of Software Management 1.0 patch updates

SM 1.0 was deprecated in 2022 and no longer receives new OS or 3rd Party patch updates. Your SM1.0 profiles must be converted to SM 2.0 profiles to ensure that patches published in June 2024 or later can be detected and deployed.

In product notices have been displayed since March 2023 advising you to upgrade to Software Management 2.0

We launched Software Management v2.0 in February 2022 with VSA v9.5.9. In March 2023, we introduced an automated upgrade wizard with v9.5.16 to convert SM 1.0 profiles to the new engine, with upgrade notices displayed within the Software Management module every 3 days until the upgrade is completed.

To complete the upgrade immediately, proceed as follows:

  1. Go to Software Management > Configuration > Settings.
  2. On the Migration tab, click on the Upgrade Wizard button.
  3. Step through the wizard and click Start Upgrade to complete conversion of SM 1.0 profiles to SM 2.0.

That’s it! The process is fully automated and patch detection and deployments will continue uninterrupted using the new engine. If you have questions or encounter any issues with the upgrade process, please contact our Support Team.


Billing Information for 3rd-Party Antivirus and Backup products

For customers using integrations with 3rd party AV & Backup Products purchased from Kaseya, we have implemented automatic billing for overages resulting from agent deployments beyond your purchased subscription limit or consumption of cloud storage (in the Acronis cloud) beyond the amount that you have purchased.

This due to an improved reconciliation process between our vendors' cloud consoles and our billing systems and not changes in the VSA product.

If you want to minimize the overbillings, uninstall any unnecessary AV or KCB agents and, in the case of KCB, additionally remove any cloud backups.

This will be reflected in invoices from July 2024 for usage dating from May 2024.

The following products are affected:

  • Webroot
  • Bitdefender
  • Malwarebytes
  • Kaseya Cloud Backup (Acronis)


Release features

Option to remove KaseyaOne Unified Login settings

To allow users to remove the KaseyaOne Unified Login settings for certain VSA organizations, a Remove Settings option has been added to the following locations:

  • System > Login Policy (alongside Enable Log In with IT Complete)
    From this page, the action will apply to the VSA organization the logged-in user belongs to.
  • System > Orgs/Groups/Depts/Staff > Manage (alongside the Enable and Disable options in the IT Complete tab)
    From this page, the action will apply to the selected VSA organization.

This action will:

1. disable Login With IT Complete (KaseyaOne Unified Login) for all users in the targeted VSA organization, and delete its configuration data. Re-enabling it will require re-registration.

2. remove the associated App Launcher link from KaseyaOne.


Exporting or importing Software Management 2.0 profiles

Via System > Import Center, users can now export and import the following Software Management 2.0 profile types and all their settings:

  • Scan and Analysis
  • Deployment
  • Override
  • Alerting

As part of this update, Software Management policy objects can be exported and imported. Selected profiles, which are matched by name, must exist in the VSA instance performing the import.

Note: 3rd-Party Software profiles are not included in this update.


Disabling TLS 1.0 and 1.1

TLS 1.0 and 1.1 can now be disabled at the operating system level on VSA application and database servers running Windows Server 2019 or later.


Update from .NET Core 3.1 to .NET v8

VSA no longer requires Microsoft .NET Core 3.1.28 - Windows Server Hosting Bundle to be installed, and dependent components have been updated to use .NET v8.

  • Added an Error level System Check to the server installer to check if .NET v8 is installed. If not, a "Fix it" link is displayed to initiate installation.
  • Added a Warning level System Check to the server installer to check if .NET Core v3.1 is installed. It should be uninstalled using Windows Control Panel, unless required by another application.


Other enhancements

Cloud backup

  • The Acronis version for new client installations has been updated to 24.2.37373. Existing clients must be updated from the Acronis cloud console.


  • Kaseya's digital signature has been added to some executable files, which are deployed to Domain Watch probe agents during the Active Directory harvest.
  • An issue causing Network Discovery scans to get stuck in a processing loop while interrogating certain devices, resulting in an indefinite processing state, has been fixed.


Bug fixes

Agent Procedures

  • An issue causing a database access error when a procedure attempted to schedule another procedure (or itself) that is already scheduled has been fixed.


  • An issue causing Azure AD single sign-on settings to be overwritten during the VSA patch install process has been fixed.
  • An issue causing the Kaseya Server service to crash when running a domain harvest from Discovery > Domain Watch has been fixed.


  • Database performance enhancement in monitor alarm processing has been implemented.
  • Database performance enhancement for the BMS Integration has been implemented.
  • Database performance enhancement for the Software Management report part/SM Status By Agent dataset has been implemented.
  • A database performance issue that could cause pages to time out when selecting certain machine view filters has been fixed.


  • The Monitor > Status > Suspend Alarm page would load very slowly or time out on systems with a large agent count. The page now loads consistently.

Network Monitor

  • The Network Monitor module will now function properly if ODBC Driver for SQL Server v18 was installed on the VSA application server.

Policy Management

  • An issue causing Agent Credential policy objects to intermittently fail to apply to target machines has been fixed.

Remote Control application

  • The clipboard is now cleared on the remote machine after a Kaseya Remote Control session is closed.
    • Note: this does not guaranty that text copied and pasted during the remote session will no longer be available to the remote user. It may still be present in clipboard manager applications which save the history.

Software Management

  • When using the Upgrade Wizard to migrate a Scan and Analysis profile with the Kaseya 1.0 OS patches engine to the new version, the migration process is now started and performed without errors.

  • Empty Patch Impact rules in Scan and Analysis profiles migrated from 3rd-Party Software 1.0 to 3rd-Party Software 2.0 were causing assigned machines to return no OS patch scan results. Any existing empty rules will now be set to Review after installing the patch.
  • An issue causing an error to be produced when attempting to edit and save an imported deployment profile has been fixed.
  • UI validation now adequately prevents saving Software Management Application Settings with empty Subject and/or Body fields. 
  • An issue causing the language to be missing from a software title in a 3rd-Party Software profile and not updated to the latest version, despite having the Auto Update property enabled, has been fixed.
  • An issue causing endpoints to restart computers in five minutes rather than respecting the Wait time value configured in the Deploy Patches dialog box has been fixed.
  • On the Machines page, certain functions and data were exposed to users without corresponding access rights. The following access changes resolve this issue:
    • Users without access rights to the Vulnerabilities page no longer have access to the Vulnerabilities, Pending Patches, and Suppressed Patches tabs on the Machines page.
    • Users without access rights to the Patch History page no longer have access to the History tab on the Machines page.
    • Users without access rights to K3PP Audited Applications no longer have access to the Audited Applications tab on the Machines page.


  • An issue causing empty graphs when attempting to view collected statistics via System > Server Management > Statistics has been fixed.

Have more questions?

Contact us

Was this article helpful?
2 out of 2 found this helpful

Provide feedback for the Documentation team!

Browse this section