Unable to find the selected font CaskaydiaCove NF #12587

va-it · 2022-02-26T16:14:43Z

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 · 2022-02-28T12:14:09Z

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 · 2022-02-28T19:17:38Z

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 · 2022-02-28T20:44:46Z

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 · 2022-02-28T20:59:59Z

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 · 2022-03-01T17:40:26Z

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 · 2022-03-01T17:43:45Z

@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 · 2022-03-01T17:54:55Z

@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 · 2022-03-01T18:04:18Z

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

va-it · 2022-03-01T18:08:52Z

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

lhecker · 2022-03-01T18:24:54Z

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 · 2022-03-01T18:49:29Z

something makes me think this is like #3257

va-it · 2022-03-01T19:11:13Z

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...

@lhecker Yes, I have always installed the font using the Install button. The font is in the AppData folder even after restarting the computer, but the error is still there.

Thanks @zadjii-msft. I have read the comments in that thread and I have now installed the font using the "Install for all users" options. After restarting the computer, I don't have the problem anymore.

I thought it worth mentioning that the "Install for all users" option is not available in the new style right-click menu, so this is a very obscure workaround.

But it solved the problem, so many thanks again to both of you for your time 🙂.

lhecker · 2022-03-01T23:20:15Z

@va-it I'll try to escalate one of the internal issues we have (or create one if needed) based one the information you've given us.
In the meantime I'll close this issue and if anything comes up I'll report back here. 🙂

AkariiinMKII · 2022-09-26T00:34:28Z

I've suffered this issue since updated to Windows 11, I believe that's the problem of system. Fortunately restarting font cache service solves this on my machine till next boot up.

Yastruhank · 2022-10-09T10:59:33Z

I've suffered this issue since updated to Windows 11,

I've suffered this issue since I updated my Windows 11 to 22H2 too. I guess this is the problem of update with Windows 11.

teeroddesigns · 2022-10-18T16:49:14Z

I have the same issue. Restarting the Windows Font Cache Service also works for me.

fredizzimo · 2022-12-17T20:36:07Z

For me it also started after the Window 11 22H2 update. It seems like it looses all user installed fonts.

The old control panel still shows the fonts, but they are missing from the new set settings Personalization/Fonts and Windows programs.

Like above, restarting the Windows Font Cache Service, seems to make it work again.

alecthegeek · 2022-12-20T03:53:15Z

