> 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.1.md). # Addressed Issues in Traps Agent 6.1.1 | Issue ID | Description | | --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | CPA-6953 (Windows 7) | Fixed an issue on endpoints running Windows 7, where a Traps agent could halt when scanning loaded DLL files. | | CPA-6893 | Fixed a performance issue that occurred when Traps was calculating a process hash. | | CPA-6892 | Fixed a performance issue that occurred when Traps attempted to open a corrupt document. | | CPA-6885 (macOS) | Fixed an issue where Mac endpoints running Traps 6.1 and Symantec would freeze upon shutdown. | | CPA-6866 (macOS) | Fixed a driver compatibility issue on Mac endpoints running Symantec. | | CPA-6840 (Windows) | Fixed an issue that occurred on Windows endpoints whose Agent Setting profile was configured to disable access to the Traps console on the endpoint. If you tried to access the console anyway, the system message wrongly stated that Traps has been disabled instead of indicating that your access to the Console has been disabled. | | CPA-6786 | When enabling Traps to monitor and collect data for sharing EDR data with other Cortex apps, Traps could halt if it attempted to reference a process that has already ended. | | CPA-6782 | Fixed an issue where the Traps agent reported to be working with the new content version even though the content update failed on the endpoint. | | CPA-6651 (Windows 10) | Fixed a compatibility issue with CFG exports suppression on endpoints running Windows 10 RS2 Version 1703 (Build 15063) and later. | | CPA-6586 (macOS) | Fixed an issue where a Mac agent that became unlicensed could not be uninstalled using the default system password. | | CPA-6542 | Now for Behavioral Threat events on Mac and Linux endpoints, the Analysis tab of the security event displays the correct year in the timeline. | | CPA-6461 (Windows) | Fixed an issue on Windows endpoints where the incorrect content version number may be reported back to Traps management service in case of a communication error. | | CPA-6344 (macOS) | Now you can upgrade Mac endpoints running Symantec to Traps 6.1.X version. | | CPA-6315 (Windows) | Fixed an issue in non-persistent VDI environments, where Traps agents on Windows endpoints were unable to connect to the Traps management service but the endpoint details on Traps management service displayed an active status. | | CPATR-6668 (Windows) | Fixed an issue where events where the evaluation of behavioral threat events caused high CPU usage on Windows endpoints. | --- # 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.1.md?ask=&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.