Skip to main content
Whatcha need to Know?
Table of Contents
< All Topics
● Knowledge Base · Troubleshooting

Having Issues?

Quick checklist to get back to working. If a recent update introduced the problem, grab an older build first to confirm it’s the cause — then try a prefs wipe.

Try a prefs wipe

Many problems are fixed by deleting all your .settings files. Quit basehead, delete them, and relaunch.

Windows Settings folder

%APPDATA%\basehead\

macOS Settings folder

~/Library/Application Support/basehead/

Capture a log for support

Open Help → Create Log For Support, then:

  1. Click Clear to start a fresh log.
  2. Reproduce the problem.
  3. Click Show Log File and send us the Debug.log file.
  4. Close the panel.

The Log panel uses extra CPU and memory while it’s open — only open it to capture a problem. It shows the last 2,000 lines, but Debug.log always has the full log.

Send your User.log

If a prefs wipe doesn’t help, send us your User.log. Same path on Windows and macOS:

~/Documents/basehead/User.log

Attach the log to a Support Ticket. You can also create one from your account dashboard.

System crash logs

Windows Event Viewer

If basehead is crashing, also submit a .evtx file from Windows Event Viewer:

  1. Open Event Viewer → Windows Logs → Applications.
  2. Right-click and choose Save Selected Events.
  3. Attach the .evtx file to your support ticket.
Windows Event Viewer — Save Selected Events on Windows Logs/Application

macOS Diagnostic Reports + Console

Apple crash logs live here:

~/Library/Logs/DiagnosticReports/ (~ is your Home folder)

Send the User.log and the Console output captured at the time of the crash:

macOS Console showing log output during a basehead crash