Thanks @miran, It may have been introduced in one of the mid 0.18.0 versions, because I tried it again on a friends **Windows 10 x64, Nim 0.18.1 x64** machine and the error is present.
@miran, could you perhaps try it with a newer version of Nim? Thanks
