> 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/fr/knowledge-base/troubleshooting-articles/force-quit-the-remote-desktop-manager-application.md).

# Forcer la fermeture de l'application Remote Desktop Manager

Forcez la fermeture d'un processus Remote Desktop Manager planté à l'aide du Gestionnaire des tâches et essayez une installation portable si les plantages persistent au relancement.

Voici quelques étapes à suivre dans l'éventualité où Remote Desktop Manager plante et que vous devez forcer la fermeture de l'application.

### Solution

1. Ouvrez votre ***Observateur d'événements Windows***.
2. Cliquez sur ***Journaux Windows - Application*** et validez qu'il n'y a aucun problème lié au plantage.
3. Lancez le ***Gestionnaire des tâches***.
4. Dans l'onglet ***Processus***, repérez et effectuez ***Fin de tâche*** sur toutes les applications Remote Desktop Manager qui pourraient être en cours d'exécution.
5. Lancez Remote Desktop Manager.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Dans l'éventualité où Remote Desktop Manager plante toujours au relancement, essayez une <a href="/rdm/fr/knowledge-base/how-to-articles/portable-remote-desktop-manager-version.md">installation portable de Remote Desktop Manager</a>.</p></div>


---

# 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/fr/knowledge-base/troubleshooting-articles/force-quit-the-remote-desktop-manager-application.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.
