> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/de/knowledge-base/troubleshooting-articles/blank-page-issues-in-a-citrix-environment.md).

# Probleme mit leeren Seiten in einer Citrix-Umgebung

Beheben Sie Probleme mit leeren Seiten in WebView2 in einer Citrix-Umgebung, indem Sie den WebView2-Prozess von den Citrix-API-Hooks ausschließen.

Mehrere Probleme im Zusammenhang mit dem Verhalten von Webview2 in einer Citrix-Umgebung.

### Lösung

Wir haben Informationen über unerwünschtes Verhalten in einer Citrix-Umgebung gefunden, das andere Benutzer erlebt haben, weil die API-Hooks von Citrix Webview2 beeinträchtigen: [Webview2 application running in a Citrix environment · Issue #1082 · MicrosoftEdge/WebView2Feedback](https://github.com/MicrosoftEdge/WebView2Feedback/issues/1082)

Nach deren Angaben wurde das Problem behoben, indem der Webview2-Prozess als Ausnahme zu den Citrix-API-Hooks hinzugefügt wurde.

Dies kann durch das Befolgen der Anweisungen in [How to Disable Citrix API Hooks on a Per-application Basis](https://support.citrix.com/article/CTX107825) erfolgen.


---

# 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://docs.devolutions.net/rdm/de/knowledge-base/troubleshooting-articles/blank-page-issues-in-a-citrix-environment.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.