Product Lifecycle
End of Support Notices
The products on this page have evolved into newer versions built to do more. If you are still running one of these versions, we encourage you to upgrade — you will get everything you have now, and more.
SecureAge does not provide support for versions that have reached their end of life (EOL) date.
How end of life works
Each minor version reaches end of life when the next version is released. For example, SecureAPlus 6.9.1 reached end of life on 15 September 2025, when 6.9.2 was released.
SecureAPlus Has evolved into CatchPulse
CatchPulse builds on everything SecureAPlus offered — the same trusted application control, now with deeper protection and greater control. Upgrading is a step forward, not a trade-off.
Upgrade to CatchPulse
Ready to upgrade to CatchPulse?
Get the latest features, ongoing updates, and continued support.
END OF LIFE TIMELINE
End of Sales
1 November 2025
End of Support
1 March 2026
End of Support
1 March 2026
VERSION HISTORY
- 6.9.1 (EOL date: 15 September 2025)
- 6.9.0 (EOL date: 18 March 2025)
Release Notes
SecureAplus 6.9.2 is now available. If you have experienced blue screen errors, unexpected service crashes, or policy retrieval failures on 6.9.1 or earlier, upgrading to 6.9.2 resolves these issues. For continued updates and supports, we recommend upgrading to CatchPulse.
Bug Fixes
- If you have experienced a blue screen of death (BSOD) on SecureAPlus 6.9.1 or earlier, upgrading to 6.9.2 resolves the issue.
- If the scan service crashed unexpectedly on 6.9.1 or earlier, upgrading to 6.9.2 fixes this.
- If the Everything.exe service continued running after upgrading SecureAPlus, this is addressed in 6.9.2.
- If devices could not retrieve the latest policy after changing device groups, upgrading to 6.9.2 will fix this.
SecureAPlus 6.9.1 is now available. If you have experienced a black screen on screensaver trigger after a Windows update, or excessive log file growth 6.9.0, upgrading to 6.9.1 or later resolves these issues. For continued updates and supports, we recommend upgrading to CatchPulse.
Bug Fixes
- If a black screen appeared when the screensaver triggered after a Windows Update on SecureAPlus 6.9.0, upgrading to 6.9.1 or later resolves this issue.
- If log files were flooded with entries when the license expired on SecureAPlus 6.9.0, this is fixed in 6.9.1 or later.
SecureAPlus 6.9.0 is now available. This release introduced real-time policy updates, improved trust level synchronisation, and several stability and compatibility fixes. For continued updates and support, we recommend upgrading to CatchPulse.
What’s New
- Real-Time Policy Updates: Administrators can now push policy changes to devices in real time from the management server. This feature requires Windows 10 or later.
Improvements
- Auto Adjust Trust Level settings now synchronised with the assigned policy, ensuring consistent behaviour across managed devices.
Bug Fixes
- If SecureData failed to function when SecureAPlus Protection was enabled on an earlier version, upgrading to 6.9.0 or later resolves the issue.
- If you experienced compatibility conflicts with other SecureAge products caused by secureage.exe being listed as a restricted application, this is addressed in 6.9.0 or later.
- If driver installation failed on Windows 10 (2015 release) on an earlier version, upgrading to 6.9.0 or later fixes this.
- If the VA Service as not removed after uninstalling SecureAPlus on an earlier version, this is corrected in 6.9.0 or later.
- If multiple licenses were consumed when the computer name changed on an earlier version, upgrading to 6.9.0 or later resolves this issue. This affected on-premise configurations only.
- If you were unable to enable a full system scan on an earlier version, this is fixed in 6.9.0 or later.
- If the AI antivirus update progress bar remained at 0% on an earlier version, upgrading to 6.9.0 or later addresses this.
Security Management Server is now SecureAge Central
SecureAge Central is the next generation of Security Management Server (SMS). We recommend upgrading to continue receiving the latest improvements, security updates, and support.
Move to SecureAge Central
Continued support, the latest updates, and a platform built to grow with your needs.
VERSION HISTORY
- 6.0.12 (EOL date: TBD)
- 6.0.11 (EOL date: 10 February 2026)
- 6.0.10 (EOL date: 27 October 2025)
Release Notes
Security Management Server 6.0.12 is now available. If devices running SecureAge Security Suite v8.0.33 or v8.0.34 were unable to connect to the server, or if you experienced issues editing Active Directory-synchronised user accounts on 6.0.11 or earlier, upgrading to 6.0.12 resolves these issues. For continued updates and support, we recommend upgrading to SecureAge Central.
Bug Fixes
- If SecureAge Security Suite v8.0.33 or v8.0.34 devices were unable to connect to Security Management Server, upgrading to 6.0.12 resolves the issue.
- If administrators were unable to edit SecureAge user accounts synchronised from Active Directory, upgrading to 6.0.12 fixes this.
- If the email column header was incorrectly labeled in SecureAge user management, this is corrected in 6.0.12.
Security Management Server 6.0.11 is now available. If devices running SecureAPlus v6.9.0 or CatchPulse v10.9.0 could not retrieve the latest policy after a device group change, or if your server license could not be activated online on 6.0.10 or earlier, upgrading to 6.0.11 or later resolves these issues. For continued updates and support, we recommend upgrading to SecureAge Central.
Bug Fixes
- If SecureAPlus v6.9.0 or CatchPulse v10.9.0 devices could not retrieve the latest policy after changing the device group, upgrading to 6.0.11 or later resolves the issue.
- If the server license could not not be activated online on 6.0.10 or earlier, this is fixed in 6.0.11 or later.
Security Management Server 6.0.10 is now available. If you have experienced issues uploading software update packages from Windows 11, or discrepancies between device count and license usage on an earlier version, upgrading to 6.0.10 or later resolves these issues. For continued updates and support, we recommend upgrading to SecureAge Central.
Bug Fixes
- If software update packages created and zipped on Windows 11 could not be uploaded through SecureAge Management Server, upgrading to 6.0.10 or later resolves the issue.
- If the device count did not match the license usage count on an earlier version, this is fixed in 6.0.10 or later.
- If the device last connection date was not being updated on an earlier version, upgrading to 6.0.10 or later addresses this.
Last modified on 23 June 2026