Typhon help: download, installation and game launch problems

Check the system and architecture on the download page. Windows needs WebView2 Runtime; Mac needs Apple Silicon and macOS 13 or later. For a macOS unsigned-application warning, use the first-launch instructions on the download page.

If the archive or installer is damaged, compare its SHA-256 with the published value. If they do not match, download the file again from the official page.

Check its status in Downloads: an item in the queue may not be downloading yet. Review speed and simultaneous-download limits in Settings, free space and disk availability.

BitTorrent needs reachable peers with the required data. Reinstalling Typhon cannot fix a lack of seeders. If the release list itself will not load, open Sources and check the error for that feed.

Open download log is available at the bottom of Downloads. Save the exact error before trying again.

Check whether automatic installation was enabled. If not, select Install for the completed download. During installation, look for a separate window waiting for confirmation or a folder choice.

Check unpacking space and destination-folder access. On Mac, make sure Typhon detects CrossOver. If an error appears, record it and save the log before retrying. Do not manually delete files while installation or cancellation is still running.

Check the EXE path: it should point to the game client, not an installer or helper program. If you moved files manually, check that the saved path still exists.

The game may require additional components or its own client. On Mac, also check the selected CrossOver environment and game compatibility. Successful installation and successful launching are separate outcomes.

Check that sharing is enabled on both computers and the game has finished preparing for sharing. Then check the network and firewall using the transfer guide. The feature is marked experimental in 0.5.1.

1. Record the Typhon and operating-system versions; add the CrossOver version on Mac.
2. Include the game, steps taken, expected result and actual result.
3. Copy the exact error and the time it appeared.
4. In Settings → About → Launcher logs, select Download logs.

Review the archive before sharing. Folder paths, the system username, email addresses, IP addresses and tokens are replaced in it with placeholders, but the names of games and releases, file names, source names and website addresses (without the path and parameters) stay, as does the system information in info.txt: the OS version, the processor model and the amount of memory. Scrubbing is not guaranteed, so download and read the archive first: an archive with the same contents is what gets sent. Send to us in the same place uploads the log to the server after confirmation and shows a number you can quote to support; from the Support section of the launcher you can attach the log to a request. If the upload fails, save the archive and describe the problem in a request.

Reproducible bugs can be discussed in the project’s GitHub Issues. Do not attach an unreviewed log archive to a public issue.