starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

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

New Issue
Closed
opened 2026-01-31 03:41:50 +00:00 by claunia · 17 comments
claunia commented 2026-01-31 03:41:50 +00:00
Owner
Copy Link

Originally created by @tgriff on GitHub (Apr 12, 2021).

Windows Terminal version (or Windows build number)

1.6.10571.0

Other Software

No response

Steps to reproduce

My OS rebooted after an update. Windows Terminal may also have been updated. At any rate, now when I run Windows Terminal (and any time I open a new tab), I get the following error:
image

I figured I could just set the font to "Consolas" permanently to get rid of the error message, but when I look at my settings.json file, I don't see where "Cascadia Mono" may have been configured. Other than setting the "fontSize" I haven't modified any settings w.r.t. fonts.

Also note that, as far as I am aware, I did not explicitly/intentionally uninstall "Cascadia Mono", although quick peek in "C:\Windows\Fonts" shows that it is no longer there.

Expected Behavior

I don't expect to see any errors about fonts, especially considering I didn't explicitly configure any in my settings.json.

Actual Behavior

Every time I open a new tab in Windows Terminal I get an error saying "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 @tgriff on GitHub (Apr 12, 2021). ### Windows Terminal version (or Windows build number) 1.6.10571.0 ### Other Software _No response_ ### Steps to reproduce My OS rebooted after an update. Windows Terminal may also have been updated. At any rate, now when I run Windows Terminal (and any time I open a new tab), I get the following error: ![image](https://user-images.githubusercontent.com/34492055/114411512-17e5c800-9b61-11eb-8818-3728d8764a8e.png) I figured I could just set the font to "Consolas" permanently to get rid of the error message, but when I look at my settings.json file, I don't see where "Cascadia Mono" may have been configured. Other than setting the "fontSize" I haven't modified any settings w.r.t. fonts. Also note that, as far as I am aware, I did not explicitly/intentionally uninstall "Cascadia Mono", although quick peek in "C:\Windows\Fonts" shows that it is no longer there. ### Expected Behavior I don't expect to see any errors about fonts, especially considering I didn't explicitly configure any in my settings.json. ### Actual Behavior Every time I open a new tab in Windows Terminal I get an error saying "Unable to find the selected font 'Cascadia Mono'. 'Consolas' has been selected instead. Please either install the missing font or choose another one."
claunia added the Resolution-Duplicate label 2026-01-31 03:41:50 +00:00
claunia commented 2026-01-31 03:41:51 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 12, 2021):

Thanks for the report! 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 #9375 for more discussion.

/dup #9375

@zadjii-msft commented on GitHub (Apr 12, 2021): Thanks for the report! 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 #9375 for more discussion. /dup #9375
claunia commented 2026-01-31 03:41:51 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 12, 2021):

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 (Apr 12, 2021): 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 03:41:51 +00:00
Author
Owner
Copy Link

@tgriff commented on GitHub (Apr 12, 2021):

Apologies for the noise, it seems I only searched for Active issues when I was looking for dupes for this one.

@tgriff commented on GitHub (Apr 12, 2021): Apologies for the noise, it seems I only searched for Active issues when I was looking for dupes for this one.
claunia commented 2026-01-31 03:41:52 +00:00
Author
Owner
Copy Link

@ismailhkose commented on GitHub (Oct 12, 2021):

@zadjii-msft

According to this message, the bug was resolved at Windows Terminal v1.7.1033.0, and the issue was closed, however I still see the same issue at Windows Terminal v1.10.2714.0
https://github.com/microsoft/terminal/issues/9375#issuecomment-819677048

image
image

