BUG: mk_logwatch ab 2.1.0p10 auf Windows komplett funktionsunfähig

In any case, logwatch looks for \n, i.e. 0x0A, aka Line Feed in text. No \n(0x0A) - no processing.
This behavior is correct and logical and rather will be not changed in the future.

Windows specific \r, i.e. 0xD, aka Carriage Return is ignored.