How to report a problem

The three ways to reach us, what each one sends, and what to include so that the first reply is an answer rather than a question.

Three ways

From inside w0a. Settings has a Report a Problem card. Type what happened, add a contact address if you want an answer, and press Send. This is the fastest route for a bug, because the report arrives with the details below already attached.

By email or Discord. Both are on the Contact page. Email is better for anything about a licence or a payment, because we can match it to your order. Discord is better for a back-and-forth.

After a crash. When w0a fails badly enough to close, it shows a "Critical error:" box and asks whether to send a crash report. Nothing is sent unless you answer Yes, and it asks again every time.

What the in-app report sends

So you know before you press Send:

No screenshot, no file list and nothing else from your PC goes with it.

The card is in English on purpose, in every language w0a runs in, and it asks you to write in English. A person reads every report, and a description that has to be machine-translated first loses the part that matters most: your own words for what went wrong.

What to include

Four things. With these, most reports get an answer on the first reply instead of a round of questions:

  1. What you saw, in your own words. "Sound stopped after I ran the optimizer" is more useful than "audio bug".
  2. What you did just before. Which page, which button. If a repair card printed something, quote it exactly — the difference between "Fixed — 3 setting(s) put back to the Windows default." and "Nothing to fix — this was already at the Windows default." changes the answer completely.
  3. Your Windows version. Press Win+R, type winver, copy the line. The in-app report adds this for you.
  4. The last 120 lines of the log, if the problem is a crash or something not starting. It is at %LocalAppData%\w0a\errors.log. If w0a does not start at all, add startup-trace.log from the same folder.

If the problem is about a game feeling different with the background engines on, say which game and roughly when. engine.log in the same folder records what the engines did, line by line, and it stays on your PC unless you send it.

What not to send

Error lines may already have reached us through Send error diagnostics (Settings > Privacy, on by default, and only with a licence key entered). They tell us that something failed on some machines. Your description of what you were doing never arrives that way; it only arrives when you send it.

What happens then

We read all of it. If it is a bug, it goes on the list and you get told when the fix ships, if you left a contact address. If it is a question whose answer will help other people too, it becomes an article here — which is where most of these pages came from.

If the card says "Could not send", your report did not arrive. Try again later, or use email or Discord instead.

Related

Did this page help?

What was missing, or what did not work? We read every one of these.

If this page did not solve it, write to us — say which article you read, and we will fix the article.