@ismailhkose commented on GitHub (Oct 12, 2021): @zadjii-msft According to this message, the bug was resolved at Windows Terminal v1.7.1033.0, and the issue was closed, however I still see the same issue at Windows Terminal v1.10.2714.0 https://github.com/microsoft/terminal/issues/9375#issuecomment-819677048 ![image](https://user-images.githubusercontent.com/353824/136893266-a1fe8855-9217-4acc-b113-56d68191c1da.png) ![image](https://user-images.githubusercontent.com/353824/136893300-c02f095e-270c-4c76-a805-8fe063ae7778.png)
claunia commented 2026-01-31 03:41:52 +00:00
Author
Owner
Copy Link

@ismailhkose commented on GitHub (Oct 12, 2021):

@zadjii-msft
Could you reopen this bug as my previous comment refers the issue?
https://github.com/microsoft/terminal/issues/9786#issuecomment-940658984

@ismailhkose commented on GitHub (Oct 12, 2021): @zadjii-msft Could you reopen this bug as my previous comment refers the issue? https://github.com/microsoft/terminal/issues/9786#issuecomment-940658984
claunia commented 2026-01-31 03:41:52 +00:00
Author
Owner
Copy Link

@Rafagd commented on GitHub (Oct 12, 2021):

Apparently this can be worked around by repairing the instalation in Settings -> Apps & Features -> Windows Terminal -> Advanced Options.

https://github.com/microsoft/terminal/issues/11451#issuecomment-938115593

@Rafagd commented on GitHub (Oct 12, 2021): Apparently this can be worked around by repairing the instalation in Settings -> Apps & Features -> Windows Terminal -> Advanced Options. https://github.com/microsoft/terminal/issues/11451#issuecomment-938115593
claunia commented 2026-01-31 03:41:52 +00:00
Author
Owner
Copy Link

@Jo-Zim commented on GitHub (Oct 13, 2021):

Apparently this can be worked around by repairing the instalation in Settings -> Apps & Features -> Windows Terminal -> Advanced Options.

#11451 (comment)

That does not work for Version 1.10!

