Secure Endpoint Agent release notes - Version 7.14 hotfixes

If automatic agent updates are disabled, you can assign an agent version to your account's Windows and Mac devices to prevent agent upgrades. To determine if you want to assign a particular agent version, review this topic to learn about the enhancements and fixes supported in each hotfix version of the Secure Endpoint Agent.

About the Secure Endpoint Agent

The Secure Endpoint Agent is a small software client that resides on devices managed in the Secure Endpoint Console. After the agent is initially installed on a new device, the agent is activated with its first connection to the Absolute Monitoring Center.

Each agent package includes software specific to its supported operating system, including the agent and its associated components, an installer, and a readme file.

System requirements

The 7.14.0.x package bundles contain Secure Endpoint Agent software that support devices running the following operating systems:

Operating system	Supported versions
Windows	Versions 7, 8.1, and 10
macOS	Versions 10.13 to 11

Agent improvements and fixes

The following fixes and improvements are available in each agent version:

Agent Version	Platform	Component	Component version	Fixes and improvements
7.14.0.1	Windows	Anti-Malware (AVP)	1.0.1.32	Previously, when a component ran a scan on a Window 7 device, the scan results may, in some cases, have failed to be processed and made available in the Secure Endpoint Console. This issue is now fixed.
		Device Usage (DUR)	1.0.3.8
		Encryption (ESP)	1.0.1.33
		Installed Software (SNG)	1.0.3.9
		Hardware (HDP)	2.0.2.40	To address a stability issue introduced in version 2.0.3.14, the HDP component has been rolled back to the previous version.
7.14.0.2	Windows	Device Usage (DUR)	1.0.4.1	Logging and error handling improvements.
		Software (SDC)	1.0.2.4
		Application Persistence (RAR)	7.13.2.14	Previously, application installers couldn't be hosted on platforms that used wildcard certificates in the SSL certificate. The agent now supports HTTPS connections signed with wildcard certificates. In some cases, devices had problems running health checks for Microsoft® SCCM. This caused the devices to return an Application Persistence status of Not compliant for SCCM, even when the device was compliant. This issue is now fixed. Performance, logging, and error handling improvements.
		Hardware (HDP)	2.0.4.9	If both the WMI and HDP services are stopped, the HDP service now restarts successfully, even if the WMI service is not restarted. Previously, when the HDP component checked the WMI service during a Hardware scan, it may have caused WMI instability on some Windows devices. This issue is now fixed. On a newly activated device, the HDP component now performs a single upload of the results of the initial Hardware scan. Previously, the scan was uploaded twice, approximately 15 minutes apart. Performance and error handling improvements.
		Installed Software (SNG)	1.0.4.12	Previously, on some Windows devices, the SNG component may have failed to detect all installed applications, meaning only a partial list of applications showed on the device's Applications page. This issue is now fixed. Logging and error handling improvements.
		Wipe (SDW)	1.0.3.5	If Active Directory is used for BitLocker key management, you can no longer unlock a wiped device using the device's BitLocker recovery key. Previously, if BitLocker was suspended after a Wipe request was successfully processed on a device, but before the Wipe was verified as complete, Device wipe failed showed on the Events page in the History area of the console. This issue is now fixed. If this scenario occurs, the SDW component now enables BitLocker so the correct event status can be reported.
	Mac	Component Manager (CTES)	1.0.0.2354	Newly activated devices running macOS 10.15 or 11 are now displayed in Absolute 7 reports and pages. Previously, in some cases, the devices were displayed in Classic reports only.