Microsoft didn’t give any technical specifics as we didn’t really get that far.
I can copy these characters from Character Map and paste them into Notepad and they print without error which tends to point the blame at Crystal Reports, however this technique of using Box Drawing characters in Crystal Reports formulas has been working for at least 14 years on every windows version going back to Win 95.
In my case I’m actually using the standard Arial font that comes on every windows computer, I just happen to be using character codes that are in the Unicode Box Drawing Range. I don’t know for sure but I suspect that the problem in KB3078601 is more related to the exact character codes being used than the font file itself. After all, I can use Arial all day as long as I don’t start with ChrW(9566) (hex value 255E) or similar Box Drawing character. As I stated before, If I start the Box Drawing sequence with a smaller valued character like ChrW(160) (hex value 00A0) then everything works fine. I know I’m not giving you anything new but this all I know.
