> 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/compatibility-matrix/where-can-i-install-the-cortex-xdr-agent/virtual-applications-supported.md).

# Virtual applications supported

The following describes the supported software vendors you can use to deploy virtual applications and the minimum software version supported with each release of the Cortex XDR agent.

### Citrix

* Citrix Virtual Apps and Desktops (previously XenApp and XenDesktop)—7.xx and later on all Cortex XDR agents.
* Citrix App Layering according to the installation process detailed in the Cortex XDR agent admin guide. Installation on the OS layer: Citrix App 4 and later on all Cortex XDR agents Installation on the Platform layer: Supported from Cortex XDR agent 9.2 and later

### VMware

* VMware AppVolumes—2.13.1 & later on all Cortex XDR agents according to the installation process detailed.
* VMware Horizon View—7.8 & later for all Cortex XDR agents.
* VMware ThinApp—5.2.2 & later for all Cortex XDR agents.

### Windows

* Windows Virtual PC—Azure Virtual Desktop (WVD or AVD) supported from Cortex XDR agent 7.5 and later.


---

# 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/compatibility-matrix/where-can-i-install-the-cortex-xdr-agent/virtual-applications-supported.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.