Installer error codes and troubleshooting

The Gluesync kit installers check the server before they install anything, and report every problem with a numbered code, a message and a fix. This page lists every code, where you find it, and how to diagnose an install that did not finish. It applies to installer kit 1.3.3 and later.

Where codes appear

Installer Where you see the code

gluesync-platform-installer.msi, setup wizard

In the error dialog (the text starts with the code) and in the System requirements dialog, where a failed check shows as [FAILED] GS-PRE-0nn. Next stays disabled while a requirement fails.

gluesync-platform-installer.msi, silent (msiexec /qn)

In status.json (errorCode, hint, lastExitCode), in logs\preflight.log, and in the MSI log when you install with /l*v <file>. msiexec returns 1603.

docker-installer-windows.ps1 and gluesync-platform-installer.exe

On the console: [ERROR] GS-PRE-0nn NAME: <message>, followed by Fix: <what to do>. The process exit code is 100 plus the number, for example 150 for GS-PRE-050.

docker-installer.sh (Linux)

On the console, for the disk check (GS-PRE-050, exit 1) and the kit ID (GS-PRE-030, exit 26).

status.json and the logs are in %ProgramData%\MOLO17\Gluesync\Installer. See Diagnose a failed install.

Prerequisite checks (GS-PRE)

The checks run before anything is downloaded. There are three kinds:

  • Hard block: the install always stops. No setting overrides it;

  • Soft block: the install stops, unless you accept the code as a warning with the GLUESYNC_ACCEPT MSI property (for example msiexec /i gluesync-platform-installer.msi GLUESYNC_ACCEPT=GS-PRE-062,GS-PRE-081) or with -Accept GS-PRE-062,GS-PRE-081 on docker-installer-windows.ps1. Only GS-PRE-061, GS-PRE-062, GS-PRE-063, GS-PRE-081 and GS-PRE-084 can be accepted;

  • Warning: the install continues. Warnings are listed in status.json (warnings).

Code Type Meaning Fix

GS-PRE-001 DOCKER_DESKTOP_PRESENT

Hard block

Docker Desktop is installed. It conflicts with the native Docker Engine for Windows containers that Gluesync installs (same C:\Program Files\Docker folder and docker_engine pipe).

Uninstall Docker Desktop (Settings > Apps), restart, then run the Gluesync installer again.

GS-PRE-010 NOT_ADMIN

Hard block

The account is not a member of the local Administrators group.

Run the installer with an account that is a local administrator.

GS-PRE-011 NOT_ELEVATED

Hard block

The installer is not running elevated. Silent installs cannot show a UAC prompt, so Windows rejects them (msiexec 1625).

Start the installer from an elevated prompt (Run as administrator), or deploy it as SYSTEM (SCCM, Intune, GPO).

GS-PRE-012 MSI_BLOCKED_BY_POLICY

Hard block

Windows Installer is blocked by Group Policy (DisableMSI, or enforced AppLocker MSI rules).

Ask your Windows administrator to allow MSI installs on this server, or to deploy the Gluesync MSI with SCCM, Intune or GPO (allow the MOLO17 publisher in AppLocker).

GS-PRE-020 CLIENT_EDITION

Hard block

This is a client edition of Windows. Gluesync for Windows needs Windows Server 2019, 2022 or 2025.

Use a Windows Server 2019, 2022 or 2025 host, or the Linux kit.

GS-PRE-022 NOT_X64

Hard block

Gluesync needs 64-bit (x64) Windows Server.

Use a 64-bit Windows Server.

GS-PRE-030 KIT_ID_INVALID

Hard block

The kit ID is not 12 hexadecimal characters, or it is empty on a silent install. Spaces around the ID and upper-case letters are accepted.

Run the installer again with GLUESYNCKITID (MSI) or the kit ID prompt set to the 12 characters (0-9, a-f) from your download e-mail.

GS-PRE-050 LOW_DISK

Hard block

Less than 100 GB free on the system drive, the Docker data-root drive or the install-folder drive (Linux: / and the Docker data-root). The lowest one is reported. This check cannot be overridden.

Free space on that drive, or move Docker’s data-root (C:\ProgramData\docker\config\daemon.json) to a disk with 100 GB free.

GS-PRE-051 LOW_RAM

Hard block

The server has less than 4 GB of RAM. Gluesync runs 7 Windows containers.

Add memory (at least 4 GB, 8 GB recommended).

GS-PRE-052 RAM_BELOW_RECOMMENDED

Warning

The server has between 4 GB and 8 GB of RAM. Gluesync works, but 8 GB is recommended.

Add memory if Gluesync runs slowly.

