We've run into this issue before, and it seems to have something to do with the font's Unicode values being "out of range" on Windows, whatever that means.
FWIW, I've worked on projects where we "blacklist" embedded fonts on certain combinations of OS+Browser -- particularly chrome on older versions of windows.
Based on the user string, we would serve up a version of the HTML that didn't request the embedded font, and then those users would see Arial instead of, for example, Proxima Nova.
Super-annoying to have to deal with. But it works.
We've run into this issue before, and it seems to have something to do with the font's Unicode values being "out of range" on Windows, whatever that means.