Missing Unicode Star after update to 2018 October

Looks like an issue with 1809. You should drop a feedback to Microsoft engineers - You can give through Feedback Hub - Press Windows Key+F to open Feedback Hub and provide feedback.

These get read by Microsoft and prioritized by them for future development.

Looks like an issue with 1809. You should drop a feedback to Microsoft engineers - You can give through Feedback Hub - Press Windows Key+F to open Feedback Hub and provide feedback.

These get read by Microsoft and prioritized by them for future development.

Will do, thanks. Just wanted to make sure it wasn't isolated to my environment before submitting. And I can't update my other devices now because I use an application that heavily relies on the Unicode set.

This is just like when 1803 was first released and it broke full-screen Chromium :/

Hi

Same problem here. After 1809 update, my foobar2000 (audio player) shows squares signs instead of musical notes (U+266A). When copied in foobar2000 conf window, it's replaced by a square sign (and a bunch of other characters behave the same, probably all symbols).

Feedback Hub Link Here: https://aka.ms/AA2qjhv

Same problem here :( In my case " ♔ " character doesn't display.

I had to clean reinstall windows 7, upgrade to 8, 10 then to find out they messed up on the 2018 fall release, and it's not me somehow messed up something.

Additional information I found is that, let say if you have a folder with the star symbol (which I uses with Japanese mostly), you see this

But, if you do a search, it shows up properly

Btw, within browser it's fine, like this

One thing you can notice is that the font style seems to be different, by looking at the Japanese characters.

Microsoft must fix that immediately.

I had to go back to 1803 and close the updates.

And i am not the only one who downgrade for this reason!

Same here. It happens also for black star and other glyphs.
Very wierd issue, MS please solve this.

After trying for a few days (and wasted a whole of time), I had to do what others did in the above comments and had to clean install into 1803, starting all over again.

In addition to this, I found out it's very, very, VERY difficult to block the update pushes from Microsoft (which wasted another few hours trying to find solution).

I am super pissed at Microsoft right now because they have pushed out faulty software, and forces you to use their faulty software regardless of your intention.  It's only a matter of time when their method affects major businesses.