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.