news-rwa

rsyslog Windows Agent 8.4a Released

Adiscon has released rsyslog Windows Agent 8.4a, a maintenance update for the rsyslog Windows Agent 8.4 line.

This update ships Service 8.4.0.241 and Client 8.4.0.335. It updates the included OpenSSL libraries to version 3.5.9 and includes maintenance for the Syslog Listener.

Changes

  • Updated the included OpenSSL libraries to version 3.5.9.
  • Syslog Listener: Bounded header parsing to prevent malformed messages from interrupting service availability.

Details are in the version history. The versioned installer is rsyslog Windows Agent 8.4a.

rsyslog Windows Agent 8.4a Version History

Release date: 2026-11-04.

Build IDs: Service 8.4.0.241, Client 8.4.0.335.

Bugfixes

  • Updated the included OpenSSL libraries to version 3.5.9.
  • Syslog Listener: Bounded header parsing to prevent malformed messages from interrupting service availability.

Download

The versioned installer is rsyslog Windows Agent 8.4a, 88 MB. SHA-256: 3ca3dbf94b593f9651f11423e33c2a2722105ae5345b2ecfc917ec240748eb4e.

The announcement is the rsyslog Windows Agent 8.4a news release.

rsyslog Windows Agent 26.11: Monthly Patch + Feature Drop

rsyslog Windows Agent 26.11 is the latest monthly Patch + Feature Drop. It adds manual hostname mappings and corrects Syslog Listener handling, TLS forwarding, remote configuration, and service diagnostics.

Map hostnames and IP addresses

General settings can define hostname and IP address mappings. The mappings are available in the Configuration Client and in the User Interface.

Safer forwarding and configuration

The Syslog Listener rejects malformed message headers. TLS and DTLS forwarding verify destination certificates and identities, and stalled TLS forwarding no longer blocks shutdown indefinitely. Remote configuration rejects invalid HTTPS certificates and insecure redirects. Registry configuration detects the default license file more reliably when the license path is empty and no separate data directory is configured. When a listening socket cannot be opened, diagnostics include possible owners. The Configuration Client and the User Interface do not save a partial configuration after loading fails, and they preserve existing settings when a selective import fails. The Syslog action can set the TLS send progress timeout. The User Interface dashboard displays content in the selected language.

The User Interface remains in preview. It is available for production use with appropriate care and review; the Configuration Client remains fully supported.

We recommend keeping rsyslog Windows Agent on the latest Patch + Feature Drop to benefit from current maintenance and product improvements. Your licence remains valid for releases in its calendar year; Upgrade Insurance provides entitlement to later calendar years and their monthly Patch + Feature Drops.

Build information

  • Service: 26.11.0.357
  • Configuration Client: 26.11.0.446
  • User Interface: 26.11.0.1020

Read the Technical Release Notes for rsyslog Windows Agent 26.11 for detailed upgrade guidance, product scope, and verification steps.

rsyslog Windows Agent 26.11 Technical Release Notes

Release date: November 3, 2026
Service build: 26.11.0.357
Configuration Client build: 26.11.0.446
User Interface build: 26.11.0.1020

Upgrade assessment

Recommendation: Recommended update

Why update now: This release adds manual hostname mappings. It also verifies TLS and DTLS destinations, rejects malformed Syslog headers, and corrects remote configuration, licensing, and service diagnostics.

If you defer: Existing processing continues, but hostname mappings and the Syslog, TLS, remote-configuration, and diagnostic corrections in this release remain absent.

Who benefits most: Administrators who map hostnames, receive Syslog, or forward over TLS or DTLS.

Upgrade and verification: Update rsyslog Windows Agent using the normal supported upgrade path. Confirm that the installed service version is 26.11.0.357. Test the changed functions that are relevant to your deployment.

Important changes

Hostname and IP mappings

  • Change: General settings can define hostname and IP address mappings in the Configuration Client and in the User Interface.
  • Operational impact: Events can use a configured hostname or IP address mapping instead of the resolved value alone.
  • Applies to: rsyslog Windows Agent installations that resolve hostnames.
  • Verification: Add a hostname and IP address mapping, then confirm a processed event uses the mapped value.

