Cannot use any font besides Consolas

[derekslenk]

Windows Terminal version

1.15.2713.0

Windows build number

10.0.22621.0

Other Software

oh-my-posh

Steps to reproduce

Install oh-my-posh with any of the available ways.
Install a Nerd Font in any available way.
Select the nerd font as your default font in terminal and it won't work.

Expected Behavior

Be able to use a different font that I install besides Consolas

Actual Behavior

Unable to find the selected font "ANYTHING NF".

"Consolas" has been selected instead.

Please either install the missing font or choose another one

[derekslenk]

This worked until the 22H2 update

[j4james]

I suspect this might be the same issue as #3257.

[ohroy]

tried many nerd fonts...same

[FDUZS]

Same here. It seems to be system-wide, not just windows terminal. And, only nerd fonts are affected?

matthewjberger/scoop-nerd-fonts#198

[lhecker]

If I'm guessing right (and if j4james is right) this is the old font caching bug.

That one affects anyone who tries to install via any of the regular install methods. In other words, all of those:



...don't work correctly in any recent Windows version and you can't use them without encountering this bug. This includes versions before 22H2 btw, see #12587 for instance.

Instead what you have to do is:

• clean your %LOCALAPPDATA%\Microsoft\Windows\Fonts directory of your previously installed, broken fonts
• hold Shift and Right-Click the font file and click this:
  

I don't know in what Windows version this bug will be fixed but I'm personally hoping for it to be resolved next year.

[FDUZS]

Same here. It seems to be system-wide, not just windows terminal. And, only nerd fonts are affected?

matthewjberger/scoop-nerd-fonts#198

the workaround offered by Dabombber in the issue above is to restart the font cache service via Restart-Service -Name FontCache, which does temporarily solve the problem. I guess I have to run it after every reboot, though.

[carlos-zamora]

Marking this as /dup #3257

[ghost]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!