Steps to reproduce:

At monitored Windows host create Zabbix (active) item with type information log:
log["C:\ERRORLOG2",,UTF-16]

part of ERRORLOG2 file is included.

It is a log form MSSQL and problematic is the empty line between 2024-11-13 23:03:30.75 and 2024-11-13 23:03:30.77 which is correctly handled by linux agents but not agents on windows.

file -b ERRORLOG2
Unicode text, UTF-16, little-endian text, with very long lines (517), with CRLF line terminators

Result:
After parsing first three log lines, I get Unsupported item state with message:

Failed to convert from encoding UTF-16 to utf8. Error: [0x00000057] The parameter is incorrect..

Expected:
Supported item.