Repository navigation
Unable to find the selected font "Cascadia Mono" in Windows 10 #12420
Description
Windows Terminal version
1.13.10336.0
Windows build number
10.0.19044.0
Other Software
I have both Windows Terminal (1.11.3471.0) and Windows Terminal Preview (1.13.10336.0) installed. The Store says Windows Terminal Preview updated today, but both apps are unable to find the "Cascadia Mono" font, which I'm told should be bundled with the app.
Steps to reproduce
Open Windows Terminal Preview
Expected Behavior
A "Warning" popup does not appear.
Actual Behavior
A "Warning" popup in the Terminal window appears with the following text
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 Riley Labrecque
Activity
rlabrecque commentedon Feb 8, 2022
Again?! :(
This was a really annoying issue some 5+ months ago. Not great that it's popped up again.
zadjii-msft commentedon Feb 8, 2022
Thanks for the suggestion! Please make sure to search for duplicates when filing new issues. This is already being tracked by another issue on our repo - please refer to #11648 for more discussion.
/dup #11648
lhecker commentedon Feb 18, 2022
FYI: When I implemented a fix I used APIs which only work on Windows 11.
Today I made some changes to make it work on Windows 10. I'll open a PR soon.
7 remaining items
Fix Windows 10 support for nearby font loading (#12554)
Fix Windows 10 support for nearby font loading (#12554)
Fix Windows 10 support for nearby font loading (#12554)
srdjanjovcic commentedon Apr 13, 2022
This is not fixed in Preview 1.13.10983.0
srdjanjovcic commentedon Apr 13, 2022
My Windows Terminal Preview was updated today, so it is clear that update is still broken. What is a workaround?
zadjii-msft commentedon Apr 13, 2022
Srdjan Jovčić (@srdjanjovcic) Are you seeing this with specifically "Cascadia Mono" or "Cascadia Code"? That's HIGHLY unexpected even with this fix. Which OS version are you on?
srdjanjovcic commentedon Apr 13, 2022
Mike Griese (@zadjii-msft) It is "Cascadia Mono" (can't stand the ligatures). I am on Windows 10.
zadjii-msft commentedon Apr 13, 2022
Huh. Leonard Hecker (@lhecker) & Dustin L. Howett (@DHowett) for visibility. Any ideas if we left in any logging do diagnose why the preemptive fallback wouldn't be working?
lhecker commentedon Apr 13, 2022
Mike Griese (@zadjii-msft) Yes, the entire nearby font loader function can only exit with debug logs on error. It should be possible to see what's going on with DebugView.
IIRC we did test this on Windows 10 (15021 and later) and it seems to work at least for some according to #12879.
srdjanjovcic commentedon Apr 13, 2022
Well, my repro is already gone, unless you have debug logs in some file in somewhere (temp folder?)
This is Windows 10.0.19044.1586, latest publicly available version (21H2).
srdjanjovcic commentedon Apr 13, 2022
Just updated Windows Terminal Preview on other Windows 10 machine (same version), and bug didn't repro.
lhecker commentedon Apr 14, 2022
Srdjan Jovčić (@srdjanjovcic) I think I've figured out what went wrong. See #12904.