I rarely use a Windows computer. but I do have one for a client. Even so, take what I'm saying with a grain of salt.
It is my understanding that Windows powershell (and Windows as a whole) defaults to UTF-16 (<https://en.wikipedia.org/wiki/UTF-16>) which would not "auto-translate" very well from UTF-8. IIRC, UTF-16 is very similar to the old "code pages" model that Windows once used, so they like to use it behind-the-scenes where they can. You could try adding pre-pending a BOM (byte-order-mark) at the start of the string. Not sure how that would play out in practice. There is also a library: [encode](https://github.com/treeform/encode) that would, in theory, let you convert from the near-universal UTF-8 to UTF-16. If that library works (or if it doesn't), you might want to post the results to the forum for the other Windows users to see.
