> 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/8.x/cortex-xdr-agent-8.9-release-information/addressed-issues-in-cortex-xdr-agent-8.9/addressed-issues-in-cortex-xdr-agent-8.9.0.md).

# Addressed issues in Cortex XDR agent 8.9.0

The following issues have been resolved in Cortex XDR agent release 8.9.0

| **Issue**                          | **Description**                                                                                                            |
| ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| <p>CPATR‑31605</p><p>(Windows)</p> | Fixed an issue that in specific scenarios may impact the Cortex XDR agent performance.                                     |
| <p>CPATR‑31160</p><p>(Windows)</p> | Fixed an issue that recreates the Agent Logs Directory if it is missing.                                                   |
| <p>CPATR-31056</p><p>(Windows)</p> | Fixed an issue that may occur on rare occasions when running a scan.                                                       |
| <p>CPATR-30980</p><p>(Linux)</p>   | Fixed an issue that may have affected JVM installation when upgrading the XDR agent.                                       |
| <p>CPATR-30946</p><p>(Windows)</p> | Fixed an issue that in specific cases may impact the Cortex XDR agent performance.                                         |
| CPATR-30886                        | Fixed an issue that may occur when using App Layering Issues VDI.                                                          |
| <p>CPATR-30537</p><p>(Windows)</p> | Improvement made to the Cortex XDR agent stability posture.                                                                |
| <p>CPATR-30480</p><p>(Windows)</p> | Improvement made to the Cortex XDR agent stability posture.                                                                |
| <p>CPATR-30212</p><p>(Linux)</p>   | Fixed an issue in Bottlerocket OS that may have caused disruption to Kernel module dependencies during agent installation. |
| <p>CPATR-30173</p><p>(Linux)</p>   | Improvement made to the Cortex XDR agent security and stability posture.                                                   |
| <p>CPATR-30147</p><p>(Windows)</p> | Fixed an issue to apply exclusion lists to files as well as folders during ImagePrep scans.                                |
| <p>CPATR-29622</p><p>(Windows)</p> | Improvement made to the Cortex XDR agent security and stability posture.                                                   |
| <p>CPATR-29517</p><p>(Linux)</p>   | Fixed an issue to limit the number of open LevelDB file descriptors.                                                       |
| <p>CPATR-28805</p><p>(Linux)</p>   | Introduced a new mechanism for detecting JVM initialization completion to improve performance and stability.               |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/8.x/cortex-xdr-agent-8.9-release-information/addressed-issues-in-cortex-xdr-agent-8.9/addressed-issues-in-cortex-xdr-agent-8.9.0.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.