Instead of looking for the event log in archives.log, could you search for it in archives.json? It should be in the same folder and will provide cleaner logs (hopefully without \n and < characters ) for Windows Event Channel.
In newer versions of Wazuh, like the one you are using, Windows Event channel events do not need a decoder, they are automatically decoded in a json-like format. Ideally you would write a simple base rule that would act as a "decoder" and then extend with specific rules.
Testing windows event log rules using wazuh-logtest is a bit tricky, as you will need to make a temporary change to rule 60000 in /var/ossec/ruleset/rules/0575-win-base_rules.xml:
<rule id="60000" level="0">
<!--category>ossec</category-->
<!--decoded_as>windows_eventchannel</decoded_as-->
<decoded_as>json</decoded_as>
<field name="win.system.providerName">\.+</field>
<options>no_full_log</options>
<description>Group of windows rules</description>
</rule>
You child rule would be something like
AD FS Auditing
<rule id="100001" level="0">
<if_sid>60000</if_sid>
<field name="win.system.providerName">AD FS Auditing</field>
<options>no_full_log</options>
<description>Group of AD FS classic security log rules</description>
</rule>
If you can get the log in json format I can provide better guidance on this.
Regards,