TLS and DTLS forwarding

  • Change: TLS and DTLS forwarding verify destination certificates and identities. Stalled TLS forwarding no longer blocks shutdown indefinitely.
  • Operational impact: A destination with an unexpected certificate or identity is not treated as verified, and a stalled TLS send does not keep the service from shutting down.
  • Applies to: rsyslog Windows Agent installations that forward over TLS or DTLS.
  • Verification: Exercise one TLS or DTLS forwarding destination you use. Confirm the service shuts down after a TLS send that does not complete promptly.

Syslog Listener

  • Change: The Syslog Listener rejects malformed message headers.
  • Operational impact: A malformed Syslog header is rejected instead of being processed as a normal message.
  • Applies to: rsyslog Windows Agent installations that receive Syslog.
  • Verification: In a test environment, confirm a malformed Syslog header is rejected.

Remote configuration, licensing, and diagnostics

  • Change: Remote configuration rejects invalid HTTPS certificates and insecure redirects. Registry configuration detects the default license file more reliably when the license path is empty and no separate data directory is configured. If a different data directory is configured, that directory remains the default license location. When a listening socket cannot be opened, diagnostics include possible owners.
  • Operational impact: Insecure remote configuration downloads are rejected. The default license file is found for the empty-path registry case described above, and a failed listening socket identifies possible owners.
  • Applies to: rsyslog Windows Agent installations that download remote configuration, use registry licensing, or open listening sockets.
  • Verification: Confirm an invalid HTTPS certificate or an insecure redirect is rejected when downloading configuration. With an empty license path and no separate data directory, confirm the service finds the default license file. Confirm a failed listening socket reports possible owners.

Configuration Client

  • General settings can define hostname and IP address mappings.
  • The Syslog action can set the TLS send progress timeout.
  • A partial configuration is not saved after loading fails, and existing settings are preserved when a selective import fails.

User Interface

  • General settings can define hostname and IP address mappings.
  • The Syslog action can set the TLS send progress timeout.
  • A partial configuration is not saved after loading fails, and existing settings are preserved when a selective import fails.
  • The dashboard displays content in the selected language.

Partner deployment notes

Availability: Use the canonical rsyslog Windows Agent download and this Technical Release Notes page as the release reference; do not use temporary build links as the long-term reference.

Localization: The User Interface translation workflow is being prepared. Translation strings and contribution guidance will be published in the Adiscon community repository when available.

Partner verification: Confirm the installed service, Configuration Client, and User Interface builds. Where relevant, compare a hostname mapping with a processed event and save a configuration change.

Related links

rsyslog Windows Agent 26.10: Monthly Patch + Feature Drop

rsyslog Windows Agent 26.10 is the latest monthly Patch + Feature Drop. It updates the included OpenSSL libraries and corrects configuration editing and service diagnostics in the User Interface.

Safer configuration editing

The User Interface validates Workbench edits before saving and restores the previous document if a save fails. Unsaved changes are kept in view when you leave, reload, switch the configuration source, or restart. Rule moves, remote-target protection, configuration-tree navigation, and debug-log follow are corrected, and the empty Advanced page is removed.

Updated OpenSSL

Included OpenSSL libraries are updated to 3.5.9.

The User Interface remains in preview. It is available for production use with appropriate care and review; the Configuration Client remains fully supported.

We recommend keeping rsyslog Windows Agent on the latest Patch + Feature Drop to benefit from current maintenance and product improvements. Your licence remains valid for releases in its calendar year; Upgrade Insurance provides entitlement to later calendar years and their monthly Patch + Feature Drops.

Build information

  • Service: 26.10.0.354
  • Configuration Client: 26.10.0.443
  • User Interface: 26.10.0.1018

Read the Technical Release Notes for rsyslog Windows Agent 26.10 for detailed upgrade guidance, product scope, and verification steps.

rsyslog Windows Agent 26.10 Technical Release Notes

Release date: October 7, 2026
Service build: 26.10.0.354
Configuration Client build: 26.10.0.443
User Interface build: 26.10.0.1018

Upgrade assessment

Recommendation: Recommended update

Why update now: This release updates included OpenSSL libraries to 3.5.9 and corrects configuration editing and service diagnostics in the User Interface.

If you defer: Existing processing continues, but included OpenSSL libraries stay on the previous update, and the configuration-editing and diagnostic corrections in this release remain absent.

Who benefits most: Administrators who use TLS and anyone who edits configuration or follows service diagnostics in the User Interface.

