Skip to content
Setup FoundrySetup Foundry
DESign in

Documentation · Reference

Diagnostics and logs

Where to find logs and what to provide to support.

since 0.9.7.6

Purpose

The error log shows which step failed. It provides the information that Support needs.

Steps

  1. Open File Explorer.
  2. Enter %LOCALAPPDATA%\SetupFoundry\logs in the address bar.
  3. Press Enter.
  4. Open the file app_error_logs.log in a text editor.

The file contains the recorded errors.

Provide the following for a Support request:

  • the version of Setup Foundry
  • the Windows version on the computer
  • the exact error message
  • the time of the error
  • the file app_error_logs.log

Important

Copy the error message verbatim. The error pages in this documentation use the original wording as their heading.

Result

The log shows which step failed. The file app_error_logs.log is ready for Support.

Notes

Setup Foundry writes the error log to the data folder at %LOCALAPPDATA%\SetupFoundry\logs. The working folder from the setup wizard contains Windows sources, software, and finished media. The log is stored separately.

The headers at the start of the file identify it as an error report from this program. They may contain file and profile names, but no passwords or contents of your files. The file remains on this computer and is not sent automatically. You can delete it safely at any time.

Each time the program starts, Setup Foundry sets the existing file aside. Up to five older versions remain as app_error_logs.log.1, app_error_logs.log.2, and so on. During a long session, Setup Foundry starts a new file when the current one reaches 2 MB.

Logs can contain paths and account names, including the configured user name. Review a log file before attaching it publicly.

If it does not work

  • The logs folder is missing. Check that you are looking in %LOCALAPPDATA%\SetupFoundry. The folder is neither in the working folder nor beside the program. If the path is correct, no run has been performed on this computer yet.
  • The error log contains only the headers. No error has occurred since the last program start. Older errors are in files ending in .1, .2, and so on.
  • The log names a step but no cause. Report this case to Support. Attach the file and describe what you did immediately before it happened.

See also