> 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/xdr-agent-release-notes/9.1/cortex-xdr-agent-release-information/cortex-xdr-agent-known-issues-91.md).
# Cortex XDR agent known limitations
The following table describes the known limitations in the Cortex XDR agent 9.1.
| ISSUE | DESCRIPTION |
| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Windows on ARM | The Cortex XDR agent 9.1 on ARM architecture has the following limitations:
- Behavioral Threat Protection: Not fully supported
- Exploit Protection: Not supported
- File Examination: JScript, VBScript, and PowerShell file examination not fully supported
|
| GKE Autopilot | When using GKE Autopilot, if there is a timing issue encountered during Cortex XDR agent installation (GKE Warden constraints violations), the YAML installation command should be repeated. |
| Custer-level scoping | Cluster name is currently not supported in Oracle Cloud, GCP, Azure and Openshift (any cloud). For these operating systems, use the node name instead. |
| Live Terminal support | Live Terminal is currently not supported for pure IPv6 endpoints, on all platforms.
Live Terminal will not be supported with GKE Autopilot.
|
| Device control | When enabling Device Control protection for the first time, some devices that are already connected (or paired in case of Bluetooth) to the machine will not be immediately affected by the change.
The profile change will affect the connected device after one of the following occurs:
- Disconnect and reconnect the device
- A computer restart
In case of Bluetooth: Toggle the Bluetooth off and on, or manually unpair the device.
|
| Linux Kubernetes Platform, TalOS | When using TalOS, note the following:
- Collect insights and compliance collection are disabled.
- Live Terminal startup location is inside the agent pod and not on the host.
- All the server and user script execution initial working directories are inside the agent pod.
|
| VA scanning engine | When using the Vulnerability Assessment engine, note the following issues:
- In some cases, the reported application version may be missing or incomplete.
- Applications installed for specific users will not be scanned.
- During a scan, memory spikes may occur.
|
| SELinux | When installing Cortex XDR agent on a system with SELinux enabled, a custom install directory cannot be used. |
| SLES 15 | Installing Cortex XDR agent on SLES (SUSE Linux Enterprise) 15 with SELinux enabled is unsupported. |
| CPATR-18568 | \[Linux] On some occasions, when a container is a short-lived container (exits within a short period of time) retrieval of the container information is not guaranteed. |
---
# 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/xdr-agent-release-notes/9.1/cortex-xdr-agent-release-information/cortex-xdr-agent-known-issues-91.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.