> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/6.1-eol/traps-tm-agent-release-notes-6.1.9-eol-windows-only/addressed-issues-in-traps-agent-6.1.7.md).

# Addressed Issues in Traps Agent 6.1.7

| Issue ID              | Description                                                                                                                                                                                 |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| CPATR-11311 (Windows) | Fixed an issue on Windows endpoints where the Traps agent did not detect the existence of a macro within a Microsoft Office document.                                                       |
| CPATR-10622           | On Linux endpoints connected to Cortex XDR through a proxy, fixed an issue where the Traps agent attempted to resolve DNS requests directly without using the proxy.                        |
| CPATR-10042           | On endpoints connected to Cortex XDR through a proxy, fixed an issue where after upgrading to Cortex XDR agent 7.1 release, the agent failed to register due to incorrect timeout settings. |
| CPATR-9972            | Fixed an issue where the Traps agent failed to connect to the server when using an invalid ID, even with the Cytool reconnect force command.                                                |
| CPATR-9871            | Addressed security issues.                                                                                                                                                                  |
| CPATR-9718 (macOS)    | Fixed a performance issue that occurred on Mac endpoints running heavy script loads.                                                                                                        |
| CPATR-9134            | Fixed an issue where the Traps agent failed to collect log files when executing the Cytool log collect command from a LocalSystem account.                                                  |
| CPATR-9082 (Linux)    | Fixed a compatibility issue where the Traps agent installation failed on Linux endpoints with preloaded libraries (LD\_PRELOAD and /etc/ld.so.preload).                                     |
| CPATR-9008            | On endpoints connected to Cortex XDR through a proxy, fixed an issue where multiple requests to get verdicts from WildFire® would hang if the activity mode of the proxy was changed.       |
| CPATR-8763 (Windows)  | On Windows endpoints, fixed compatibility issues with the scanning of CSVFS volumes.                                                                                                        |
| CPATR-8533 (Linux)    | Removed unnecessary error messages from the log files on Linux endpoints.                                                                                                                   |
| CPATR-8488            | Fixed an issue where the Traps agent reported an empty status to Cortex XDR, if the status reporting occurred immediately after agent startup on the endpoint.                              |
| CPATR-8244            | Fixed an issue where Cytool erroneously reported running services as stopped on a Linux endpoint running non XSI-conforming PS binary (pre-2014).                                           |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/6.1-eol/traps-tm-agent-release-notes-6.1.9-eol-windows-only/addressed-issues-in-traps-agent-6.1.7.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.