Font loading faults after Windows update KB5039212 about terminal

[lhecker]

So, the font was showing in the old control panel, but not in Windows->Settings->Personalisation->Fonts.

I have encountered broken font caches before, but definitely not like that. Hopefully this isn't a common bug.

The font is now loaded at the start up of Terminal, as expected.

I'm glad to hear that this fixed the problem! I'll close this issue for now and hope that this is just a rare bug in Windows. This is because...

I guess there are multiple ways of enumerating the fonts, and something got damaged during the update? This would make sense if the start-up process was checking in a different way to the Terminal->Settings tab.

...your assumption is sort of correct. We have a number of problems with the font caching service on Windows and we're tracking the worst one in issue #3257: Per-user fonts simply don't work. That's internally tracked as MSFT:42103854. Font support is definitely more robust for unpackaged applications unfortunately.

[lhecker]

Note: This is not the same as #9375 , and the fix for that issue does not apply

For my understanding: You did install the font for all users and, if you previously installed for your user only, you made sure to remove it from AppData again, right?

[i-e-b]

Hi.

Yes, the font is installed for all users. It is not installed in AppData, only in C:\Windows\Fonts.

I have also tried multiple reboots, and have run "Repair" for the Terminal app in Settings.

[lhecker]

Did you already try to remove the font and reinstall it? If not, I'd check both the old control panel

as well as the new one

If you already tried this, please let me know. 🙂

[i-e-b]

Hi.

So, the font was showing in the old control panel, but not in Windows->Settings->Personalisation->Fonts.
I deleted via the old control panel, and re-installed via settings.

The font is now loaded at the start up of Terminal, as expected.

I guess there are multiple ways of enumerating the fonts, and something got damaged during the update? This would make sense if the start-up process was checking in a different way to the Terminal->Settings tab.

[i-e-b]

This fault has re-occurred

Looks like it might be a bug in Windows -- I have made no font changes, but my chosen font was lost from the 'new style' Windows Settings, but was present in the 'old style' Fonts.

Re-installing in the Settings app triggered the 'This font is already installed' warning from the old side, but then the Console issue stopped.