Skip to main content

How to collect AdGuard logs

info

This article covers AdGuard for Windows, a multifunctional ad blocker that protects your device at the system level. To see how it works, download the AdGuard app.

note

Data and files provided in logs are processed in accordance with the AdGuard Privacy Policy.

To diagnose problems you may encounter while using AdGuard, our support team may need AdGuard log files. These files record errors and other events that occur in the application. This article explains how to change the logging level, collect the logs, and send them to support.

AdGuard for Windows offers two logging levels: Default and Debug. For most troubleshooting, Debug is sufficient, but it may slow down the app.

How to change the logging level​

You can change the logging level in either of two ways:

Option 1: In the app​

Go to AdGuard settings → Support → Logs, and in the Logging level dropdown select Debug.

Logging level dropdown on Support page *border

Option 2: From the tray menu​

Right-click the AdGuard icon in the system tray, select Advanced → Logging level, and choose Debug.

Logging level in tray menu *border

Debug logs​

For most issues, debug logs give the support team enough information to identify and fix the problem.

  1. Set the logging level to Debug using one of the methods described above.

  2. Reproduce the issue. Note the exact time — it will help our support team find the relevant log entries and solve the problem faster.

  3. Go to AdGuard settings → Support → Logs, and click Export logs and system info.

    Once the export is complete, you’ll see a confirmation message. You can click Show in folder to open the folder where the exported archive with logs and system information was saved.

    note

    Set the logging level back to Default after exporting the logs. The Debug level slows down the application.

:::

  1. Send the archive to support@adguard.com, describe the problem, and mention the time you reproduced the issue.

Trace logs​

Sometimes the support team may ask you for trace logs. Trace logging captures more detail than debug logging and is only available via command line.

  1. Exit AdGuard by right-clicking the AdGuard icon in the tray menu and choosing Exit AdGuard.

    Exit AdGuard *border

    If prompted to keep the service running in the background, make sure to stop it — the service must not be running when you start AdGuard with trace logging.

  2. Open the command prompt (type cmd in the Start menu search).

  3. Run AdGuard with trace logging enabled:

    C:\"Program Files"\Adguard\Adguard.exe /trace

  4. Reproduce the issue. Note the exact time — it will help our support team find the relevant log entries and solve the problem faster.

  5. Export the collected logs: go to Settings → Support → Logs → Export logs and system info.

    Don’t worry if the log file is large — we need as much detail as possible to fix your problem.

  6. After exporting the trace logs, close AdGuard and restart it normally to return to the default logging level.

Diagnostic report​

When contacting support through the form in Settings → Support, you can include a diagnostic report that automatically attaches application logs together with other system information.

The diagnostic report includes:

  • Information about the system
  • A list of running processes
  • Details about AdGuard settings, including enabled filters and installed extensions
  • Application logs

To use this option, check the Add diagnostic report checkbox before sending your message.

Diagnostic report option *border

note

AdGuard is committed to protecting your privacy. We strictly follow our Privacy Policy and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first.