I now have this problem, and restarting the Font Cache Service did not fix it :-(.

Happy to run any diagnostics people suggest, meanwhile I will keep pooking it

GlennWo · 2022-12-24T13:51:37Z

I was having this problem as well on Windows 11. I tried lots of things which stopped working after reboot. I finally found this solution which worked for me.

https://answers.microsoft.com/en-us/windows/forum/all/solution-installed-fonts-disappearing-after/146f4039-47c3-4017-a9b1-76f72badce39

Press Windows Key + R to open the Run dialog
Paste %LOCALAPPDATA%\Microsoft\Windows\Fonts and press Enter
You should see all your installed fonts, press Ctrl + A to select all the font files
While all the files are selected, right click any one of the files and press "Install for all users", not "Install" (with the shield icon, requires administrator privileges)

johanvanmol · 2023-01-12T12:31:01Z

Thank you @GlennWo . This worked for me. Like a lot of other commenters, I was restarting the FontCacheService at least daily. I even created a small batch script for this. Your solutions is way better: a one time fix that takes care of this problem.

ChromaticRanger · 2023-04-07T18:37:09Z

I was having this problem as well on Windows 11. I tried lots of things which stopped working after reboot. I finally found this solution which worked for me.

https://answers.microsoft.com/en-us/windows/forum/all/solution-installed-fonts-disappearing-after/146f4039-47c3-4017-a9b1-76f72badce39

Press Windows Key + R to open the Run dialog

Paste %appdata%..\Local\Microsoft\Windows\Fonts and press Enter

You should see all your installed fonts, press Ctrl + A to select all the font files

While all the files are selected, right click any one of the files and press "Install for all users", not "Install" (with the shield icon, requires administrator privileges)

A small addition. If you try this and get confused that you are not seeing "Install for all users". You need to be holding down the Shift key when right clicking on the selected files. You will then see that option in the displayed menu.

MrKomputerKid · 2023-09-05T02:24:39Z

I was having this problem as well on Windows 11. I tried lots of things which stopped working after reboot. I finally found this solution which worked for me.

https://answers.microsoft.com/en-us/windows/forum/all/solution-installed-fonts-disappearing-after/146f4039-47c3-4017-a9b1-76f72badce39
1. Press Windows Key + R to open the Run dialog

2. Paste %appdata%..\Local\Microsoft\Windows\Fonts and press Enter

3. You should see all your installed fonts, press Ctrl + A to select all the font files

4. While all the files are selected, right click any one of the files and press "Install for all users", not "Install" (with the shield icon, requires administrator privileges)

Amazing! Thank you! This worked for me on my PC at home! Once again thank you!

4N7 · 2023-09-13T19:27:19Z

The replies in this issue contain a malformed path.
Here's the instructions with the correct path and pretty formatting 🙂:

Press ⊞ Win + R to open the Run dialog
Paste %appdata%\..\Local\Microsoft\Windows\Fonts and press Enter
You should see all your installed fonts in file explorer. Select the desired font(s) (press Ctrl + A to select all).
With the desired fonts selected, right-click one of the files and click "Install for all users" (NOT "Install") next to the shield icon (requires administrator privileges). If you do not see "Install for all users", hold down Shift before right-clicking.

Hoernchen · 2023-11-16T02:07:05Z

This is still a problem, btw. Maybe adding a hint to the error popup would help?

DHowett · 2023-11-16T03:17:39Z

This is still a problem, btw. Maybe adding a hint to the error popup would help?

Which version of Terminal are you on? We just published an update that should fix this.

Hoernchen · 2023-11-16T09:09:06Z

The current store version, 1.18.2822.0 - it is too late to try the preview, because I manually fixed it as described in #12587 (comment)

anatilopan · 2023-12-05T08:23:37Z

Which version of Terminal are you on? We just published an update that should fix this.

Hello, I have the same issue (and some of my friends too). After testing a theory.. I found out that only the versions installed via Microsoft Store have this issue.
I tried the preview (v. 1.19.231113002-preview) version installed from ms. store and the same issue appeared;
Tired the preview version manually downloaded and put under program files directory (to be in the same zone as the ms. store one) and I could not reproduce the issue.
Same for the current stable version (v. 1.18.3181.0)

So I have new theories but i cannot confirm them right now as i do not own a Windows machine myself. (the one I've tested the theory is from work and i cannot make the necessary changes on it)

Somewhere the way that store apps are run/installed does not have the proper permissions to check user's installed fonts.
There is some GPO/administrative setting in my company that restricts store apps to have access to the fonts.

There could be other things but frankly, i'm not a windows user and do not know a lot about it.. and i do not have a lot of time for testing those issues right now even if i'm an administrator on this machine, sorry for that.

Hope it helps somewhat... Have a nice day! ^^

Gonkers · 2023-12-06T09:05:55Z

This is still a problem, btw. Maybe adding a hint to the error popup would help?

Which version of Terminal are you on? We just published an update that should fix this.

I just decided to try Oh-My-Posh and I ran into this issue today. ~~I had to install the fonts into c:\windows\fonts in order to get this working.~~ I have installed Windows Terminal via winget
Windows Terminal Preview
Version: 1.19.3172.0

Windows 11 23H2

Edit: Never mind, I'm back at square one, I thought I had it working, but Terminal cannot find the fonts. Visual Studio 2022 sees them and uses them just fine.

NewtonChutney · 2023-12-28T04:47:28Z

I have recently been seeing more of this issue:

Unable to find the selected font "FiraCode Nerd Font Mono".

"Consolas" has been selected instead.

Please either install the missing font or choose another one.

WT version: Windows Terminal - Version: 1.18.3181.0
winver - Microsoft Windows [Version 10.0.22631.2861]

Looks like whatever fix was pushed didn't completely solve the issue..

I installed the fonts by dragging and dropping into the fonts section in both control panel and Settings UWP. I see that the fonts are installed in `%LOCALAPPDATA%\Microsoft\Windows\Fonts`. They are still visible in control panel after a restart, but not in Settings UWP.

Settings UWP:

%LOCALAPPDATA%\Microsoft\Windows\Fonts:

Control panel

lhecker · 2024-01-08T15:18:58Z

Looks like whatever fix was pushed didn't completely solve the issue..

Just to be clear, this was never fixed by us. It's a bug in Windows font handling code and affects any store application. Follow these steps instead: #12587 (comment)
To add, you should also make sure to delete all fonts from %LOCALAPPDATA%\Microsoft\Windows\Fonts if you can, since those don't work consistently correct anyways.

NewtonChutney · 2024-01-08T16:12:13Z

Just to be clear, this was never fixed by us. It's a bug in Windows font handling code and affects any store application. Follow these steps instead: #12587 (comment)
To add, you should also make sure to delete all fonts from %LOCALAPPDATA%\Microsoft\Windows\Fonts if you can, since those don't work consistently correct anyways.

Yep, I had installed for all users and removed those in my (user's) localappdata..
But, this wouldn't be a solution for the enterprise lot.. They wouldn't have admin privileges..

Now I think of it.. I don't remember seeing the font not found prompts on my non-admin enterprise user account.. 🤔
I'll check and comment again

dlplenin · 2024-08-08T18:39:18Z

I had the same issue (with a different font) after installing Docker on Windows 11.

The solution was to reset the app:

I hope this helps someone in a similar situation.

UPDATE:
This works after restarting the terminal, but after restarting the PC the error is still there.
Since my problem was with ohmyposh, I installed the font for all users by running the terminal as Administrator, which fixed the problem:

DonutWrecker · 2024-08-10T22:34:26Z

#14231 (comment)

The solution in the link solved my issue.

ignatirabo · 2024-11-04T10:20:45Z

#12587 (comment)

Comment above fixed the issue. Problem is still present with Terminal 1.21.2911.0

ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Feb 26, 2022

va-it closed this as completed Feb 28, 2022

va-it reopened this Mar 1, 2022

lhecker closed this as completed Mar 1, 2022

zadjii-msft mentioned this issue Mar 7, 2022

warning font not found #11583

Closed

zadjii-msft mentioned this issue May 3, 2022

Can not Set installed Font for Terminal Profile #13021

Closed

lhecker mentioned this issue Oct 17, 2022

Cannot use any font besides Consolas #14231

Closed

fredizzimo mentioned this issue Dec 17, 2022

'fontFace' not working for any profile after system reboot. #3257

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Unable to find the selected font CaskaydiaCove NF #12587

Unable to find the selected font CaskaydiaCove NF #12587

va-it commented Feb 26, 2022 •

edited

Loading

zadjii-msft commented Feb 28, 2022

lhecker commented Feb 28, 2022

lhecker commented Feb 28, 2022

va-it commented Feb 28, 2022

va-it commented Mar 1, 2022 •

edited

Loading

lhecker commented Mar 1, 2022

va-it commented Mar 1, 2022 •

edited

Loading

lhecker commented Mar 1, 2022

va-it commented Mar 1, 2022

lhecker commented Mar 1, 2022 •

edited

Loading

zadjii-msft commented Mar 1, 2022

va-it commented Mar 1, 2022

lhecker commented Mar 1, 2022 •

edited

Loading

AkariiinMKII commented Sep 26, 2022

Yastruhank commented Oct 9, 2022

teeroddesigns commented Oct 18, 2022

fredizzimo commented Dec 17, 2022

alecthegeek commented Dec 20, 2022

GlennWo commented Dec 24, 2022 •

edited by lhecker

Loading

johanvanmol commented Jan 12, 2023

ChromaticRanger commented Apr 7, 2023

MrKomputerKid commented Sep 5, 2023

4N7 commented Sep 13, 2023

Hoernchen commented Nov 16, 2023

DHowett commented Nov 16, 2023

Hoernchen commented Nov 16, 2023

anatilopan commented Dec 5, 2023 •

edited

Loading

Gonkers commented Dec 6, 2023 •

edited

Loading

NewtonChutney commented Dec 28, 2023

lhecker commented Jan 8, 2024

NewtonChutney commented Jan 8, 2024

dlplenin commented Aug 8, 2024 •

edited

Loading

DonutWrecker commented Aug 10, 2024

ignatirabo commented Nov 4, 2024 •

edited

Loading

Unable to find the selected font CaskaydiaCove NF #12587

Unable to find the selected font CaskaydiaCove NF #12587

Comments

va-it commented Feb 26, 2022 • edited Loading

zadjii-msft commented Feb 28, 2022

lhecker commented Feb 28, 2022

lhecker commented Feb 28, 2022

va-it commented Feb 28, 2022

va-it commented Mar 1, 2022 • edited Loading

lhecker commented Mar 1, 2022

va-it commented Mar 1, 2022 • edited Loading

lhecker commented Mar 1, 2022

va-it commented Mar 1, 2022

lhecker commented Mar 1, 2022 • edited Loading

zadjii-msft commented Mar 1, 2022

va-it commented Mar 1, 2022

lhecker commented Mar 1, 2022 • edited Loading

AkariiinMKII commented Sep 26, 2022

Yastruhank commented Oct 9, 2022

teeroddesigns commented Oct 18, 2022

fredizzimo commented Dec 17, 2022

alecthegeek commented Dec 20, 2022

GlennWo commented Dec 24, 2022 • edited by lhecker Loading

johanvanmol commented Jan 12, 2023

ChromaticRanger commented Apr 7, 2023

MrKomputerKid commented Sep 5, 2023

4N7 commented Sep 13, 2023

Hoernchen commented Nov 16, 2023

DHowett commented Nov 16, 2023

Hoernchen commented Nov 16, 2023

anatilopan commented Dec 5, 2023 • edited Loading

Gonkers commented Dec 6, 2023 • edited Loading

Windows 11 23H2

NewtonChutney commented Dec 28, 2023

lhecker commented Jan 8, 2024

NewtonChutney commented Jan 8, 2024

dlplenin commented Aug 8, 2024 • edited Loading

DonutWrecker commented Aug 10, 2024

ignatirabo commented Nov 4, 2024 • edited Loading

va-it commented Feb 26, 2022 •

edited

Loading

va-it commented Mar 1, 2022 •

edited

Loading

va-it commented Mar 1, 2022 •

edited

Loading

lhecker commented Mar 1, 2022 •

edited

Loading

lhecker commented Mar 1, 2022 •

edited

Loading

GlennWo commented Dec 24, 2022 •

edited by lhecker

Loading

anatilopan commented Dec 5, 2023 •

edited

Loading

Gonkers commented Dec 6, 2023 •

edited

Loading

dlplenin commented Aug 8, 2024 •

edited

Loading

ignatirabo commented Nov 4, 2024 •

edited

Loading