Unable to find the selected font "Cascadia Mono". #9375

Flightkick · 2021-03-04T12:21:06Z

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.

The text was updated successfully, but these errors were encountered:

Flightkick · 2021-03-04T12:23:53Z

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 · 2021-03-05T07:41:10Z

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 · 2021-03-05T12:06:35Z

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 · 2021-03-05T12:14:51Z

Hey @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 · 2021-03-05T14:10:32Z

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 · 2021-03-05T17:15:03Z

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 · 2021-03-05T18:26:02Z

Hey @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?

I will not have the capacity to look at this for at least a week.

fujiawei-dev · 2021-03-06T11:48:47Z

I am also suffering from this problem, after an automatic update via the Windows Store.

ghost · 2021-03-06T15:39:34Z

Same thing here, Source Code Pro.

eturnq · 2021-03-08T15:52:38Z

"Install for all users" fixed this trouble for me.

MuTLY · 2021-03-08T16:30:03Z

"Install for all users" fixed this trouble for me.

I've tried that and it didn't make a difference. I even rebooted the computer after reinstalling the fonts using the "Install for all users" option. On startup, Windows Terminal still complains about a missing font that's not missing and can be used anywhere else on the system ("Ubuntu Regular", in my case).

https://design.ubuntu.com/font/

Xbuduo · 2021-03-09T09:20:20Z

The one installed from the store has no problem. But the one installed by scoop has the same issue.

yikakia · 2021-03-09T15:33:14Z

Same happens to me at

version 1.6.10571.0

WSLUser · 2021-03-10T15:29:23Z

