Windows setup wizard

The Gluesync Windows setup wizard is the recommended MSI for installing Gluesync on Windows Server. Nothing in it runs PowerShell or VBScript at install time, so it works on servers where your security policy blocks PowerShell scripts. The previous MSI, gluesync-platform-installer.msi, is now the legacy MSI. It runs PowerShell scripts during the install and stays available for existing deployments and scripts.

Why use the setup wizard

Use gluesync-windows-setup-wizard.msi for new installations. It is the only MSI that installs on a server with one of these settings:

Group Policy sets the PowerShell execution policy to AllSigned, and MOLO17 SRL is not (or cannot be) added to Trusted Publishers.
The execution policy is Restricted.
Turn on Script Execution is disabled.
AppLocker or Windows Defender Application Control (WDAC) rules block scripts.

On such a server the legacy MSI stops with GS-PRE-070.

What is different

The setup wizard and the legacy MSI install the same product. The setup wizard is the recommended MSI. The legacy MSI runs PowerShell scripts during the install and is kept for existing deployments and scripts. The setup wizard differs in how the installer steps run:

Every installer step is compiled code signed by MOLO17 SRL. There are two components: gluesync-setup.exe and the custom-action DLL of the MSI.
gluesync-setup.exe is installed in C:\Program Files\Gluesync and copied to %ProgramData%\MOLO17\Gluesync\Installer.
The resume task (\MOLO17\GluesyncInstallerResume) and the launch window task run gluesync-setup.exe. They do not run powershell.exe.
It needs .NET Framework 4.7.2 or later. This is part of Windows Server 2019 and later.

Everything else is the same as in the legacy MSI:

The wizard screens and steps.
The prerequisite checks and the GS-PRE and GS-RUN codes. See Installer error codes and troubleshooting.
The status file at %ProgramData%\MOLO17\Gluesync\Installer\status.json.
The restart during the install, and the automatic resume as SYSTEM after the restart.
The silent install options.

Both MSI files are the same product. If you install one on a server that has the other, the new one replaces it.

System requirements

The system requirements are the same as for the legacy MSI. See System requirements in the Windows Server installation guide. In addition, the server needs .NET Framework 4.7.2 or later.

If the host runs antivirus or EDR software, agree on exclusions with your security team before you install. The same exclusions as for the legacy MSI apply. See Prepare antivirus and EDR software.

If Microsoft Defender Attack Surface Reduction (ASR) rules are in block mode, also exclude these paths:

C:\Program Files\Gluesync\*
C:\ProgramData\MOLO17\Gluesync\Installer\*

The installer lists these paths in the warning GS-PRE-080.

Download

Download: gluesync-windows-setup-wizard.msi

Install with the setup wizard

Download gluesync-windows-setup-wizard.msi.
Right-click the MSI in File Explorer and choose Run as administrator.
Follow the Setup Wizard. The steps are the same as for the legacy MSI: accept the End-User License Agreement, choose the destination folder, wait for the System Requirements Check, and enter your Gluesync kit ID (the 12 hexadecimal characters from your download e-mail). See Step-by-step setup for each screen.
Click Finish, and restart the server when Windows asks for it (the Containers feature needs a restart).
After the restart, the installation resumes automatically as SYSTEM; nobody needs to sign in. It installs the Docker engine and Docker Compose.
When you next sign in, a Gluesync launch window opens and starts the platform. Keep it open until it reports that Gluesync is running.

If a prerequisite check fails, the installer shows its GS-PRE code and a fix. See Installer error codes and troubleshooting.

Install silently

Run this command from an elevated command prompt:

msiexec /i gluesync-windows-setup-wizard.msi /qn GLUESYNCKITID=<kit id>

A silent install starts the platform on its own after the restart, without the launch window.

The options are the same as for the legacy MSI:

Property Use

Property	Use
`GLUESYNCKITID`	Your Gluesync kit ID: the 12 hexadecimal characters (0-9, a-f) from your download e-mail.
`GLUESYNC_ACCEPT`	A comma-separated list of codes to accept as warnings, for example `GLUESYNC_ACCEPT=GS-PRE-062,GS-PRE-081`.
`GLUESYNCTELEMETRY`	Set it to `0` to turn off telemetry.

GLUESYNCKITID

Your Gluesync kit ID: the 12 hexadecimal characters (0-9, a-f) from your download e-mail.

GLUESYNC_ACCEPT

A comma-separated list of codes to accept as warnings, for example GLUESYNC_ACCEPT=GS-PRE-062,GS-PRE-081.

GLUESYNCTELEMETRY

Set it to 0 to turn off telemetry.

In a silent install, the result is in %ProgramData%\MOLO17\Gluesync\Installer\status.json. See Diagnose a failed install.

What starts the platform

When the installation is complete, gluesync-setup.exe starts the platform with the same steps as the run.ps1 script of the kit:

It grants NT SERVICE\docker access to the installation folder.
It adds the system proxy to the .env file (PROXY_HTTP and PROXY_HTTPS).
It runs docker-compose pull (skipped once the platform has started once, when the .setup_completed file exists).
It runs docker-compose up -d --remove-orphans.

After the installation

Open the Gluesync Control Plane and configure your agents as described in Post-installation steps.

The installer itself runs no scripts, but the kit also contains PowerShell scripts: run.ps1, stop.ps1, update.ps1 and collect-logs.ps1. In kits generated from 14 October 2026, these scripts and the Gluesync control app are signed by MOLO17 SRL. If the execution policy is AllSigned, they run only when MOLO17 SRL is a trusted publisher on the server.