Repository navigation
Terminal suddenly can't find the font Cascadia Mono #11648
Description
Windows Terminal version (or Windows build number)
10.0.19043.1288
Other Software
No response
Steps to reproduce
Just starting the Terminal on Windows 10. Not running as admin.
Expected Behavior
A new terminal window
Actual Behavior
Got this error
`Unable to find the selected font "Cascadia Mono".
"Consolas" has been selected instead.
Please either install the missing font or choose another one.`
Reacted by Diogo Paschoal, Sqwrly, Peru S, Mark Kim, Will Fenton, soustruh, Chase Miller, Kai, Ilja Nosik, Cade Roux and 6 more
Activity
ChameleonDevil commentedon Oct 29, 2021
I added a comment on Cascadia Code font repo for a solution on the font installation, for Windows Terminal and VS Code:
Please check there, I have discovered "Cascadia Mono" to be missing (can't even get it reinstalled currently), but show there how to update Windows Terminal and VS Code to use "Cascadia Mono PL"
Peru-S commentedon Oct 30, 2021
zadjii-msft commentedon Nov 1, 2021
this is the thread
We've tracked this in other threads in the past, and we've done work to mitigate this before, but we didn't get all of it. Every time we push an update, more folks start running into this again. We've got an idea of what's wrong here - one of the code paths does the right thing for the SxS font lookup, and the other path doesn't, and that leads to this warning.
In the past, we used #9375 to track this. #9734 attempted to mitigate. #10305 tracked the version of this that caused a crash on startup.
So this was the first thread for the issue during this update, congrats.
IF YOU'RE HITTING THIS
Try "Repairing" the Terminal app, by going to "Settings > Apps > {whatever Terminal Install you have} > Advanced Options > Repair". This shouldn't delete your settings. (But "Reset" will, so be careful!)
If you comment some variation of "me too" in this thread,
you will be removed from the selfhost programyour comment will be minimized as spam, thanks.37 remaining items
Another attempt at fixing nearby font loading (#12904)
Another attempt at fixing nearby font loading (#12904)
AlpineWeezl commentedon Oct 14, 2022
Unfortunately, this issue still exists with completely updated system. I also did the reset as mentioned in the second post of this thread.
cmschlenke commentedon Aug 16, 2023
If any poor soul has found their way here wondering why Windows Terminal can't find their font, let me assure you that this is actually not a Windows Terminal bug, or even a Windows bug. This behavior is caused by not having the font installed for all users. Follow these steps to remedy the problem... https://answers.microsoft.com/en-us/windows/forum/all/solution-installed-fonts-disappearing-after/146f4039-47c3-4017-a9b1-76f72badce39
psxlover commentedon Oct 23, 2023
I just run into this issue. Version 1.18.2822.0. Windows 10. According to the Microsoft Store Terminal was updated today.
The previous comment does not apply in my case, there is no Fonts folder in %appdata%..\Local\Microsoft\Windows.
What's even more confusing is that in "Fonts" they are "there" but are invisible until I hove over them with the mouse in which case only the names appear:
DHowett commentedon Oct 23, 2023
This was an issue on Windows 10 that Terminal had worked around. We recently (accidentally) broke our workaround. Stay tuned. 😄
psxlover commentedon Oct 23, 2023
Glad to hear it is a known issue and not just something wrong with my PC.
barkermn01 commentedon Nov 7, 2023
Dustin L. Howett (@DHowett) i believe there is a specific term for that it's called a Regression :D
stevenwong commentedon Nov 30, 2023
If anyone needs a temporary fix, uninstalling then reinstalling the Terminal app solved it for me. Neither repair or reset worked.
IMB11 commentedon Sep 7, 2024
I fixed this issue by making sure that the font being used was installed for all users instead of locally just for my user.