Press CTRL+K to open search

Resolved issues

  • Published on Sep 8, 2026
  • 1 minute(s) read
Prev Next

The following issues were resolved in the Endpoint Security Agent (HX) 35.31.25 release.

Tracking number

Summary

ENDPT-108949

Upgrading to xAgent version 35 in a Windows environment frequently caused the xAgent to consume excessive memory on the Endpoint Security (HX) server. This issue has been resolved.

ENDPT-108858

Resolved an issue with the Quarantine Malicious Artifacts feature in Exploit Guard where it failed to quarantine documents in xAgent version 35.31.0.

ENDPT-109686

Upgrading the xAgent from a version before 35.31.22 using a custom installation path creates a separate swidtag folder outside the custom installation path. Some files are stored in the swidtag folder and not in the correct directories. This issue has been resolved.

ENDPT-109998

On Windows installations of xAgent 35.31.22, the host endpoint could unexpectedly hang, requiring a reboot of the host. This issue has been resolved.

ENDPT-109763

On Windows 10 22H2 and Windows 11 22H2 agents, Exploit Guard can adversely affect the normal execution of 32-bit monitored applications. This issue has been resolved.

:
Related articles
  • Resolved issues
    Endpoint Security Agent (HX) > Endpoint Security Agent (HX) Release Notes > xAgent 36 > 36.30.0
  • Resolved issues
    Endpoint Security Agent (HX) > Endpoint Security Agent (HX) Release Notes > xAgent 36 > 36.20.0 > xAgent 36 (Mac) 36.20.0
  • Resolved issues
    Endpoint Security Agent (HX) > Endpoint Security Agent (HX) Release Notes > xAgent 35 > 35.31.22