-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to find the selected font CaskaydiaCove NF #12587
Comments
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). |
Here's what I did:
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 🙏. |
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 |
@va-it Can you check the old legacy Fonts control panel? You can find it in the start menu by typing "Fonts". |
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. I believe something is wrong with Windows 11... |
@va-it Is your "Windows Font Cache Service" running? Which .ttf file from the nerd fonts collection are you using specifically? |
something makes me think this is like #3257 |
@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 🙂. |
@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. |
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. |
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. |
I have the same issue. Restarting the Windows Font Cache Service also works for me. |
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. |
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 |
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.
|
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. |
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. |
Amazing! Thank you! This worked for me on my PC at home! Once again thank you! |
The replies in this issue contain a malformed path.
|
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. |
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) |
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. 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)
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! ^^ |
I just decided to try Oh-My-Posh and I ran into this issue today. Windows 11 23H2Edit: 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. |
I have recently been seeing more of this issue:
WT version: 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.
|
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) |
Yep, I had installed for all users and removed those in my (user's) localappdata.. Now I think of it.. I don't remember seeing the font not found prompts on my non-admin enterprise user account.. 🤔 |
The solution in the link solved my issue. |
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
The text was updated successfully, but these errors were encountered: