Skip to content
Weik.ioDocs
2026.2
Try Weik.io

Agents on Windows

Weik.io 2026.2

Run an agent on Windows Server 2022 or 2025, installed from an MSI that brings its .NET and Java runtimes.

On this page

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.

On Windows Server 2022 and 2025, an agent runs your integrations as it does on Linux. It links to Weik.io on port 443 and sends the same telemetry. A Windows agent runs integrations only, because a gateway at a site runs on Linux hosts. The installer, weikio-agent-win-x64-<version>.msi, puts everything the agent needs on the server. The agent’s identity comes from its folder, which Weik.io issues when you enrol the agent.

What the installer installs#

The installer puts the agent’s files in C:\Program Files\Weikio\Agent\:

  • The agent and its .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\, which has the collector’s module list otelcol-contrib.modules

It also registers the agent’s services, which start at boot and start again 10 seconds after a failure:

Service Runs as What it does
weikio-agent NT SERVICE\weikio-agent Runs the integrations, and stops them first when the server shuts down, within its pre-shutdown time of 120 seconds
weikio-leaf NT SERVICE\weikio-leaf Runs nats-server.exe with the agent’s link to Weik.io

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

Enrol a Windows agent#

Enrol the agent with --host windows, and give it capabilities and projects as for an agent on Linux:

Terminal
$ 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.

Install it on the server#

Download weikio-agent-win-x64-2026.2.4.msi from weik.io and check its SHA-256 against SHA256SUMS before you put it in the folder beside install.cmd. Copy the folder to the Windows server and run install.cmd as an administrator.

install.cmd first checks that Adafy Oy signed the installer and that the signature is valid. If the check fails, install.cmd stops and leaves a running agent as it is. Otherwise it stops the agent and runs the installer. Then it places the agent’s files in C:\ProgramData\Weikio. It makes the administrators the owner of that folder and sets who may read and write there. Last, it starts both services.

The install.cmd of a folder issued before 2026.2.3 doesn’t check the signature. If you installed an agent from such a folder, issue a new folder with weikio agent credentials agent-hq-w1 --out ./agent-hq-w1 and run its install.cmd as an administrator.

A known issue in 2026.2.4: under PowerShell’s Constrained Language Mode, install.cmd stops with the message that the installer isn’t signed by Adafy Oy, even when it is.

An install from the MSI alone, without the site’s folder, starts neither service.

Check the agent from your own machine:

Terminal
$ weikio get agents

Then delete the folder on both machines, because it contains the agent’s credential.

When install.cmd stops#

Message What to do
The installer weikio-agent-win-x64-<version>.msi is not signed by Adafy Oy, or its signature is not valid. Download the installer again from weik.io.
The folder C:\ProgramData\Weikio is a link to another folder, so the site's files would be written wherever it points. Remove the link with rmdir "C:\ProgramData\Weikio". The folder it points to stays as it is.
The folder C:\ProgramData\Weikio is owned by <account>, and the owner of a folder can always change who may read the files in it. Delete the folder if no agent was installed in it before. Otherwise make the administrators the owner of the folder and everything in it with takeown /F "C:\ProgramData\Weikio" /A /R.
The settings file <file> sets <name>, and a site's folder cannot set it. Delete that line from the folder’s agent.env.

After you fix the cause, run install.cmd again.

The agent checks the folder in the same way each time it starts. When the folder is a link or another account owns it, the agent doesn’t start and writes the reason to the Application log under the event source Weikio.Agent.

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 the account and, for a domain account, its password:

Property Default What it does
WEIKIO_SERVICE_ACCOUNT NT SERVICE\weikio-agent Sets the account that the agent and its integrations run as, such as a group managed service account EXAMPLE\weikio-site$ or a domain account
WEIKIO_SERVICE_PASSWORD None Sets the password of a domain account in WEIKIO_SERVICE_ACCOUNT
Terminal
msiexec /i weikio-agent-win-x64-2026.2.4.msi /qn WEIKIO_SERVICE_ACCOUNT=EXAMPLE\weikio-site$

Settings in agent.env#

Besides the lines Weik.io writes into C:\ProgramData\Weikio\agent.env, you can add a line for each setting you change:

Setting Default What it does
Weikio__Agent__HealthPort 6006 Sets the loopback port the agent serves its health endpoints on
Weikio__Agent__StopWindow 00:01:25 Sets how long the agent gives its deployments to stop when it stops
Weikio__Agent__Runtime__StopMargin 00:00:10 Sets how long a deployment’s process has to exit after Camel’s own stop time, before it’s killed
Weikio__Agent__Runtime__ClassDataFixedAddress false When true, deployments of the same Camel version share part of their memory

The agent loads the file when it starts, so restart the weikio-agent service after you change it. The agent ignores a setting with any other name and writes a warning that starts with The agent's settings file to the Application log.

Upgrade and uninstall#

To upgrade, 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 and settings. The telemetry that Weik.io hasn’t accepted yet stays there through the upgrade.

The installer’s version counts the year from 2000, so release 2026.2.2 has the installer version 26.2.2.

Before you uninstall, revoke the agent with weikio agent revoke agent-hq-w1. Uninstalling removes the agent from the server:

  • The program files
  • The services
  • The event source
  • C:\ProgramData\Weikio and the agent’s credentials in it

To install the agent again, issue a new folder with weikio agent credentials agent-hq-w1.

Sign in to the live demo

Sign in with the shared viewer account. It can open every screen of the example projects but can't change anything.

E-mail
viewer@demo.weik.io
Password
try-weikio-live-demo
Open the live demo