> For the complete documentation index, see [llms.txt](https://docs.kouch.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kouch.dev/troubleshooting/create-a-report.md).

# Create a report

Make a report for the Kouch team in one step, and what is and isn't in it. Where the logs are.

When something goes wrong, tell the Kouch team **what you did**, **what you expected** and **what happened**, and attach a report.

## Make one

1. Open **Settings › About**.
2. Choose **Create a report for the Kouch team**. It takes a moment: **Creating the report…**
3. Kouch saves `kouch-report-<date>-<time>.zip` to your **Desktop** (the date and time are in UTC, and a new report never replaces an older one) and says where. **Open the report's folder** shows it.

Add a screenshot if the problem is something you can see.

## What's in it

* Kouch's logs from the last 3 days;
* your controllers: which kinds, not who owns them;
* your emulators' names and versions;
* your settings, with personal details removed;
* any settings file Kouch had to set aside because it was damaged.

## What's never in it

Game names or paths, saves, firmware, keys, your Steam account or Steam ID. The report is built so it can't include them.

## Settings › About

Besides the report, **About** shows:

* **Kouch:** the version, and the build it came from;
* **Steam:** **Connected** or **Not connected**;
* **Controllers connected**;
* **Motion server ports:** where Kouch passes controllers to emulators;
* a note if Kouch runs as administrator, and the alpha's note about Steam features;
* **Testing this alpha**, four quick tips, and **Show the tips again**.
* **Credits:** the controller icons and button glyphs come from Kenney (kenney.nl), under CC0.

## If Kouch won't start

Then there's no About screen, so send the log instead. **Open logs folder** in About opens it when Kouch runs. Otherwise:

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

```
%LOCALAPPDATA%\kouch\logs\kouch.<date>.log
```

{% endtab %}

{% tab title="Steam Deck / Linux" %}

```
~/.local/share/kouch/logs/kouch.<date>.log
```

{% endtab %}
{% endtabs %}

## Damaged settings

If a settings file is damaged, for example after a power cut, Kouch doesn't give up. It sets the file aside as `<name>.corrupt-<time>` and starts with defaults for that file. The next report includes the damaged file so the team can see what happened.

If the game library itself is damaged, Kouch starts a new one and says so. It finds your games again by itself, and keeps the old library file beside the new one.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kouch.dev/troubleshooting/create-a-report.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.