Agents on Windows

A Windows agent needs an installation on Weik.io 2026.2.2 or later. On 2026.2.0 and 2026.2.1 every agent runs on a Linux host. The weikio CLI runs on Windows on every release, installed with irm https://weik.io/install.ps1 | iex.

A Windows agent is the same agent as on Linux, with the same integrations, the same link to Weik.io on port 443 and the same telemetry. One installer, weikio-agent-win-x64-<version>.msi, puts everything on the server, and the agent’s folder, which Weik.io issues when you enrol it, gives it its identity. Windows Server 2022 and 2025 are supported.

What the installer installs#

The installer puts the agent and everything it runs with in C:\Program Files\Weikio\Agent\:

• the agent with its own .NET runtime
• a Java runtime built from Temurin JDK 21, which runs your Camel integrations
• nats-server.exe for the agent’s link to Weik.io
• rclone.exe for file transfers
• otelcol-contrib.exe, the OpenTelemetry collector, which keeps the agent’s telemetry in C:\ProgramData\Weikio\agent\telemetry until Weik.io accepts it
• licenses\, with the collector’s module list otelcol-contrib.modules

It also registers two services that start at boot and start again 10 seconds after a failure:

The agent writes to the Application log under the event source Weikio.Agent.

Enrol a Windows agent#

Enrol the agent with --host windows. Everything else works as for an agent on Linux, including capabilities and projects:

$ weikio agent enrol agent-hq-w1 --host windows --capabilities os=windows,environment=production --projects finance --out ./agent-hq-w1

The folder the CLI writes has the agent’s identity and an install.cmd. A gateway at a site runs on Linux hosts, so a Windows agent runs integrations.

Install it on the server#

Download weikio-agent-win-x64-2026.2.2.msi from weik.io, where SHA256SUMS gives its SHA-256, and put it in the folder beside install.cmd. Copy the folder to the Windows server and run install.cmd as an administrator. It runs the installer, passing the folder to it as WEIKIO_BUNDLE_DIR, and then loads the folder: Weikio.Agent.exe load-site <folder> places the agent’s files in C:\ProgramData\Weikio, sets who may read and write there and starts both services. Check the agent from your own machine, then delete the folder on both machines, because it contains the agent’s credential:

$ weikio get agents

A fresh install from the MSI alone starts neither service. The agent’s folder is what makes the server an agent’s host.

Run under a service account#

By default the agent, and every integration it runs, runs as NT SERVICE\weikio-agent. To run them as a group managed service account or a domain account, give the installer these properties:

msiexec /i weikio-agent-win-x64-2026.2.2.msi /qn WEIKIO_SERVICE_ACCOUNT=EXAMPLE\weikio-site$

Upgrade and uninstall#

Run a later release’s installer over the installed one. It replaces the program files and starts both services again. C:\ProgramData\Weikio stays, so the agent keeps its identity, its settings and the telemetry waiting for Weik.io. Windows Installer compares versions as three numbers, so the installer’s version is the release’s with the year counted from 2000: 2026.2.2 is 26.2.2.

Uninstalling removes the program files, the services, the event source and C:\ProgramData\Weikio with the agent’s credentials. Revoke the agent first with weikio agent revoke agent-hq-w1. To install the agent again, issue a new folder with weikio agent credentials agent-hq-w1.