> 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/knowledge-base/troubleshooting-articles/citrix-environment-windows-crash.md).

# Citrix environment Windows crash

Prevent Windows crashes in a Citrix environment caused by repeated RDS credential prompts by disabling the Windows prompt on RDP sessions.

When an RDS server prompts for credentials, it uses adll and if we prompt it too many times by many users, Windows will crash.

### Solution

All the sessions must be configured not to use the Windows prompt. In the entries properties:

1. Change the Credentials type to ***Default***.
2. Check the box ***Always ask password***.

If you have many entries that needs to be changed, follow these steps (A backup of your database is recommended):

1. Select every RDP session that you need to edit (an [Advanced search](/rdm/ribbon-menu-bar/view/search/advanced-search.md) can be used).
2. Right click on them and select ***Edit – Edit (Special Actions)***.
3. Select ***Custom Powershell Command***.
4. And in the next windows type the text below:

   ```powershell
   $connection.PromptCredentials = $true;
   $RDM.Save();
   ```
5. Click ***OK*** Then every session will be configured with the prompt for credentials.


---

# 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/knowledge-base/troubleshooting-articles/citrix-environment-windows-crash.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.