The new docs.trellix.com features a modernized UI and AI-powered conversational search. Content is currently available in English, with additional languages launching in early November 2026. We hope you enjoy the updated experience.

Press CTRL+K to open search

Resolved issues

  • Published on Sep 10, 2026
  • 2 minute(s) read
Prev Next

Tracking number

Summary

ENDPT-108976

After a tasking failure and subsequent tasking restoration, some IOC alerts from the xAgent are not visible on the Endpoint Security (HX) server. This issue has been resolved.

ENDPT-110221

When a high volume of bulk acquisitions is enabled, a 503 tasking failure can occur on HX. This issue has been resolved.

ENDPT-109060

Too many stale policies prevent timely policy updates. This issue has been resolved.

ENDPT-109061

If the regenstale policy service returns an error, the configUpdateMonitor also returns an error, but continues processing. This issue has been resolved.

ENDPT-106838

A virtual Endpoint Security (HX) deployment on NutanixTM AHV can unexpectedly detect the wrong HX appliance model number. This issue has been resolved.

ENDPT-108552

On Endpoint Security (HX) deployments, the fenet_content_manager process does not properly interact with the DTI server when connected via proxy. This issue has been resolved.

ENDPT-110422

In log file output, the am-service Alerts Monitor (avAlertsMonitor) incorrectly reports skipped data elements as errors. This issue has been resolved.

ENDPT-111121

On the Web UI page for macOS hosts, the Actions dropdown menu is missing entries for Standard, Comprehensive, and Quick File acquisitions. This issue has been resolved.

ENDPT-103586

Following a configuration change, the Endpoint Security (HX) unexpectedly serves default configurations to some host endpoints. This issue has been resolved.

COM-30911

A known SSL handling issue in the nxlog.conf file can interrupt data streaming between an Endpoint Security (HX) server and a Helix instance. This issue has been resolved.

ENDPT-110161

The API Documentation Module incorrectly states that id:ascending and id:descending are allowed query-string parameters. This issue has been resolved.

: