Unable to find the selected font CaskaydiaCove NF

[va-it]

N.B. I have looked at the other font related issues (e.g. #11648), but I believe mine is slightly different. In my case, the Cascadia Mono font is found without problems.

This issue is occurring in both Terminal and Terminal Preview. I have the CaskaydiaCove NF font installed and I am able to use it on other apps such as WordPad. However, upon starting the Terminal, I receive the "Unable to find the selected font" error.

The problem is temporarily resolved by simply opening the settings and saving, even without changing anything. But then the error is presented once more when the program is closed and opened again.

Windows Terminal Version: 1.12.10393.0
Windows Terminal Preview Version: 1.13.10395.0

[zadjii-msft]

Hmm. This sounds like #9360, but that was duped to #9375 which was supposed to be fixed like, months ago.

Maybe this is a variant of the thing in PR at #12554? (Mind confirming for me @lhecker?)

[lhecker]

Maybe this is a variant of the thing in PR at #12554? (Mind confirming for me @lhecker?)

Hmm... no, on Windows 11 this should've worked. The experimental text rendering engine doesn't support proper font fallback, which is why this can't be it either (WT crashes instead of presenting a Warning popup).
This is probably an unrelated issue.

[lhecker]

Here's what I did:

• Visit https://www.nerdfonts.com/font-downloads
• Download "Cascadia Code" aka "CaskaydiaCove"
• Install Caskaydia Cove Nerd Font Complete Mono Windows Compatible.ttf
• Set font.face to "CaskaydiaCove NF"

The result: It works!

Unfortunately this means that I can't reproduce your issue in neither 1.12 nor 1.13.

[va-it]

Here's what I did:

• Visit https://www.nerdfonts.com/font-downloads
• Download "Cascadia Code" aka "CaskaydiaCove"
• Install Caskaydia Cove Nerd Font Complete Mono Windows Compatible.ttf
• Set font.face to "CaskaydiaCove NF"

The result: It works!

Unfortunately this means that I can't reproduce your issue in neither 1.12 nor 1.13.

Thanks a lot for looking into this guys. I am not sure why I was having that issue, but I have followed the steps described and now I cannot replicate it either.

Sorry for wasting your time, but the issue is now resolved so thanks a lot again 🙏.

[va-it]

Sorry for reopening this, but the issue is back... After restarting the computer the error message appears again.

Maybe there is a problem in Windows and the way fonts are installed? If I search for the font in settings I don't see CaskaydiaCove NF (I believe I could see it yesterday after following @lhecker suggestions).

But I can see it (and use it) in WordPad for example

[lhecker]

@va-it Can you check the old legacy Fonts control panel? You can find it in the start menu by typing "Fonts".
If it's there I'd suggest removing the font and adding it back in.

[va-it]

@va-it Can you check the old legacy Fonts control panel? You can find it in the start menu by typing "Fonts". If it's there I'd suggest removing the font and adding it back in.

Ok, so I deleted the font via the Control Panel and installed it again. Predictably, I could see the font in various apps and the new Settings, and I was able to use it in Terminal.
Then I have restarted the computer, and again the font is not visible in Settings and cannot be used in Terminal.
When I try to install it again (without removing it first from Control Panel) I am told that it's already installed.

I believe something is wrong with Windows 11...

[lhecker]

@va-it Is your "Windows Font Cache Service" running? Which .ttf file from the nerd fonts collection are you using specifically?

[va-it]

The service is running and the .ttf is the one you suggested yesterday: Caskaydia Cove Nerd Font Complete Mono Windows Compatible.ttf

[lhecker]

I can find various internal feedback that fonts are lost after a restart. One particular issue seems to occur if you install fonts via drag and drop in the settings app.

Did you try installing these fonts using this?

If it works correctly, fonts should end up in C:\Users\<username>\AppData\Local\Microsoft\Windows\Fonts.
If they aren't there, something is wrong...

[zadjii-msft]

something makes me think this is like #3257