> 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/cortex-xdr-3.x-rn/cortex-xdr-release-information/known-issues-xdr.md).

# Known Issues

The Cortex XDR release includes the following known issues:

<table data-header-hidden><thead><tr><th></th><th></th></tr></thead><tbody><tr><td>Issue ID</td><td>Description</td></tr><tr><td>CPATR-25409</td><td>In some cases, when the XDR Collectors is installed on a Linux platform, the XDR Collectors fails to register due to an incorrect operating system version. As a workaround, remove the <code>agilitytools</code> application and restart XDR Collectors.</td></tr><tr><td>CPATR-20105</td><td><p>When performing a XDR Collectors installation or upgrade in Linux using a shell installer, the  <code>/tmp</code> folder cannot be marked as <code>noexec</code>. Otherwise, the installation or upgrade fails. As a workaround, before the installation or upgrade, use the following command:</p><pre><code>mount -o remount,exec /tmp
</code></pre><p>The <code>deb</code> and <code>rpm</code> installations work fine without any problems.</p></td></tr><tr><td>CRTX-57553</td><td><p>When setting up the Broker VM on Google Cloud Platform (GCP) and a GCP image is imported using the G Cloud CLI, the following command fails.</p><p><code>gcloud compute images import &#x3C;VMDK image> --os=ubuntu-1804 --source-file="gs://&#x3C;image path>" --network=&#x3C;network_name> --subnet=&#x3C;subnet_name> --zone=&#x3C;region> --async</code></p><p>Until this is resolved as a workaround, use the following command.</p><p><code>gcloud compute images import &#x3C;VMDK image> --data-disk --source-file="gs://&#x3C;image path>" --network=&#x3C;network_name> --subnet=&#x3C;subnet_name> --zone=&#x3C;region> --async</code></p></td></tr><tr><td>CRTX-41336</td><td>A Database Collector applet on a broker VM that is deployed in a Cortex XDR FedRAMP environment cannot connect to MySQL and MSSQL.</td></tr><tr><td>XDR-55313</td><td>When exporting Restriction type profile with custom indicator rules and then importing those back, the rules are no longer available.</td></tr><tr><td>CPATR-15036</td><td>Cortex XDR only supports stitching login Windows Event Logs into stories for a Windows 8.1 or later machine.</td></tr><tr><td>XDR-30122</td><td>When your XQL query includes a filter with a result that is an exponential number, the filter can sometimes not work as expected, including not returning any results.</td></tr><tr><td>XDR-29691</td><td>Cortex XDR calculates CVEs for applications according to the application version, and not according to application build numbers.</td></tr><tr><td>XDR-21780</td><td>Backwards scan is not supported when generating a BIOC from the Native Search.</td></tr><tr><td>CPATR-10766</td><td>After a Microsoft Windows patch (KB) is uninstalled from the endpoint, the Cortex XDR agent continues to report this KB to Cortex XDR. As a result, the CVEs list for the endpoint in Vulnerability Management cannot be updated to include the CVEs addressed by the uninstalled KB.</td></tr></tbody></table>


---

# 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/cortex-xdr-3.x-rn/cortex-xdr-release-information/known-issues-xdr.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.