Installing the launcher

Installer not published yet

The wfx.re landing page links to /download/WildM-Setup.exe, but no installer is published at the moment (the master server's downloads/ folder does not exist yet). During development the launcher is run from source — see For testers: running from source.

Where WildM lives on your PC

Everything is in your Windows user profile, never in the game folder:

Path	Contents
%USERPROFILE%\WildM\settings.json	Launcher settings: player name, game folder (if set by hand), master server URL, favourites, history, linked account
%USERPROFILE%\WildM\client\	The installed WildM client: dinput8.dll, wildm_inject.exe, plugins\…, the client's logs and ini files, wildm_connect.json, wildm_status.json
%USERPROFILE%\WildM\client\.wildm_installed.json	The list of files the launcher installed (used to remove only those when they disappear from a new build)
%USERPROFILE%\WildM\cache\<host>_<httpPort>\	Resources downloaded from each server you joined

TIP

Paste %USERPROFILE%\WildM into the Explorer address bar to open the folder.

Why not %APPDATA%?

Until 2026-11-14 the data lived in %APPDATA%\wildm-launcher. Windows redirects AppData for programs started from a packaged (MSIX) app: the launcher then wrote into a private copy while the game read the real folder, and the connection stayed stuck at 55 %. %USERPROFILE%\WildM is never redirected. The launcher copies your old settings.json and cache over on first start. Set the WILDM_HOME environment variable to use another folder.

First start: the boot checks

The launcher opens a small splash window and runs these checks (each one shows ✓, ! or ×):

Check	What it does
Launcher files	Verifies its own assets (logo, fonts).
Finding Ghost Recon Wildlands	Manual folder → Ubisoft Connect → Steam. A warning if the game is not found; set the folder in Settings → Game.
Licence	Starts Steam (-silent) for the Steam version, and Ubisoft Connect in the background (its window is hidden). The licence itself is checked by the platform when the game starts.
Anti-cheat	Scans the game folder. Anti-cheat files found → × (launching will be blocked).
WildM services	Contacts the master server (/version, /servers). Offline is only a warning.
Client updates	Installs or updates the client in %USERPROFILE%\WildM\client\ if it differs from the latest build, and removes legacy files from the game folder if the game is closed. Warns if a newer client version is published on the master.
WFX.re account	Checks the saved session with /auth/me. No account or an expired session → you are offered to link one.

Then the account screen appears if needed (Linking your account); Later skips it.

Settings

Open Settings (Paramètres — the launcher UI is currently in French) from the main window. Three tabs:

Tab	Options
Account (Compte)	The linked WFX.re account and Sign out. Player name (max 24 characters) — shown to other players. If empty, your account name is used, then Joueur.
Game (Jeu)	Status (game detected, client built, client installed). Game folder with Change (must contain GRW.exe). Install / Reinstall, Uninstall the client, Check anti-cheat.
Network (Réseau)	Master server URL. Default https://wfx.re; point it at http://127.0.0.1:7777 to use a master you run locally.

Uninstall deletes %USERPROFILE%\WildM\client\ and, if old WildM files are still in the game folder from an early build, restores the original files (the game must be closed).

Client updates and your settings

When the client is (re)installed, the launcher copies the whole client build, sub-folders included, except build artefacts (.pdb .ilk .lib .exp .obj .o .iobj .ipdb .map .tmp).

• .ini files are copied only if they do not exist yet, so your settings survive updates.
• Files written by the client itself (logs, crash reports, ini) are never deleted by an update; only files listed in .wildm_installed.json that disappeared from the new build are removed.

For testers: running from source

cd launcher
npm install
npm start          # electron .

In development the launcher installs the client from grw-mp/build/ (a packaged launcher would use its own resources\client\). You also need a master server to talk to — npm run master in launcher/ starts ../master-server/server.js on port 7777.