Getting Started & Installation
Guides and release notes are shown in their original language.
On this page
← All guides · GET STARTED
Synix is a local Windows desktop manager for personal game-server hosting. Official Windows x64 packages include the .NET 10 runtime. Games can still require their own Visual C++ packages, Java setup, accounts, agreements, or Windows features.
Install Synix
Choose an official method:
| Method | Use |
|---|---|
| SynixSetup.msi | Normal installer |
| Standalone Synix Control Panel executable from the same release | Run the official self-contained application without the MSI workflow |
| WinGet package ubidzz.Synix | Install/update the catalog's published Synix package |
For WinGet, use the exact package:
winget install --id ubidzz.Synix --exact
winget list --id ubidzz.Synix --exact
winget upgrade --id ubidzz.Synix --exact
WinGet availability can lag behind a GitHub release while its manifest is reviewed and published. The command installs the version available in that catalog, not necessarily a just-uploaded release.
Do not bypass installer hash checks. See Troubleshooting if a package is rejected.
Routine Synix/server management uses normal Windows permissions. Optional system changes or a particular game's deployment tool can require a separate Windows prompt.
Update an existing installation
- Finish active installs, backups, restores, and maintenance.
- Stop servers when needed for an orderly application update.
- Close the old Synix instance normally, including an instance running from the folder you want to replace.
- Install the new official package or replace the standalone application.
- Reopen and check server entries, paths, and pending recovery messages.
The MSI application normally installs under %LocalAppData%/Programs/Synix. Game-server data is separate.
Older versions through 1.0.20 used an Inno installer named SynixSetup.exe. Moving from that installer to the MSI may require removing the old application entry first. Preserve C:/Synix and custom server locations; do not delete game data as part of an app-only update.
Windows security/reputation warnings are different from an installer hash mismatch. Read security troubleshooting rather than disabling protection.
Create your first server
- Open Synix and let its initial setup finish.
- Choose Add Server, then create a server. Use Import Existing Server if the files already exist.
- Select the game and a unique local server name. For Minecraft, choose the correct edition/version/runtime.
- Review the configuration pages and fill in the required settings.
- Finish entering your settings, then use Review or the next-step button to open the review page. Typing in a password does not advance the page.
- Read the current summary, then use the save button on the review page. You can go back to change a setting before saving.
- Save, select the entry, and open Readiness.
- Start through Synix and follow the game's first-start prompts.
- Wait for the actual game to finish loading, then test locally before testing internet access.
- Create and verify a backup before adding mods or unattended maintenance.
Passing required checks does not skip Review. Changing settings after review requires reviewing the current choices again.
Saving an entry is not proof the game is installed or ready for players. Readiness and the game's own logs explain the next action. A process can be running while a world is still loading.
Setup pages
General, Security, World Generation, Network & RCON, Automation, Discord, and Install & Launch show fields applicable to the selected profile.
Beginner mode simplifies the interface; Advanced mode exposes additional technical choices. Neither bypasses validation or replaces the required review.
Seed generation is available for supported games. Changing the seed does not regenerate an already existing world. Use a new world or the game's supported procedure when a fresh world is intended.
See Server Configuration & Dashboard for the complete setup workflow.
Where data is stored
| Default location | Purpose |
|---|---|
| C:/Synix | Main managed data tree |
| C:/Synix/SteamCMD | Shared SteamCMD installation/download tooling |
| C:/Synix/Games | Default per-game/per-server installations |
| C:/Synix/BackupGames | Default rolling server backups |
| C:/Synix/SynixData/servers.json | Saved Synix server entries and protected values |
| C:/Synix/SynixData/AddOns | Server-scoped add-on bookkeeping and recovery files |
| C:/Synix/SynixData/logs | Synix diagnostic logs |
Custom paths can differ. Use Open Server Folder and Open Backup Folder instead of guessing a subfolder name.
Games may store saves outside their installation. Synix also uses ordinary Windows application settings; the data tree is not a sandbox containing every file any game can write.
Uninstall safely
Removing the application and deleting game-server data are separate decisions.
Before uninstalling or deleting a server, stop it and preserve wanted worlds, configuration, add-on recovery data, and backups. Review each deletion confirmation, especially any option to include backups. Do not manually delete the shared C:/Synix tree as an app-uninstall shortcut.
For another PC/account, use Backups, Restore & Transfers, including separate copies of external paths.
Next steps
First-start checks · Game List · Networking · Mods & Plugins · Troubleshooting