Hinweis! Dieser Inhalt wurde noch nicht übersetzt und ist nur auf Englisch verfügbar.


If you should encounter any issues with MaxTo, here are some steps to help you identify what is happening.

Some of these steps require advanced PC knowledge. We will explain as clearly as we can, and will be clear whenever we suggest doing anything destructive.

Log files

MaxTo produces quite a bit of log data when it is installed and running. These are the locations where you can expect to find useful information should you experience a crash or unexpected behavior:

Runtime logs

This log file contains entries about what MaxTo is doing at specific points in time, including any crashes that MaxTo experience. You will find this file in %AppData%\MaxTo\maxto.log.

You can see the file paths we specify contain special variables (such as %AppData%). These expand into full paths on your machine, but can be different from computer to computer.

To quickly open the log file, hit + R on your keyboard, and copy in the path to the file. Then press OK, and the file should open in your default text editor (usually Notepad).

Each line in this file is timestamped; and the file can grow quite large. If you can reliably reproduce your issue, it could be helpful to delete the log file before trying to reproduce the issue — that way there will be less data for us to read when we try to figure out what is going on.

Here is an excerpt from the log file, with specific bits of information highlighted:

2018-11-26 21:36:42 [[email protected]] [Information] 3 processes started
2018-11-26 21:36:43 [[email protected]] [Information] Found no specified configuration location file, using default settings location "C:\Users\vegar\AppData\Roaming\MaxTo"
2018-11-26 21:36:43 [[email protected]] [Information] Found no specified configuration location file, using default settings location "C:\Users\vegar\AppData\Roaming\MaxTo"
2018-11-26 21:36:43 [[email protected]] [Information] Activated "MaxTo.UI.ViewModels.NotificationIconViewModel"
2018-11-26 21:36:44 [[email protected]] [Information] Read shims from "C:\Users\vegar\AppData\Local\MaxTo\shims.json"
2018-11-26 21:36:44 [[email protected]] [Information] Read shims from "C:\Users\vegar\AppData\Local\MaxTo\shims.json"
2018-11-26 21:36:44 [[email protected]] [Information] Enabled hook
2018-11-26 21:36:45 [[email protected]] [Information] Enabled hook

Each line has a log level, which indicates the severity of what is being reported. The log levels are, in order from least to most important:

Trivial events that specify in very intricate detail what is being done.
Events that carry information about normal program behavior.
Events that may indicate something is off; but may be totally trivial.
Something went wrong, but not badly enough that the program crashed.
Something went so wrong that MaxTo couldn't recover and exited.

Installation logs

If you use the normal installer, it generates a log file during installation in %LocalAppData%\SquirrelTemp\SquirrelSetup.log.

Note that the installation log may also contain information about other programs on your machine; as other program may use the same installer as MaxTo does.