Upgrade and verification: Update rsyslog Windows Agent using the normal supported upgrade path. Confirm that the installed service version is 26.10.0.354. Test the changed functions that are relevant to your deployment.

Important changes

OpenSSL 3.5.9

  • Change: The included OpenSSL libraries are updated to 3.5.9.
  • Operational impact: TLS-using actions and services run with the updated library.
  • Applies to: All rsyslog Windows Agent installations.
  • Verification: After upgrade, confirm the installed service build and exercise one TLS-using function you rely on.

Configuration interface and diagnostics

  • Change: Workbench edits are validated before saving, and the previous document is restored when a save fails. Leaving the page, reloading, switching the configuration source, or restarting asks whether to save or discard unsaved changes. Move rule up moves the selected rule when two rule names differ only by punctuation. Failures from an older remote registry session are ignored, and service commands that would change a remote target are blocked. Empty optional allowed-peer and TLS rows no longer block other edits. Configuration-tree navigation is denser, selection feedback is clearer, and license file path handling is clearer. The empty Advanced page is removed. Debug-log follow stays with appended lines and a replaced log file.
  • Operational impact: Configuration edits are less likely to be lost or applied to the wrong rule, and commands that would change a remote target are blocked.
  • Applies to: rsyslog Windows Agent installations using the User Interface for configuration or service diagnostics.
  • Verification: Save a valid edit and a failing edit, move two rules whose names differ only by punctuation, and follow a debug log while new lines are appended.

User Interface

  • Workbench edits are validated before saving. If a save fails, the previous document is restored.
  • Leaving the page, reloading, switching the configuration source, or restarting asks whether to save or discard unsaved changes.
  • Move rule up moves the selected rule when two rule names differ only by punctuation.
  • Failures from an older remote registry session are ignored, and service commands that would change a remote target are blocked.
  • Empty optional allowed-peer and TLS rows no longer block other edits to the selected service.
  • Configuration-tree navigation is denser, selection feedback is clearer, and license file path handling is clearer.
  • The empty Advanced page is removed.
  • Debug-log follow stays in view when lines are appended or the log file is replaced.

Partner deployment notes

Availability: Use the canonical rsyslog Windows Agent download and this Technical Release Notes page as the release reference; do not use temporary build links as the long-term reference.

Localization: The User Interface translation workflow is being prepared. Translation strings and contribution guidance will be published in the Adiscon community repository when available.

Partner verification: Confirm the installed service, Configuration Client, and User Interface builds. Save a configuration change in the User Interface and, where relevant, exercise one TLS-using function.

Related links

rsyslog Windows Agent 26.09: Monthly Patch + Feature Drop

rsyslog Windows Agent 26.09 is the latest monthly Patch + Feature Drop. It focuses on dependable service operation and smoother configuration administration.

More dependable service operation

The service now keeps a stop request effective even when it overlaps a configuration reload. Services installed with a custom Windows service name also start more reliably.

Smoother configuration administration

The User Interface preserves unsaved configuration changes when you restart as administrator, so you can review and save your work after elevation. After local metrics setup, standard users can reload their configuration without needing to restart as administrator. This release also includes stability maintenance for timestamp and configuration handling.

The User Interface remains in preview. It is available for production use with appropriate care and review; the Configuration Client remains fully supported.

We recommend keeping rsyslog Windows Agent on the latest Patch + Feature Drop to benefit from current maintenance and product improvements. Your licence remains valid for releases in its calendar year; Upgrade Insurance provides entitlement to later calendar years and their monthly Patch + Feature Drops.

Read the Technical Release Notes for rsyslog Windows Agent 26.09 for detailed upgrade guidance, product scope, and verification steps.

rsyslog Windows Agent 26.09 Technical Release Notes

Release date: September 1, 2026
Service build: 26.9.0.353
Configuration Client build: 26.9.0.442
User Interface build: 26.9.0.1017

Upgrade assessment

Recommendation: Recommended update

Why update now: This release corrects service-stop handling during configuration reload, startup of custom-named Windows services, and a timestamp-conversion crash. It also improves administration through the User Interface metrics dashboard.

If you defer: Installations retain the service-operation and timestamp-conversion limitations addressed by this release, as well as the earlier User Interface administration behaviour.

Who benefits most: Administrators who reload configuration, use custom Windows service names, or use the User Interface metrics dashboard.

