Troubleshooting and logs

When something looks wrong, the log file is the first place to look.

Find the log file

MaxTo writes a JSON log to:

%AppData%MaxTomaxto-log.json

The log rolls daily and on size, so you’ll usually see one or two .json files alongside it. The most recent file is what you want.

Each line is a JSON object — open the file in any text editor and search for the term that matches your problem.

Common issues

My hotkey doesn’t do anything

Another application has probably already registered the same combination. Search the log for Failed to register hotkey; that line names the combination MaxTo couldn’t grab.

Pick a different combination under Settings → Shortcuts. See Customize your hotkeys for which combinations tend to be free.

The resize overlay has a black background

This is expected on systems where Windows can’t render Mica — most commonly remote desktop sessions and virtual machines without GPU acceleration or with transparency disabled. Functionality is unaffected; the overlay still works correctly.

The trial says it’s expired right after I installed

MaxTo detects clock rollback. If your system clock drifts backwards by more than an hour, MaxTo treats the trial as expired to prevent indefinite re-runs.

Set the system clock to the correct current time and re-launch MaxTo. The trial resumes from where it should.

File a bug

If something’s broken and the log doesn’t help, open an issue on GitHub at https://github.com/domino-as/maxto/issues. Attach the relevant log file (or the lines that look related) and describe what you expected vs. what happened.