> 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/password-manager/fr/knowledge-base/application-knowledge-base/lost-the-master-key-set-on-the-devolutions-password-manager-desktop-app.md).

# Perte de la clé maîtresse définie dans l'appli de bureau Devolutions Password Manager

Récupérer Devolutions Password Manager après avoir perdu la clé maîtresse en supprimant le fichier local shared\_preferences et en relançant l'appli de bureau.

Pour effectuer une installation propre de Devolutions Password Manager ou pour réinitialiser l'application en cas de perte de la clé maîtresse, supprimez le fichier de données local.

{% tabs %}
{% tab title="Windows" %}

### Solution

1. Fermez Devolutions Password Manager.
2. Trouvez et supprimez le fichier `shared_preferences.json` (chemin par défaut : `%AppData%\net.devolutions\Devolutions Password Manager`).
3. Lancez Devolutions Password Manager.
   {% endtab %}

{% tab title="macOS" %}

### Solution

1. Fermez Devolutions Password Manager.
2. Exécutez la commande suivante dans le Terminal : `defaults delete net.devolutions.authenticator`
3. Lancez Devolutions Password Manager.
   {% endtab %}

{% tab title="Linux" %}

### Solution

1. Fermez Devolutions Password Manager.
2. Trouvez et supprimez le fichier `shared_preferences.json` (chemin par défaut : `/home/<user>/.local/share/Devolutions Password Manager/`).
3. Lancez Devolutions Password Manager.
   {% endtab %}
   {% endtabs %}


---

# 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/password-manager/fr/knowledge-base/application-knowledge-base/lost-the-master-key-set-on-the-devolutions-password-manager-desktop-app.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.