Upgrade and verification: Update using the normal supported path. Confirm service build 26.9.0.353, reload configuration in a controlled maintenance window, verify a custom service name where used, and reload the User Interface dashboard after Metrics Helper setup.

Important changes

Service operation and reliability

  • Change: Stop requests are retained during configuration reload, and services with custom Windows service names start reliably.
  • Operational impact: Reduces avoidable disruption during service administration and maintenance.
  • Applies to: rsyslog Windows Agent installations that reload configuration or use custom service names.
  • Verification: Reload configuration and, where applicable, stop/start the custom-named service during a controlled maintenance window.

Timestamp conversion reliability

  • Change: A crash while converting certain read-only timestamp properties is corrected.
  • Operational impact: Improves reliability for configurations that process these timestamp properties.
  • Applies to: rsyslog Windows Agent configurations using the affected timestamp conversion path.
  • Verification: Process a representative test message that uses the relevant timestamp property.

Configuration Client and User Interface

  • After local Metrics Helper setup, standard users can reload the User Interface metrics dashboard.
  • Service-owned older General settings no longer produce unnecessary unknown-configuration indications.

Published errata and known issues

Installer-update reliability: ERR-2026-002: rsyslog Windows Agent update reports success but program files are not upgraded correctly is resolved in the 26.09 setup release. After a direct upgrade from an earlier product generation, confirm that the installed service reports 26.9.0.353 and that the Configuration Client and the required features are present.

Related links

rsyslog Windows Agent 26.08: Monthly Patch + Feature Drop

rsyslog Windows Agent 26.08 is available now. This monthly Patch + Feature Drop gives Windows log-forwarding teams a clearer view of selected messages, more flexible file monitoring in supported editions, and maintenance improvements for dependable event collection and forwarding.

Faster insight into selected messages

Operators can now view a selected set of stored log and event messages directly in the User Interface. This makes it easier to check what is being processed without leaving the product workflow.

More flexible collection and forwarding

In supported editions, file monitoring can now match files across nested paths with multiple wildcard components, helping teams cover dynamic directory structures with less configuration overhead. 26.08 also improves Event Log monitoring reliability during shutdown and recovery conditions.

Plan your update

The User Interface remains in preview and can be used in production with appropriate care and validation for the individual environment. The Configuration Client remains fully supported.

We recommend keeping rsyslog Windows Agent on the latest Patch + Feature Drop to benefit from current maintenance and product improvements. Consult the rsyslog Windows Agent documentation, then download rsyslog Windows Agent.

Rsyslog Windows Agent 8.4 Released

A new version of the rsyslog Windows Agent is now available. Version 8.4.0 brings native configuration import/export options, improved service stability, and multiple client bug fixes.

Core Service Engine Updates

In the core engine, a critical concurrency fix has been applied to both the Syslog and RELP forwarding actions. The update resolves shared disk-queue rewrite race conditions that previously occurred when multiple forwarding actions were configured to use the same queue directory simultaneously, ensuring greater data integrity during high-load forwarding scenarios.

Configuration Client Enhancements

Native YAML Support

The Configuration Client now natively supports importing and exporting YAML configuration files. This functionality is fully aligned with the service runtime loader, streamlining configuration backups and migrations across environments.

Reliability & Configuration Handling

Registry-based configuration loading has been hardened to handle fresh installations and incomplete registry data smoothly. Additionally, when encountering unknown configuration blocks—such as those introduced by newer service versions—the client now gracefully skips them with a clear warning rather than failing to load.

Service Management & Stability

Service control logic has been overhauled to handle edge cases such as orphan processes, access control issues, and transitional service states. Administrators now have access to optional process termination options and a direct shortcut to Windows Services.

Timeout messaging during start and stop operations has been clarified for cases where the client stops waiting before Windows completes the service transition. The status bar now explicitly tracks states like Stopping, Starting, and Paused (Reloading), and false stop-timeout errors—where the service had already reached a stopped state—have been eliminated.

Additionally, the Event Viewer now prepends new events following start, stop, restart, or reload actions rather than clearing the existing list, while background threading has been improved to recover cleanly from aborted operations. A client crash on shutdown involving open Event Viewer or Service Management panels has also been resolved.

Released versions

  • Service: 8.4.0.239
  • Client: 8.4.0.334

Download rsyslog Windows Agent 8.4.0

Scroll to top