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

# Verlust des in der Devolutions Password Manager Desktop-App festgelegten Hauptschlüssels

Stellen Sie Devolutions Password Manager nach dem Verlust des Hauptschlüssels wieder her, indem Sie die lokale Datei shared\_preferences löschen und die Desktop-App neu starten.

Um eine Neuinstallation von Devolutions Password Manager durchzuführen oder die Anwendung bei Verlust des Hauptschlüssels zurückzusetzen, löschen Sie die lokale Datendatei.

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

### Lösung

1. Schließen Sie Devolutions Password Manager.
2. Suchen und löschen Sie die Datei `shared_preferences.json` (Standardpfad: `%AppData%\net.devolutions\Devolutions Password Manager`).
3. Starten Sie Devolutions Password Manager.
   {% endtab %}

{% tab title="macOS" %}

### Lösung

1. Schließen Sie Devolutions Password Manager.
2. Führen Sie den folgenden Befehl im Terminal aus: `defaults delete net.devolutions.authenticator`
3. Starten Sie Devolutions Password Manager.
   {% endtab %}

{% tab title="Linux" %}

### Lösung

1. Schließen Sie Devolutions Password Manager.
2. Suchen und löschen Sie die Datei `shared_preferences.json` (Standardpfad: `/home/<user>/.local/share/Devolutions Password Manager/`).
3. Starten Sie 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/de/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.