I hit this issue today (don't know why not before now) but when I installed the Cascadia Code font directly to Windows, the error disappeared and the font appears as it should. It did appear to look like Consolas before doing this. So I think WT isn't reading the font files correctly from inside the msix package.

hawko2600 · 2021-03-11T05:33:46Z

I had the same issue with the Store version, using "Cascadia Code PL Regular" as the font.
If I remove the "Regular" from the font string text, I do not get the error dialogue and the font loads correctly.

Edit: I should also mention, font is installed in C:\Windows\Fonts for all users and I pulled the current version of Cascadia Code PL off Github that day - version 2005.150. Earlier version also didn't load properly so I used opportunity to upgrade it.

Rod-in-NM · 2021-03-11T15:41:14Z

I never had "Cascadia Code PL Regular" as the font, only "Cascadia Code PL". And I still get that error dialogue.

lonelydev · 2021-03-12T00:01:13Z

I ran into a similar issue. I followed all sorts of instructions from various different posts online and I finally got powershell to recognize the right font but windows terminal would still not pick it up.
here is my powershell core rendering the font Space Mono for Powerline correctly.

A screenshot of the console's properties:

However, I tried the same in Windows Terminal and guess what?

settings file:

I got lucky and got help from smart people online by posting this question on twitter -https://twitter.com/eakangk/status/1369949792034562048?s=20

And someone responded that I was using the full name of the font and not the short name. I quickly opened the modern font setting window and searched for the font 'space' and that was when I realised, I couldn't find it.

However the same font would show up in the old schools c:\windows\fonts folder:

This prompted me to think that maybe, i didn't really install it for all users.
Luckily I had a clone of https://t.co/Xo6f5LikOV?amp=1 so I rightclicked the font and clicked install for all users.

and guess what happened next?

it appeared in Font Settings!

I couldn't wait to open up my windows terminal to check how it looked like and... wait for it....

it worked.

Thank you everyone for the valuable suggestions and directing me to this issue here. i had almost given up on this back in January, thinking I was taking too long to set up a prompt.

Rod-in-NM · 2021-03-12T14:50:19Z

@lonelydev, I just checked my C:\Windows\Font folder. I don't have any font there named Space Mono for Powerline there. In fact, I don't have any font there that starts with Space Mono. Should I try to find that and install it?

lonelydev · 2021-03-12T15:31:54Z

@Rod-in-NM
seems like you need powerline fonts from https://github.com/powerline/fonts
once you clone the repo to your pc, you can then choose to install the fonts you wish to Windows right clicking the font image and then clicking install for all users.

That should get you the font you want.
In my case, I configured my Windows Terminal to use Space Mono, so I only selectively installed that font and it started rendering correctly.

Rod-in-NM · 2021-03-12T15:55:08Z

@lonelydev I've cloned that font repo. The I installed for all users these fonts:

Space Mono Bold for Powerline
Space Mono Bold Italic for Powerline
Space Mono for Powerline
Space Mone Italic for Powerline

I didn't think I needed the others.

This hasn't helped - I'm still getting that error message whenever I get into Windows Terminal

Reduce instances of font fallback dialog through package font loading, basic name trimming, and revised fallback test - Adjusts the font dialog to only show when we attempt last-chance resolution from our hardcoded list of font names with a flag instead of with a string comparison by name - Adds a resolution step to trim the font name by word from the end and retry to attempt to resolve a proper font that just has a weight suffix - Adds a second font collection to font loading that will attempt to locate all TTF files sitting next to our binary, like in our package - [x] Wrote my font preference in the JSON as `Cascadia Code Heavy` and watched it quietly resolve to just `Cascadia Code` without the dialog. - [x] Put a font that isn't registered with the system into the layout directory for the package, set it as my desired font in Terminal, and watched it load just fine. - [x] Try a font name with different casing and see if dialog doesn't pop anymore - [x] Try a font with different (localized) names like ＭＳゴシック and see if dialog doesn't pop anymore - [x] Check Win7 with WPF target Closes #9375

Reduce instances of font fallback dialog through package font loading, basic name trimming, and revised fallback test - Adjusts the font dialog to only show when we attempt last-chance resolution from our hardcoded list of font names with a flag instead of with a string comparison by name - Adds a resolution step to trim the font name by word from the end and retry to attempt to resolve a proper font that just has a weight suffix - Adds a second font collection to font loading that will attempt to locate all TTF files sitting next to our binary, like in our package - [x] Wrote my font preference in the JSON as `Cascadia Code Heavy` and watched it quietly resolve to just `Cascadia Code` without the dialog. - [x] Put a font that isn't registered with the system into the layout directory for the package, set it as my desired font in Terminal, and watched it load just fine. - [x] Try a font name with different casing and see if dialog doesn't pop anymore - [x] Try a font with different (localized) names like ＭＳゴシック and see if dialog doesn't pop anymore - [x] Check Win7 with WPF target Closes #9375 (cherry picked from commit 7f5a19b)

ghost · 2021-04-14T17:03:30Z

🎉This issue was addressed in #9734, which has now been successfully released as Windows Terminal v1.7.1033.0.:tada:

Handy links:

ghost · 2021-04-14T17:06:51Z

🎉This issue was addressed in #9734, which has now been successfully released as Windows Terminal Preview v1.8.1032.0.:tada:

Handy links:

sigoden · 2021-04-22T02:26:35Z

open Windows Terminal Settings, add/change fontFace setting

{
    "profiles": {
         "defaults":  {
                "fontFace": "Consolas"  //  edit here

brucek2 · 2021-06-04T22:41:01Z

This just started happening to me today (wasn't happening yesterday or for weeks before.) In my case the missing font is "Cascadia Mono". I can't think of any update, config change, or anything else that should have triggered a change.

Edit: Also want to clarify that for me the biggest issue isn't having to click "OK", it's that the font I enjoyed and preferred is no longer being used for no good reason I can think of.

DHowett · 2021-06-04T22:45:32Z

@brucek2 sorry about that. We actually had to push an update to make sure we didn't crash when this happens. I edited the original/top post on this issue to sum up what's happening.

softwrx · 2021-06-05T17:00:21Z

It started happening to me today. Weeks no issues then all of WSL linux sessions closed, about 8 of them, while they were running tasks and without notifying me or giving me the option to delay/cancel/not update at this time! This is a very very bad update procedure as it closed active SSH connections in all of these. Fortunately I started the critical jobs via screen.

Apps, especially terminal apps, that can be open for extended periods of time while running long-running jobs should not silently just close and update in the middle of the night.

As near as I can tell an update was applied and my terminal is now 1.9.1523. Not happy that it silently updated and closed my active sessions. And now I have the missing font error too. Which I did not have before. In fact everything had been working very well before. Now it's having problems. Very annoying.

softwrx · 2021-06-05T17:09:35Z

As annoying as it was, I normally do not reboot because I might have things going for several days, I closed everything down and rebooted and it appears the error with the font has gone away.

So this "update" not only closed all my active terminal sessions without warning in the middle of the night, it also forced a reboot to fix this error.

Lest I only complain - I realize this is a preview release, so some hiccups are to be expected. I was caught off guard by the sudden closing and update without warning though. That's not good.

Other than this one issue, the preview version has been working great. My only issue is an apparent lack of a keyboard shortcut to start a new terminal window. The preview has otherwise been very useful. The terminal preview, along with WSL, has enabled my switch from Mac to Windows as I live in various unix/linux terminals most of the day with my job. Good job on it.

bikeoid · 2021-06-06T14:08:05Z

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 · 2021-06-06T14:12:13Z

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.

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 · 2021-06-07T05:38:34Z

Lest I only complain - I realize this is a preview release, so some hiccups are to be expected. I was caught off guard by the sudden closing and update without warning though. That's not good.

@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 · 2021-06-07T06:18:45Z

Well, resetting the app, and unticking all fonts, chose cascadia code did it for me. You got limited selection ofc

stefanwendelmann · 2021-06-07T12:40:35Z

Had to

Close Terminal
Install font from https://github.com/microsoft/cascadia-code/releases for all users
kill the explorer.exe process (from Task Manager)
start the explorer.exe process (from Task Manager)
Start Terminal

And the error was gone.

ghylander · 2021-06-08T06:30:16Z

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 · 2021-06-08T08:21:43Z

I had the same thing as @ghylander and the proposed solution to repair the app did indeed work for me.

kusma · 2021-06-08T08:58:41Z

I just triggered the same issue, but sadly "repairing" the app did nothing for me. I'm using 1.8.1521.0.

kusma · 2021-06-08T09:02:29Z

I can also add that the font (Cascadia Mono) is installed and works fine in other applications.

magosla · 2021-06-09T09:05:07Z

Repairing the App did work for me

SteveALee · 2021-06-10T09:56:24Z

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 · 2021-06-10T13:19:40Z

Please refer to the body of the first post in this issue.

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 Mar 4, 2021

zadjii-msft added Area-Fonts Related to the font Issue-Bug It either shouldn't be doing this or needs an investigation. Priority-2 A description (P2) Product-Terminal The new Windows Terminal. labels Mar 5, 2021

ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Mar 5, 2021

zadjii-msft assigned miniksa Mar 9, 2021

zadjii-msft added this to the Terminal v1.8 milestone Mar 9, 2021

zadjii-msft added the zStable-Service-Consider label Mar 9, 2021

miniksa mentioned this issue Apr 7, 2021

Parse/understand weight suffixes in font names #9744

Open

ghost closed this as completed in #9734 Apr 8, 2021

ghost removed the In-PR This issue has a related PR label Apr 8, 2021

ghost added the Resolution-Fix-Committed Fix is checked in, but it might be 3-4 weeks until a release. label Apr 8, 2021

zadjii-msft mentioned this issue Apr 12, 2021

Unable to find the selected font "Cascadia Mono" #9786

Closed

DHowett pinned this issue Jun 4, 2021

microsoft locked and limited conversation to collaborators Jun 10, 2021

miniksa removed the zStable-Service-Consider label Sep 27, 2021

zadjii-msft unpinned this issue Sep 29, 2021

This issue was closed.

Unable to find the selected font "Cascadia Mono". #9375

Unable to find the selected font "Cascadia Mono". #9375

Comments

Flightkick commented Mar 4, 2021 • edited by zadjii-msft Loading

Environment

Steps to reproduce

Expected behavior

Actual behavior

Additional information

Flightkick commented Mar 4, 2021

oskar commented Mar 5, 2021

MuTLY commented Mar 5, 2021

zadjii-msft commented Mar 5, 2021

J-Hoff389 commented Mar 5, 2021

Rod-in-NM commented Mar 5, 2021

miniksa commented Mar 5, 2021

fujiawei-dev commented Mar 6, 2021

ghost commented Mar 6, 2021

eturnq commented Mar 8, 2021

MuTLY commented Mar 8, 2021 • edited Loading

Xbuduo commented Mar 9, 2021

yikakia commented Mar 9, 2021

WSLUser commented Mar 10, 2021

hawko2600 commented Mar 11, 2021 • edited Loading

Rod-in-NM commented Mar 11, 2021

lonelydev commented Mar 12, 2021

Rod-in-NM commented Mar 12, 2021

lonelydev commented Mar 12, 2021

Rod-in-NM commented Mar 12, 2021

ghost commented Apr 14, 2021

ghost commented Apr 14, 2021

sigoden commented Apr 22, 2021

brucek2 commented Jun 4, 2021 • edited Loading

DHowett commented Jun 4, 2021

softwrx commented Jun 5, 2021

softwrx commented Jun 5, 2021

bikeoid commented Jun 6, 2021

softwrx commented Jun 6, 2021

rcarde commented Jun 7, 2021 • edited Loading

crash-horror commented Jun 7, 2021

stefanwendelmann commented Jun 7, 2021

ghylander commented Jun 8, 2021

ErikSchierboom commented Jun 8, 2021

kusma commented Jun 8, 2021 • edited Loading

kusma commented Jun 8, 2021

magosla commented Jun 9, 2021

SteveALee commented Jun 10, 2021

DHowett commented Jun 10, 2021

Flightkick commented Mar 4, 2021 •

edited by zadjii-msft

Loading

MuTLY commented Mar 8, 2021 •

edited

Loading

hawko2600 commented Mar 11, 2021 •

edited

Loading

brucek2 commented Jun 4, 2021 •

edited

Loading

rcarde commented Jun 7, 2021 •

edited

Loading

kusma commented Jun 8, 2021 •

edited

Loading