Secure Endpoint release notes - Version 9 hotfixes

In addition to monthly security updates, this topic describes the software changes included in all hotfixes since the release of Secure Endpoint 9.0.

To view the software changes that apply to the Secure Endpoint Agent, see the Secure Endpoint Agent release notes - Version 9 hotfixes.

Depending on the Absolute product licenses associated with your account, some of the following features, enhancements, and fixes may not be available to you.

July 2024 improvements and fixes

Feature/Area Details
Absolute APIs
Application Resilience
  • Some health checks that are used to check compliance run PowerShell scripts. To prevent any antivirus programs or execution policies from blocking these scripts, the PowerShell scripts used for the following applications are now signed by Absolute:

    • BitLocker Drive Encryption
    • BlackBerry CylancePROTECT
    • Forescout SecureConnector
    • Microsoft Defender Antivirus
    • Microsoft Defender for Endpoint
    • Microsoft Intune
    • Symantec DLP
Applications
  • The following areas of the console now show information about the anti-malware (for example, Windows Defender) and full disk encryption (for example, BitLocker Drive Encryption) products installed on Windows devices:
    • Applications page
    • Installed Applications report
    • Applications page in Device Details

    Previously, theses products were only shown when the Include Health data option was selected in each device's Installed Applications policy.

Device groups
  • Previously, when a smart group used a Custom Field filter to define group membership, the filter may not have been applied correctly. This caused some devices that didn't satisfy the filter criteria to become members of the group. This issue is now fixed.
History > Actions
  • When you click the background of a completed Run Script action to view the request overview, the Return code field now shows 0 instead of Unknown.
Unenroll Device
  • Previously, an Unenroll Device request may have failed to be processed if it was submitted using the Upload Bulk Device File feature. This issue is now fixed.