GS-PRE-060 PROXY_DETECTED

Warning

A machine proxy is configured. The installer downloads through it.

If downloads fail, allow the Gluesync and Docker hosts on the proxy. If the proxy inspects TLS, import its CA certificate into LocalMachine\Root.

GS-PRE-061 DOCKER_ENDPOINTS_UNREACHABLE

Soft block

Docker Hub or download.docker.com cannot be reached.

Allow HTTPS (443) to download.docker.com, registry-1.docker.io, auth.docker.io and production.cloudflare.docker.com (the Gluesync images are molo17/* on Docker Hub), or configure a registry mirror.

GS-PRE-062 MOLO17_ENDPOINTS_UNREACHABLE

Soft block

MOLO17 services cannot be reached.

Allow HTTPS (443) to molo17.com and api.backoffice.molo17.com, directly or on your proxy.

GS-PRE-063 GITHUB_UNREACHABLE

Soft block

GitHub cannot be reached (Docker Compose is downloaded from GitHub). A warning before the restart; a block in the check after the restart, right before the download.

Allow HTTPS (443) to github.com and objects.githubusercontent.com.

GS-PRE-080 DEFENDER_ASR_RISK

Warning

Microsoft Defender Attack Surface Reduction rules in Block or Warn mode can stop the freshly downloaded Docker binaries and the installer scripts.

If the install fails, add ASR exclusions: Add-MpPreference -AttackSurfaceReductionOnlyExclusions 'C:\Program Files\Docker*','C:\Program Files\Gluesync\*','C:\ProgramData\MOLO17\Gluesync\Installer\*'.

GS-PRE-081 DEFENDER_CFA_PROTECTS_DOCKER

Soft block

Microsoft Defender Controlled Folder Access protects Docker’s data folder, so dockerd.exe cannot write Windows container image layers.

Allow Docker: Add-MpPreference -ControlledFolderAccessAllowedApplications 'C:\Program Files\Docker\dockerd.exe','C:\Program Files\Docker\docker.exe' (or remove the folder from the protected list), then run the installer again.

GS-PRE-082 DEFENDER_NO_DOCKER_EXCLUSIONS

Warning

Microsoft Defender real-time protection scans Docker’s data folder. Microsoft recommends excluding it (performance and layer corruption).

Add-MpPreference -ExclusionPath 'C:\ProgramData\docker' -ExclusionProcess 'dockerd.exe','vmcompute.exe','vmwp.exe'

GS-PRE-083 THIRD_PARTY_AV_DETECTED

Warning

Security software is installed (for example Elastic Defend, CrowdStrike, SentinelOne, Sophos, Trend Micro, Symantec, Trellix, Carbon Black, Cortex XDR, ESET, Kaspersky, Bitdefender or Cylance). It can block Docker from writing or starting Windows container layers. The message names the product.

If Docker fails to start or pull images, ask your security team to exclude Docker, containerd, the folders C:\ProgramData\docker\windowsfilter and C:\ProgramData\docker\image, and the Gluesync install and kit folders. For Elastic, add them as trusted applications or endpoint exceptions in the Elastic Defend integration policy. See Prepare antivirus and EDR software.

GS-PRE-084 AV_BLOCK_OBSERVED

Soft block

An antivirus product blocked Docker during the Docker setup or the platform launch (for example a Controlled Folder Access event, or Access is denied while importing image layers).

Allow Docker in your antivirus or EDR (see GS-PRE-081 and GS-PRE-083), then run the installer again.

Runtime codes (GS-RUN)

These codes appear in status.json (errorCode) and in the logs when the install stops after the prerequisite checks: while downloading, setting up Docker or launching the platform.

Code Meaning Fix

GS-RUN-010 KIT_DOWNLOAD_FAILED

The Gluesync kit could not be downloaded.

Check HTTPS access to MOLO17 services (see GS-PRE-062) and the proxy, check the kit ID, then run the installer again.

GS-RUN-011 COMPOSE_DOWNLOAD_FAILED

Docker Compose could not be downloaded after the restart.

Allow HTTPS to GitHub (see GS-PRE-063). The resume task retries this step.

GS-RUN-012 DOCKER_DOWNLOAD_FAILED

The Docker Engine could not be downloaded after the restart.

Allow HTTPS to download.docker.com (see GS-PRE-061). The resume task retries this step.

GS-RUN-020 KIT_EXTRACT_FAILED

The kit zip could not be extracted.

Check free disk space and that no antivirus product quarantines the kit, then run the installer again.

GS-RUN-021 KIT_INVALID

The kit has no folder for this platform.

Use the Windows kit from your download e-mail, or contact MOLO17 support.

GS-RUN-022 KIT_COPY_FAILED

Copying the kit into the install folder failed.

Check permissions on the install folder and your antivirus exclusions, then run the installer again.

GS-RUN-040 PHASE2_MSIEXEC_FAILED

The Docker setup stage after the restart failed. An antivirus block in this stage is reported as GS-PRE-084 instead.

See logs\msi-phase2-*.log. The resume task retries this stage up to three times.

GS-RUN-050 LAUNCH_FAILED

The platform launch (run.ps1) exited with an error.

See C:\GluesyncSupport\Logs\launch-platform.log. The resume task retries the launch.

GS-RUN-055 NO_CONTAINERS_RUNNING

The launch finished, but no container is running.

Run docker ps -a and check the security software on the server (see GS-PRE-083). The resume task retries the launch.

GS-RUN-060 MAX_FAILURES

The install failed three times. The resume task is removed.

Fix the cause reported by the previous failure, then run the installer again.

GS-RUN-070 STATE_MISSING

The installer state or the cached MSI is missing.

Run the MSI again.

GS-RUN-090 RUNNER_EXCEPTION

Unexpected error in the resume task. It counts as a failure and is retried.

See logs\resume.log. If it repeats, contact MOLO17 support with the logs folder.

GS-RUN-091 PREFLIGHT_EXCEPTION

The prerequisite check itself failed (exit 91).

See logs\preflight.log and contact MOLO17 support with the logs folder.

Exit codes

msiexec

Code Meaning

0

Installed.

3010

The first stage is installed and Windows needs a restart. After the restart, the SYSTEM resume task continues the install. Check the final result in status.json.

1603

The install stopped. The code (GS-PRE-0nn or GS-RUN-0nn) and the fix are in status.json and in the MSI log.

1625

Windows refused the install before the installer ran: the prompt was not elevated, or Windows Installer is blocked by policy. There is no status.json. Run docker-installer-windows.ps1 -ExplainMsiExit 1625 to get the code (GS-PRE-010, GS-PRE-011 or GS-PRE-012).

1618

Another installation is in progress. Wait for it to finish, then run the installer again.

docker-installer-windows.ps1 and gluesync-platform-installer.exe

  • 0: installed, or only warnings;

  • 100 plus the number for a blocked check, for example 150 for GS-PRE-050 and 184 for GS-PRE-084;

  • 91: the check itself failed (GS-RUN-091);

  • 21 to 32: named fatal errors of the script, listed in Fatal exit codes.

Diagnose a failed install

Read status.json

%ProgramData%\MOLO17\Gluesync\Installer\status.json holds the result of the last install:

Field Meaning

result

InProgress, PendingReboot, PendingUserLaunch (setup-wizard installs: the launch window opens at the next sign-in), Succeeded or Failed.

phase / step

Where the install is, or where it stopped (for example preflight, phase2/msiexec, launch/verify-containers).

errorCode / errorName

The code of a failed install, for example GS-PRE-050 LOW_DISK.

hint

The fix for that code.

lastExitCode

The exit code of the failed step. For a blocked check: 100 plus the number.

warnings

Every warning of the run (code, name, message, hint). A Succeeded install still lists them.

message

A readable summary. While a step is retried, it ends with failure n/3.

Logs

  • %ProgramData%\MOLO17\Gluesync\Installer\logs\: preflight.log and preflight.json (the checks), install-containers.log, schedule-resume.log, resume.log (after the restart), msi-phase2-*.log (Docker setup), user-launch.log;

  • %ProgramData%\MOLO17\Gluesync\Installer\logs\docker-gluesync-installation.log: the log of docker-installer-windows.ps1;

  • C:\GluesyncSupport\Logs\launch-platform.log: the platform launch;

  • the MSI log, when you install with msiexec /i gluesync-platform-installer.msi /l*v C:\Temp\gluesync-install.log.

When you contact MOLO17 support, send status.json and the logs folder.

Run the checks without installing

Run the prerequisite checks and print the result without changing anything:

.\gluesync-platform-installer.exe -PreflightOnly
.\docker-installer-windows.ps1 -PreflightOnly -Json

Explain an msiexec exit code

Turn an msiexec exit code into a GS code with its fix. With -MsiLog, the code is read from the MSI log:

.\docker-installer-windows.ps1 -ExplainMsiExit 1603 -MsiLog C:\Temp\gluesync-install.log
.\docker-installer-windows.ps1 -ExplainMsiExit 1625

Run it in the same prompt that ran msiexec: for 1625 it checks that prompt’s rights (not elevated, not an administrator, or Windows Installer blocked by policy).