I just ran some updates and have the exact same problem. It's clearly a Windows bug. Not a big one, but clearly a bug.
Just a note, for other users - most of the Microsoft "experts" here are utterly useless and don't even read your question past a quick skim. Scott_LA, I suggest reading peoples questions and looking at their screenshots before pulling answers out of thin air. This clearly wasn't a language pack issue and anyone who has worked with Windows over the years would know that. All the other numbers are fine - but you think dropping into Kanji for one field means the user has the wrong language pack? Hokay. Then again, you un-ironically used the word "quarry" in an internet post response, so you're suspect from the get-go. (Surprised you didn't pull out the ol' DISM and sfc /scannow.) You're a moderator on here? Yikes.
Considering this is a mix of special characters, it seems to be an overflow issue, probably a bug where units weren't converted right, and something's landing randomly on the upper unicode characters for whatever current language you have selected.
Hands down a rather benign Windows bug, but a bug nonetheless.
(Am I little irked? Yes. This resource has become increasingly useless over the years. Get better.)