@Jo-Zim commented on GitHub (Oct 13, 2021): > Apparently this can be worked around by repairing the instalation in Settings -> Apps & Features -> Windows Terminal -> Advanced Options. > > [#11451 (comment)](https://github.com/microsoft/terminal/issues/11451#issuecomment-938115593) That does not work for Version 1.10!
claunia commented 2026-01-31 03:41:53 +00:00
Author
Owner
Copy Link

@Rafagd commented on GitHub (Oct 13, 2021):

Worked for me on v1.10.2714.0

@Rafagd commented on GitHub (Oct 13, 2021): Worked for me on v1.10.2714.0
claunia commented 2026-01-31 03:41:53 +00:00
Author
Owner
Copy Link

@b4bu commented on GitHub (Oct 29, 2021):

Apparently this can be worked around by repairing the instalation in Settings -> Apps & Features -> Windows Terminal -> Advanced Options.

Worked for me, v1.11.2921.0

@b4bu commented on GitHub (Oct 29, 2021): >Apparently this can be worked around by repairing the instalation in Settings -> Apps & Features -> Windows Terminal -> Advanced Options. Worked for me, v1.11.2921.0
claunia commented 2026-01-31 03:41:53 +00:00
Author
Owner
Copy Link

@mugwhump commented on GitHub (Nov 2, 2021):

Apparently this can be worked around by repairing the instalation in Settings -> Apps & Features -> Windows Terminal -> Advanced Options.

Worked for me, v1.11.2921.0

Interesting, didn't work for me in the exact same version.

@mugwhump commented on GitHub (Nov 2, 2021): > > > > Apparently this can be worked around by repairing the instalation in Settings -> Apps & Features -> Windows Terminal -> Advanced Options. > > Worked for me, v1.11.2921.0 Interesting, didn't work for me in the exact same version.
claunia commented 2026-01-31 03:41:53 +00:00
Author
Owner
Copy Link

@donfiguerres commented on GitHub (Apr 10, 2022):

Apparently this can be worked around by repairing the instalation in Settings -> Apps & Features -> Windows Terminal -> Advanced Options.

#11451 (comment)

Thanks! This worked for me.
Version: 1.12.10732.0

@donfiguerres commented on GitHub (Apr 10, 2022): > Apparently this can be worked around by repairing the instalation in Settings -> Apps & Features -> Windows Terminal -> Advanced Options. > > [#11451 (comment)](https://github.com/microsoft/terminal/issues/11451#issuecomment-938115593) Thanks! This worked for me. Version: 1.12.10732.0
claunia commented 2026-01-31 03:41:54 +00:00
Author
Owner
Copy Link

@franciscoestevao commented on GitHub (Apr 11, 2022):

Apparently this can be worked around by repairing the instalation in Settings -> Apps & Features -> Windows Terminal -> Advanced Options.

#11451 (comment)

The repair workaround fixed it for me 👍
Version: 1.12.10732.0

@franciscoestevao commented on GitHub (Apr 11, 2022): > Apparently this can be worked around by repairing the instalation in Settings -> Apps & Features -> Windows Terminal -> Advanced Options. > > [#11451 (comment)](https://github.com/microsoft/terminal/issues/11451#issuecomment-938115593) The repair workaround fixed it for me 👍 Version: 1.12.10732.0
claunia commented 2026-01-31 03:41:54 +00:00
Author
Owner
Copy Link

@christopher-pope commented on GitHub (Apr 22, 2022):

Had this issue occur on Version: 1.12.10982.0. Repairing it resolved the issue.

@christopher-pope commented on GitHub (Apr 22, 2022): Had this issue occur on Version: 1.12.10982.0. Repairing it resolved the issue.
claunia commented 2026-01-31 03:41:54 +00:00
Author
Owner
Copy Link

@LostInBrittany commented on GitHub (Apr 25, 2022):

I still have the problem with version 1.12.10983.0.
Repairing or reset hasn't solved it 😢

@LostInBrittany commented on GitHub (Apr 25, 2022): I still have the problem with version 1.12.10983.0. Repairing or reset hasn't solved it 😢
claunia commented 2026-01-31 03:41:55 +00:00
Author
Owner
Copy Link

@mreduar commented on GitHub (Sep 9, 2022):

It happens every time I reboot my PC. With any font I choose I have this problem. I have to reinstall the font to get it to work. None of the above solutions or the FAQ's work. I am coming to think it is the antivirus corrupting the font, I don't know.

@mreduar commented on GitHub (Sep 9, 2022): It happens every time I reboot my PC. With any font I choose I have this problem. I have to reinstall the font to get it to work. None of the above solutions or the FAQ's work. I am coming to think it is the antivirus corrupting the font, I don't know.
claunia commented 2026-01-31 03:41:55 +00:00
Author
Owner
Copy Link

@ysertbas commented on GitHub (Jan 20, 2023):

1.15.3466.0 I still have the problem.

@ysertbas commented on GitHub (Jan 20, 2023): 1.15.3466.0 I still have the problem.
claunia commented 2026-01-31 03:41:55 +00:00
Author
Owner
Copy Link

@ysertbas commented on GitHub (Jan 20, 2023):

It happens every time I reboot my PC. With any font I choose I have this problem. I have to reinstall the font to get it to work. None of the above solutions or the FAQ's work. I am coming to think it is the antivirus corrupting the font, I don't know.

Seeing your comment I tried it a few times and yes. As soon as I reinstall the fonts, the problem is fixed, but when I reboot, it breaks again.

@ysertbas commented on GitHub (Jan 20, 2023): > It happens every time I reboot my PC. With any font I choose I have this problem. I have to reinstall the font to get it to work. None of the above solutions or the FAQ's work. I am coming to think it is the antivirus corrupting the font, I don't know. Seeing your comment I tried it a few times and yes. As soon as I reinstall the fonts, the problem is fixed, but when I reboot, it breaks again.
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 Resolution-Duplicate
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#13406
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?