--- title: "Resolved issues" slug: "resolved-issues-43" tags: ["Release Notes"] updated: 2026-10-01T08:04:07Z published: 2026-10-01T08:04:07Z canonical: "docs.trellix.com/resolved-issues-43" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Resolved issues The current release of the product resolves these issues. For a list of issues fixed in earlier releases, see the Release Notes for the specific release. For a list of current known issues, see:Trellix IPS 11.1 Known Issues [(KB96274)](https://support.trellix.com/s/article/KB96274). ### Resolved Manager software issues The following table lists the **high-severity** Manager software issues: | Reference # | Resolution | | --- | --- | | NSPMGR-27552 | In an MDR pair, the Secondary active Central Manager fails to display new attacks on the **Attack log** page while the Primary Central Manager is down. | | NSPMGR-27474 | An error **Initializing Default Policies** is displayed in the Manager while creating a new policy from **Policy \| \| Intrusion Prevention \| Policy Types \| Inspection Options**. | The following table lists the **medium-severity** Manager software issues: | Reference # | Resolution | | --- | --- | | NSPMGR-27832 | In rare scenarios, the "**alertdbcoord.log**" file size may exceed more than 100 GB. The log file keeps growing over time and it does not rotate. | | NSPMGR-27752 | Unable to access the **Device Software** details from **Manager \| \| Trellix IPS Protection Status**. | | NSPMGR-27744 | Import of CSV file hashes with hash lengths that are not equal to 32 or 64 hexadecimal digits are accepted and validated. | | NSPMGR-27727 | In the Linux-based Manager, the Manager service fails to start after upgrading from **10.1.7.65** to **11.1.7.56**. | | NSPMGR-27578 | The deployment failed to activate the secondary Sensor when the primary Sensor was not connected or was inactive. | | NSPMGR-27511 | The **Attack Severity Summary** hyperlink in the **** of the **Dashboard** fails to redirect to the specific severity of an **Attack Log**. | | NSPMGR-27426 | Unable to add the IP addresses to the **Exclusions** list in **Manager \| \| Setup \| Telemetry**. | | NSPMGR-27373 | After assigning the inspection policy to the Sensor by '**Policy Group**' **with Endpoint Reputation Analysis** enabled, the **IP Reputation** fails to be enabled. | | NSPMGR-27175 | In an MDR pair, the primary becomes inactive due to a large number of new users in the MLC Group Sync. | | NSPMGR-22133 | In an MDR pair, the **Alert Archive** file is generated even when the **Background Tasks** status is "**In Progress**". | | NSPMGR-21141 | In the **Background Tasks** tab of **Manager \| \| Troubleshooting \| Logs**, the Manager fails to display the actual **End Time**, **Duration**, and task **Status** for **Alert and Packetlog Pruning**. | | NSPMGR-12768 | For alert pruning, tuning, and other maintenance tasks, the Manager displays the data based on time rather than the status of the process. | ### Resolved Sensor software issues The following table lists the **high-severity** Sensor software issues: | Reference # | Resolution | | --- | --- | | NSPSNSR-15818 | Trellix SSL Agent installation fails due to incorrect Glibc library dependency. | The following table lists the **medium-severity** Sensor software issues: | Reference # | Resolution | | --- | --- | | NSPSNSR-15209 | SSL inspection causes latency with traffic having Diffie Hellman ciphers when the server initiates SSL resumption with a new Session ID. | | NSPSNSR-12869 | The signature update fails at the Sensor with an error message - "**DOWNLOAD FAILED: Reason #28: Sensor sigfile convert error**" during incremental sigfile update because the sigfile segments were getting missed while trying to form the full sigset. | | NSPSNSR-5107 | False Positive: Sensor detects "**DNS: Microsoft Windows Internet Connection Sharing Denial of Service**" when the internal Application ID resources are getting exhausted and error handling is incorrect. |