Creation of new Rich Text Format files creates wrong files. How to fix it?

Hi to everyone. I am new to this forum, but I was a user of the Directory Opus since its version 10. I love this program and wish I could use it as the only file-explorer, if not one extremely annoying issue with it. When I create a new RTF (Rich Text Format) file using a standard "New..." Windows dialog, the resulting RTF file can not be opened as such in WordPad, nor in Word. Such an RTF file opens in a manner if you are opening an RTF file in Notepad - even the WordPad shows its contents as "{\rtf1}" in plain text - exactly as if it were an attempt to open a new empty RTF file in the Notepad. Word behaves similarly, except that instead of "{\rtf1}" contents, it shows some unreadable characters. If one wants to recreate the problem - open an empty RTF file in Notepad and imagine that WordPad shows the same thing as the Notepad does. If to compare the "proper" RTF file and the "wrong" RTF files both opened in Notepad++, the difference will be that the "proper" file's contents will be "{\rtf1}" only, while the "wrong" RTF files contents will be "{\rtf1}NUL", where "NUL" is some special invisible character visible in Notepad++, but invisible in Notepad and WordPad. File extension (.rtf) is proper and the file association (with WordPad or with Word) is proper too. The new RTF files created in a Windows Explorer window are proper, but those created in a Directory Opus window are not - they are not usable after creation and I can not figure out why this behavior occurs and what to do to fix it. I will appreciate any advice. Thank you so much in advance.

Which version are you using? I'm fairly sure that's something we fixed a few months ago, and it works OK in 13.4 here.

Hi Leo. Thanks for your reply. I tested it in a version 10 (which I purchased a long time ago, but could not use merely because of this problem, because I use a lot of RTF files), also tested it in trial versions 10, 11 and 12. And it was all the same (hence I did not purchase any newer version, as I can not use it anyway). But when it comes to the version 13.4, I did not test it yet. I will try. Thanks.

P.S. yes, I indeed tested it with the latest version 13.4. This problem is no more - a new RTF file is being created in a proper way. Thanks. I should buy a new version now, at last.