Syncture-Setup.exe command line

Syncture-Setup.exe is one file that installs, updates, removes and checks Syncture on Windows. Every switch it takes and every code it returns is on this page.

The file

The same file for every release.

https://downloads.syncture.com/Syncture-Setup.exe

It holds no version of Syncture. When it runs, it reads which release is current, downloads that release's installer, checks its size, its SHA-256 and its signature by DI Osama Almughanni, BSc, and runs it. A package made from it today installs whatever is current on the day it runs, so it never needs replacing. Switches go to the release's installer unchanged.

Switches

Install, update and remove. Combine them freely.

(none): Opens Setup's window: what it found, Install for (Only me, or Everyone on this computer), and one button.
--silent: No window and no question. Also /S, /silent, /quiet, /q, /qn, /VERYSILENT and -s, in any case.
--uninstall: Removes Syncture. Revit has to be closed. Workspace keys and storage credentials stay on the computer. Also /uninstall and /x.
--machine: For every Windows account on the computer instead of the person signed in, with either of the above. Needs an administrator or SYSTEM: a window asks Windows for one, a silent run returns 740.
--offline <folder>: Installs the release in that folder, the release folder of the Syncture ZIP, and downloads nothing. Every file is still checked against its signature.
--log <file>: Writes the log to that file (also /log). Without it, %TEMP%\Syncture-Setup.log. The update task for everyone writes %ProgramData%\Syncture\Logs\Syncture-Setup.log.

Where it goes

Installed for one person, or for everyone on the computer.

Only me: The program in %LOCALAPPDATA%\Programs\Syncture, Revit's manifests in %APPDATA%\Autodesk\Revit\Addins, Installed apps under HKEY_CURRENT_USER. No administrator. It updates itself from inside Revit.
Everyone (--machine): The program in %ProgramFiles%\Syncture. Revit's manifests where each Revit reads them for every account: %ProgramFiles%\Autodesk\Revit\Addins for Revit 2027 and later, %ProgramData%\Autodesk\Revit\Addins for 2026 and earlier. Installed apps under HKEY_LOCAL_MACHINE, and one task, Syncture Update, that keeps it current as SYSTEM.
Both: Models, cache, sign-in and logs in %ProgramData%\Syncture. Never both scopes at once: an install for one person is refused where one for everyone exists, and steps aside when one arrives.

An install for one person updates itself from inside Revit, forty seconds after it starts and every two hours. An install for everyone cannot, because a Revit run by somebody without administrator rights may not write Program Files, so the task Syncture Update runs the installed Syncture-Setup.exe with --silent --machine as SYSTEM, every two hours and after Windows starts. Either way a new version goes in beside the one in use, and every Revit loads it at its next start. To hold every computer at one version, set TargetVersion as Deploying Syncture describes.

Exit codes

What a script or a deployment tool reads afterwards.

0: Done.
1: Failed. The log says why.
2: Revit is open, so Syncture could not be removed. Retry.
3: No Revit that Syncture supports is on this computer. A required assignment is offered again within about a day, so a Revit installed later still gets Syncture.
4: It ran as SYSTEM or another service account for one person. Run it in the user's context, or add --machine.
5: syncture.com could not be reached. Retry.
740: --machine without an administrator. Run it elevated, or as SYSTEM.
1602: The administrator prompt was cancelled. Nothing was changed.
1618: Another Syncture install is running on this computer. Retry.

Syncture-Setup.exe is a windowed program, so a shell does not wait for it on its own. In cmd, start it with start /wait. In PowerShell, use Start-Process -Wait -PassThru, or pipe it to Out-Host, which also shows what the key and storage tools print.

Commands

Copy, paste, adjust the path.

Install for the person signed in, with no window

Syncture-Setup.exe --silent

Install for everyone on the computer, as an administrator or SYSTEM

Syncture-Setup.exe --silent --machine

Install for everyone from the extracted ZIP, with no download

Syncture-Setup.exe --silent --machine --offline "C:\Install\Syncture-<version>\release"

Remove it for everyone

Syncture-Setup.exe --uninstall --silent --machine

Keep the log with the deployment's own logs

Syncture-Setup.exe --silent --log "C:\ProgramData\Deploy\Syncture.log"

In cmd, wait for it; %errorlevel% is then its exit code

start /wait Syncture-Setup.exe --silent

In PowerShell, wait for it and read the exit code

(Start-Process .\Syncture-Setup.exe -ArgumentList '--silent' -Wait -PassThru).ExitCode

Prove every computer has its workspace keys

.\Syncture-Setup.exe --key check | Out-Host

Without the download

For a computer that will not start a downloaded program.

In Windows PowerShell, this line runs the same installer inside PowerShell after checking its signature, so no new program starts:

irm https://syncture.com/install.ps1 | iex

The Syncture ZIP, from syncture.com/download.zip, holds the current release and Install.cmd, which installs from the extracted folder with nothing downloaded. Its release folder is what --offline takes, so a deployment tool can carry the ZIP to computers that cannot reach downloads.syncture.com.

Workspace keys

Encrypted workspaces need their key on every computer.

--key new: Prints one new workspace key on its output and writes nothing.
--key set <key>: Adds the key for the person signed in, or with --machine for every account (administrator or SYSTEM). It adds to what is there; --replace overwrites, and has to be typed.
--key check: Names every place a key may live and the id of each key in it, never a key. The exit code is the number of places in trouble.

The key tool needs no network and may run as SYSTEM. Rollouts by Group Policy, Intune or an RMM are in Deploying a workspace key.

Your own storage

Workspaces kept in a bucket you run.

--storage set: Deploys a credential: --endpoint, --bucket, --region, --access-key-id and --secret-access-key, with --name, --prefix and --path-style when needed, --machine for every account, and --replace to overwrite.
--storage set --from <file>: Deploys a prepared profile file instead of switches.
--storage check: Names every place a credential may live and the profiles in it by name, bucket and host, never a secret. The exit code is the number of places in trouble.
--storage probe --bucket <bucket>: Writes, reads and deletes one small object with the credential found here, and says what each step answered. Add --endpoint for a bucket outside AWS.

Like the key tool, it prints no secret. The whole setup is in Your own storage.