Installers changelog

Prerequisite checks run before anything is downloaded. A failed check stops the install with a numbered code (GS-PRE-0nn), a message and a fix. The code is shown in the error dialog, the MSI log and status.json, and msiexec returns 1603. The codes are listed in Installer error codes and troubleshooting;

The install is blocked when the system drive, the Docker data-root drive or the install-folder drive has less than 100 GB free (GS-PRE-050). This applies to setup-wizard and silent installs and cannot be overridden;

The setup wizard shows RAM, Docker Desktop and free disk space in the System requirements dialog. Next is disabled while a requirement fails;

An invalid kit ID, or an empty kit ID on a silent install, stops with GS-PRE-030. The kit ID is trimmed and converted to lower case before it is checked;

A silent install started from a non-elevated prompt stops with GS-PRE-011 before any download;

The installer checks that MOLO17, Docker and GitHub endpoints are reachable, and reports a configured machine proxy (GS-PRE-060). Downloads go through the machine proxy;

Microsoft Defender checks: a warning when Docker’s data folder has no exclusion (GS-PRE-082) or when ASR rules may interfere (GS-PRE-080), and a block when Controlled Folder Access protects Docker’s data folder (GS-PRE-081);

Endpoint protection products, including Elastic Defend, are reported as a warning with the folders and processes to exclude (GS-PRE-083);

When an antivirus product blocks Docker during the Docker setup stage or the platform launch, the install fails with GS-PRE-084 instead of a generic error;

After the restart, before the Docker setup stage, the resume task checks Docker Desktop, Docker and GitHub reachability, and Controlled Folder Access again. A block is reported with exit code 100 plus the check number;

Soft blocks (GS-PRE-061, GS-PRE-062, GS-PRE-063, GS-PRE-081, GS-PRE-084) can be accepted as warnings with the GLUESYNC_ACCEPT property, for example GLUESYNC_ACCEPT=GS-PRE-062,GS-PRE-081. No value accepts GS-PRE-050 or any hard block;

status.json (schemaVersion 2) adds the prerequisite result: errorCode, errorName, hint and warnings;

When a prerequisite check stops an install and the kit ID is known, the installer sends an install-failure notice with the code. No notice is sent without a valid kit ID;

After a successful install, the online MSI sends an install-success confirmation. The offline Windows installer does not;

Correct handling of the Windows "restart required" result (exit code 3010). The installer no longer hides that result;

After the reboot, the install resumes automatically as a SYSTEM startup task. No logon is required. This replaces the previous RunOnce resume;

Writes a status file at %ProgramData%\MOLO17\Gluesync\Installer\status.json. The result values and the resume task exit codes are listed below;

Silent installs start the platform in the background. Setup-wizard installs still open the visible launch window for the installing user;

A retry resumes from the failed step. It does not reinstall from the beginning;

Copying the Docker binaries no longer fails when Docker is already running;

The install is blocked when / or the Docker data-root has less than 100 GB free (GS-PRE-050, exit 1). It cannot be overridden;

The kit ID is trimmed and converted to lower case before it is checked. An invalid kit ID is logged as GS-PRE-030 and still exits 26;

The same prerequisite checks as the MSI run before the install. A failed check prints [ERROR] GS-PRE-0nn NAME, a message and a fix, and exits with 100 plus the number. The codes are listed in Installer error codes and troubleshooting;

-PreflightOnly runs the checks without installing anything. Add -Json for a machine-readable report;

-ExplainMsiExit <code> explains an msiexec exit code, for example 1603 or 1625. Add -MsiLog <path> to read the GS code from an MSI log;

-Accept GS-PRE-062,GS-PRE-081 (or $env:GLUESYNC_ACCEPT) accepts soft blocks as warnings. No value accepts GS-PRE-050 or any hard block;

After the restart (-ContinueAfterReboot), Docker Desktop, Docker and GitHub reachability, and Controlled Folder Access are checked again before Docker is installed;

With Microsoft Defender Controlled Folder Access on, the script no longer stops with an unexplained error. It reports GS-PRE-081 before the install, and GS-PRE-084 (exit 184) when Controlled Folder Access blocks the Docker install;

A failed Docker install is no longer reported as completed;

The log file is now %ProgramData%\MOLO17\Gluesync\Installer\logs\docker-gluesync-installation.log (or %TEMP% when that folder cannot be written). It was written to the current folder;

A desktop shortcut that cannot be created is a warning, not a failed install;

After a successful install, the online script sends an install-success confirmation. The offline Windows installer does not;

The install is blocked when the host has less than 4 GB of RAM, and warns when RAM is between 4 GB and 8 GB;

Docker Compose download tries Invoke-WebRequest first, then BITS, then curl.exe. The downloaded file must run as docker-compose, or the install stops;

The script reports success only when the platform is running: run.ps1 exited 0 and the containers are up;

Named fatal errors print GS-RUN-<CODE> and exit with the codes below;

Stronger error handling and logging for endpoint reachability (Gluesync 2.2.2.0, Released: March 19, 2026);

Windows Server 2019 support, with Docker 28.5.2 enforced on that release (8fbcc6f7, March 1, 2026; ccf07728, March 2, 2026);

Linux offline installer available as early access (Gluesync 2.2.2.0, Released: March 19, 2026);

Linux offline installer generally available, including the dependencies needed to run Gluesync and offline updates (Gluesync 2.2.3.0, Released: March 23, 2026);

Windows offline installer available (Gluesync 2.2.3.0, Released: March 23, 2026);

Offline installers accept versioned platform archives named by architecture and prefix, not only the unversioned alias (7b876155, September 6, 2026);