Repository navigation
Unable to find the selected font "Cascadia Mono". #9375
Description
There is a bug in the application deployment platform on recent versions of Windows that results in the Cascadia Mono font (the default font) being unreadable. Terminal cannot read it, and if it tries it will crash.
Unfortunately, that means that through no fault of your own, you'll get a dialog that says we can't find Cascadia Mono or Cascadia Code.
KNOWN SOLUTIONS
- Either reboot or
- choose to "Repair" the Terminal application in the "All apps" list in Settings.
ONLY COMMENT HERE IF THE WORKAROUNDS DON'T HELP
Since there are so many subscribers to this thread, we will lock it if it starts to accumulate unrelated commentary.
2021-06-10: we’ve locked it as folks haven’t read this disclaimer.
Original bug in Terminal 1.6
Environment
Windows build number: Microsoft Windows NT 10.0.19042.0
Windows Terminal version: 1.6.10571.0
Steps to reproduce
This 'happens on my machine', not sure if easily reproducible.
- Start Microsoft Terminal
Expected behavior
Microsoft terminal opens on the default terminal
Actual behavior
A pop-up is shown with the following error message:
Transcript:
Warning
Unable to find the selected font "Cascadia Mono".
"Consolas" has been selected instead.
Please either install the missing font or choose another one.
Additional information
Other applications, Microsoft Word, Paint.NET, show the Cascadia Mono font and allow usage without any issues.
Activity
Flightkick commentedon Mar 4, 2021
Off course I think of a possible fix right after submitting the issue.
Starting Microsoft Terminal as Administrator once fixes the issue.
Subsequent runs as non-admin do not show the warning anymore.
Leaving the issue open so the maintainers can decide if this should be handled without the 'start as admin' workaround/fix.
oskar commentedon Mar 5, 2021
After upgrading to 1.6.10571.0, this happens to me as well. But starting as administrator does not help for me. Any other workaround?
MuTLY commentedon Mar 5, 2021
I'm experiencing the same behavior, this was not an issue until about a week ago. In my case, it is not finding the "Ubuntu Regular" font, and as you can see, the font is installed correctly.
zadjii-msft commentedon Mar 5, 2021
Hey Michael Niksa (@miniksa) can you take a look at this and #9157? We're seeing a pretty dramatic uptick in the number of these kinds of reports after adding the warning. Did we change anything about the font lookup when we added the dialog?
J-Hoff389 commentedon Mar 5, 2021
I have a Similar experience but with the font "Cascadia Code PL". The message does not go away if Started as Administrator.
Rod-in-NM commentedon Mar 5, 2021
I've also having an issue with Windows Terminal not being able to find Cascadia Code PL. I've been using Cascadia Code PL for several months with no issues, now Windows Terminal can't find it.
miniksa commentedon Mar 5, 2021
I will not have the capacity to look at this for at least a week.
fujiawei-dev commentedon Mar 6, 2021
I am also suffering from this problem, after an automatic update via the Windows Store.
43 remaining items
bikeoid commentedon Jun 6, 2021
I finally solved the problem with losing active terminal sessions from an automatic update by disabling automatic updates for Windows Apps. I just got the missing "Cascadia Mono" bug today also.
softwrx commentedon Jun 6, 2021
Thanks bikeoid , good idea. thuogh I'd prefer to just disable it for the terminal and not all apps. i'll look it up and see if the options are that granular.
rcarde commentedon Jun 7, 2021
Greg Youngblood (@softwrx) I had the same issue when auto-upgraded to 1.8.1521.0 which, as far as I know, is not pre-release. So I think the update process is borked.
crash-horror commentedon Jun 7, 2021
Well, resetting the app, and unticking all fonts, chose cascadia code did it for me. You got limited selection ofc
stefanwendelmann commentedon Jun 7, 2021
Had to
And the error was gone.
ghylander commentedon Jun 8, 2021
I know the issue is closed, but i had it happen today for the very first time ever, couldnt find cascadia mono, on v1.8.1521.0
"repaired" the app from the windows 10 settings menu, restarted terminal and it worked
ErikSchierboom commentedon Jun 8, 2021
I had the same thing as Gustavo Hylander (@ghylander) and the proposed solution to repair the app did indeed work for me.
kusma commentedon Jun 8, 2021
I just triggered the same issue, but sadly "repairing" the app did nothing for me. I'm using 1.8.1521.0.
kusma commentedon Jun 8, 2021
I can also add that the font (Cascadia Mono) is installed and works fine in other applications.
magosla commentedon Jun 9, 2021
Repairing the App did work for me
SteveALee commentedon Jun 10, 2021
This is a "Me too" posts but adding that in Windows terminal "about" the version is "1.8.1521.0" but latest release is only "v1.8.1444.0". huh? Deployment issues? Time to repoen this issue?
DHowett commentedon Jun 10, 2021
Please refer to the body of the first post in this issue.