[BUG] [LOGMONITOR] WARNING: Failed to render event log event. The event will not be processed. Error: 15033.

Describe the bug
Getting the following errors when running LogMonitor in a container

[2023-08-07T14:33:10.000Z][LOGMONITOR] WARNING: Failed to render event log event. The event will not be processed. Error: 122.
[2023-08-07T14:33:10.000Z][LOGMONITOR] WARNING: Failed to render event log event. The event will not be processed. Error: 15033.
[2023-08-07T14:33:10.000Z][LOGMONITOR] WARNING: Failed to render event log event. The event will not be processed. Error: 15033.
[2023-08-07T14:33:10.000Z][LOGMONITOR] WARNING: Failed to render event log event. The event will not be processed. Error: 15033.
[2023-08-07T14:33:10.000Z][LOGMONITOR] WARNING: Failed to render event log event. The event will not be processed. Error: 15033.
[2023-08-07T14:33:10.000Z][LOGMONITOR] WARNING: Failed to render event log event. The event will not be processed. Error: 15033.
[2023-08-07T14:33:10.000Z][LOGMONITOR] WARNING: Failed to render event log event. The event will not be processed. Error: 15033.

To Reproduce
Steps to reproduce the behavior:
Build image using mcr.microsoft.com/dotnet/framework/runtime:4.8 base image
Set ENTRYPOINT C:\LogMonitor\LogMonitor.exe ...
Launch container
Observe STDOUT for LOGMONITOR exceptions

Expected behavior
Log Event Log channels events without warnings/failures

Configuration
Container image mcr.microsoft.com/dotnet/framework/runtime:4.8
Running latest Docker Desktop on Windows 10 22H2
LogMonitor v2.0 with example .json config from this repo

Reproduce the warnings by running LogMonitor.exe in a container based on mcr.microsoft.com/dotnet/framework/runtime:4.8 with the example JSON configuration from this repository. Start by inspecting the LogMonitor event-log rendering path and the reported errors 122 and 15033. Done means event-log events are written to STDOUT without rendering warnings or failures.