The only obvious difference between your environment and one of mine was the Windows 10 version (I upgraded from Windows 7 a couple of days ago and the update cycle had only got to 1803 by yesterday evening, whilst 1903 was installed last night) and since the 1903 update I see the same output but only in some contexts?!
When run in TCC running under Take Command (with Unicode output off) I see the output unsullied (although I do see a strange artefact on the right hand end of the output line - three white squares, where my background colour is black). Running in a standalone TCC (with Unicode off and Raster font) I see a question mark whereas with (say) Consolas I see the right facing arrow but with some other fonts I see an empty square or a small dot (presumably representing the fact that there isn't a character in that position in the font). Both Powershell and CMD show the same, depending on font.
Yes. I also discovered what it was (and neglected to push "Post reply"). And, as you said, Steve, it depends on the font. Other fonts give a more typical representation of an "unprintable" character. The programmer can choose a default character when converting Unicode to Ascii (which may be happening). That one is an odd choice. And what's an extra character doing there in the first place?