Finding Logs for MuteDeck Support

When you contact MuteDeck support, we may ask for your log file and a few details about your setup. This helps us see what MuteDeck detected, which meeting app was active, and whether anything failed in the background.

Windows

1. Press Win + R.
2. Paste this path: %LOCALAPPDATA%\MuteDeck
3. Press Enter.
4. Attach this file to your support reply: mutedeck.log

Full path: %LOCALAPPDATA%\MuteDeck\mutedeck.log

macOS

1. Open Finder.
2. In the menu bar, choose Go → Go to Folder…
3. Paste this path: ~/Library/Application Support/MuteDeck
4. Press Enter.
5. Attach this file to your support reply: mutedeck.log

Full path: ~/Library/Application Support/MuteDeck/mutedeck.log

Other files that may help

If support asks for the full MuteDeck data directory, send the contents of the same folder listed above.

It may include files such as:

• mutedeck.log
• mutedeck.db
• mutedeck.dat

The log file is usually the most important one. Only send the other files if support specifically asks for them.

Automatic Crash Reports

From v4.13, Settings → General → Send crash reports lets MuteDeck send technical crash reports automatically. This is separate from the log file and from anonymous usage statistics. See what crash reporting includes and how to turn it off.

If you contact support about a crash, still include the details below and any logs requested so we can investigate your specific issue.

If MuteDeck is crashing on macOS

macOS may create a crash report separately from the MuteDeck log.

To check:

1. Open Console.app.
2. Go to Crash Reports.
3. Look for reports named MuteDeck.
4. If there is a recent report, attach it to your support reply.

Include these details too

When sending logs to support, please also include:

• Your MuteDeck version.
• Your operating system and version.
• Which meeting app you are using, for example Zoom, Microsoft Teams, Slack, Discord, or the other app.
• A screenshot that shows both the active call and MuteDeck at the same time, if possible.