starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Unable to find the selected font "Cascadia Mono" in Windows 10 #16706

New Issue
Closed
opened 2026-01-31 05:20:14 +00:00 by claunia · 15 comments
claunia commented 2026-01-31 05:20:14 +00:00
Owner
Copy Link

Originally created by @anthonypants on GitHub (Feb 7, 2022).

Originally assigned to: @lhecker on GitHub.

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.
Originally created by @anthonypants on GitHub (Feb 7, 2022). Originally assigned to: @lhecker on GitHub. ### 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. ```
claunia commented 2026-01-31 05:20:15 +00:00
Author
Owner
Copy Link

@rlabrecque commented on GitHub (Feb 8, 2022):

Again?! :(

This was a really annoying issue some 5+ months ago. Not great that it's popped up again.

@rlabrecque commented on GitHub (Feb 8, 2022): Again?! :( This was a really annoying issue some 5+ months ago. Not great that it's popped up again.
claunia commented 2026-01-31 05:20:15 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (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

@zadjii-msft commented on GitHub (Feb 8, 2022): Thanks for the suggestion! Please make sure to [search for duplicates](https://github.com/microsoft/terminal/issues?q=is%3Aissue+Unable+to+find+the+selected+font+%22Cascadia+Mono%22+) when filing new issues. This is already being tracked by another issue on our repo - please refer to #11648 for more discussion. /dup #11648
claunia commented 2026-01-31 05:20:15 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 8, 2022):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Feb 8, 2022): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
claunia commented 2026-01-31 05:20:16 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (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.

@lhecker commented on GitHub (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.
claunia commented 2026-01-31 05:20:16 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Feb 18, 2022):

I'm repurposing this issue to submit a change for Windows 10 support.

@lhecker commented on GitHub (Feb 18, 2022): I'm repurposing this issue to submit a change for Windows 10 support.
claunia commented 2026-01-31 05:20:16 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 25, 2022):

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

Handy links:

@ghost commented on GitHub (Mar 25, 2022): :tada:This issue was addressed in #12554, which has now been successfully released as `Windows Terminal Preview v1.13.1073`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.13.1073) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
claunia commented 2026-01-31 05:20:16 +00:00
Author
Owner
Copy Link

@srdjanjovcic commented on GitHub (Apr 13, 2022):

This is not fixed in Preview 1.13.10983.0

@srdjanjovcic commented on GitHub (Apr 13, 2022): This is not fixed in Preview 1.13.10983.0
claunia commented 2026-01-31 05:20:16 +00:00
Author
Owner
Copy Link

@srdjanjovcic commented on GitHub (Apr 13, 2022):

My Windows Terminal Preview was updated today, so it is clear that update is still broken. What is a workaround?

@srdjanjovcic commented on GitHub (Apr 13, 2022): My Windows Terminal Preview was updated today, so it is clear that update is still broken. What is a workaround?
claunia commented 2026-01-31 05:20:16 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 13, 2022):

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

@zadjii-msft commented on GitHub (Apr 13, 2022): @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?
claunia commented 2026-01-31 05:20:17 +00:00
Author
Owner
Copy Link

@srdjanjovcic commented on GitHub (Apr 13, 2022):

@zadjii-msft It is "Cascadia Mono" (can't stand the ligatures). I am on Windows 10.

@srdjanjovcic commented on GitHub (Apr 13, 2022): @zadjii-msft It is "Cascadia Mono" (can't stand the ligatures). I am on Windows 10.
claunia commented 2026-01-31 05:20:17 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 13, 2022):

Huh. @lhecker & @DHowett for visibility. Any ideas if we left in any logging do diagnose why the preemptive fallback wouldn't be working?

@zadjii-msft commented on GitHub (Apr 13, 2022): Huh. @lhecker & @DHowett for visibility. Any ideas if we left in any logging do diagnose why the preemptive fallback _wouldn't_ be working?
claunia commented 2026-01-31 05:20:17 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Apr 13, 2022):

@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.

@lhecker commented on GitHub (Apr 13, 2022): @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](https://docs.microsoft.com/en-us/sysinternals/downloads/debugview). IIRC we did test this on Windows 10 (15021 and later) and it seems to work at least for some according to #12879.
claunia commented 2026-01-31 05:20:17 +00:00
Author
Owner
Copy Link

@srdjanjovcic commented on GitHub (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 commented on GitHub (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).
claunia commented 2026-01-31 05:20:17 +00:00
Author
Owner
Copy Link

@srdjanjovcic commented on GitHub (Apr 13, 2022):

Just updated Windows Terminal Preview on other Windows 10 machine (same version), and bug didn't repro.

@srdjanjovcic commented on GitHub (Apr 13, 2022): Just updated Windows Terminal Preview on other Windows 10 machine (same version), and bug didn't repro.
claunia commented 2026-01-31 05:20:18 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Apr 14, 2022):

@srdjanjovcic I think I've figured out what went wrong. See #12904.

@lhecker commented on GitHub (Apr 14, 2022): @srdjanjovcic I think I've figured out what went wrong. See #12904.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Tag-Fix Priority-3 Product-Terminal Resolution-Fix-Committed
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#16706
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?