> 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/unigetui/help/troubleshooting/send-logs-to-support.md).

# Send logs to support

Collect the UniGetUI logs that support needs, hide your username from them, and send them.

Support can almost always tell what went wrong from the logs. This page shows which logs to collect, how to keep your username out of them, and where to send them.

## Which logs to send

All logs are in the ***More*** menu of the navigation menu.

<table><thead><tr><th width="240">LOG</th><th>WHAT'S IN IT</th><th width="220">SEND IT WHEN</th></tr></thead><tbody><tr><td><strong>Operation history</strong></td><td>Every install, update and uninstall, with its status and full output.</td><td>An operation failed.</td></tr><tr><td><strong>Package Manager logs</strong></td><td>The commands each package manager ran and their output.</td><td>Apps are missing, or a manager misbehaves.</td></tr><tr><td><strong>UniGetUI Log</strong></td><td>Events and errors of UniGetUI itself.</td><td>Always.</td></tr></tbody></table>

## Collect them

{% stepper %}
{% step %}

### Hide your username (optional)

Logs can contain file paths with your username.

1. Go to ***Settings*** – ***General preferences*** and turn on ***Hide my username from the logs***.
2. Restart UniGetUI, so older entries are hidden too.
3. Reproduce the problem.
   {% endstep %}

{% step %}

### Copy the failed operation

1. Open ***More*** – ***Operation history***.
2. Right-click the failed operation and select ***View full log***, then copy it. ***Copy details*** gives a shorter summary.
   {% endstep %}

{% step %}

### Export the other logs

1. Open ***More*** – ***Package Manager logs***. In ***Log level:***, select the manager involved, in its ***(Verbose)*** version, then click ***Export to a file***.
2. Open ***More*** – ***UniGetUI Log***. In ***Log level:***, select ***5 - information (debug)***, then click ***Export to a file***.
   {% endstep %}

{% step %}

### Note your version

The UniGetUI version is shown in the ***More*** menu and in ***About***. Add it to your message.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Read the logs before you send them. Even with your username hidden, they can contain computer names, folder names and the list of your apps.
{% endhint %}

## Send them

Attach the files to your request to [Devolutions support](https://devolutions.net/support/), or to an issue on the [UniGetUI GitHub repository](https://github.com/Devolutions/UniGetUI/issues).

{% hint style="danger" %}
GitHub issues are public. Don't attach logs that contain anything you don't want to publish.
{% endhint %}

## If UniGetUI won't open

* **It crashes at startup:** run `UniGetUI.exe --no-corrupt-dialog` to get the detailed crash report instead of the simplified dialog, and send that report.
* **The window is unusable but UniGetUI runs:** collect the logs from the command line:

```powershell
unigetui log app --level 5 > unigetui-app-log.json
unigetui log manager --manager winget --verbose > unigetui-winget-log.json
unigetui log operations > unigetui-operations.json
```

* **Nothing else works:** UniGetUI also writes a `session.log` file in `%TEMP%\UniGetUI` on Windows (`Settings\Temp` in the installation folder for a portable installation).

See [Command-line interface](/unigetui/reference/cli.md) for all the log options.


---

# 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/unigetui/help/troubleshooting/send-logs-to-support.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.