May contain traces of nut
That's a work-around, not joined-up thinking.
Until the program defect is corrected that causes it, users could run a Unix-to-DOS utility on the file before opening it. The discussion HERE (click) offers a variety of options, I would probably code something in AWK*.
* AWK is designed for text processing. I can't remember the syntax off the top of my head, but an AWK program to do this would go something like:
Set input record delimiter = "LF"
Set output record delimiter = "CR LF"
Copy input records to output until end of file
The AWK call can then be wrapped in a .BAT to hide the details away, which (if suitably tweaked) can even be drag-and-drop (I have done this with another conversion I do regularly). So, in Explorer, with "output.log" and "unix2dos.bat" files in the folder, you would just drag output.log onto unix2dos.bat and bingo, output.log.txt would appear and be openable in normal Windows utilities.
Is it worth me doing this? Probably not, anyone wanting to use it would need not only the unix2dos.bat file and the .awk program but the gawk.exe AWK interpreter as well. A compiled unix2dos.exe would be much better (and is almost certainly out there somewhere).