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

Cascadia Mono Font not found: Release fix to stable #17218

New Issue
Closed
opened 2026-01-31 05:35:48 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 05:35:48 +00:00
Owner
Copy Link

Originally created by @maxgerhardt on GitHub (Apr 10, 2022).

Windows Terminal version

1.12.10732.0

Windows build number

10.0.19044.1586

Other Software

No response

Steps to reproduce

Start the terminal.

Expected Behavior

No error messages, font works fine.

Actual Behavior

Error message

grafik

"Warning: The selected font "Cascadia Mono" was not found.
"Consolas" was selected instead
Install missing fonts or choose a different one.

Most suspiciously, looking in the Microsoft Windows Store, it shows that an update has been executed just today, so it heavily suggests that an update broke it.

grafik

https://github.com/microsoft/terminal/issues/12420#issuecomment-1079498501 says this was fixed in the release version more than 2 weeks ago, can this land in the stable release?

Originally created by @maxgerhardt on GitHub (Apr 10, 2022). ### Windows Terminal version 1.12.10732.0 ### Windows build number 10.0.19044.1586 ### Other Software _No response_ ### Steps to reproduce Start the terminal. ### Expected Behavior No error messages, font works fine. ### Actual Behavior Error message ![grafik](https://user-images.githubusercontent.com/26485477/162626091-9cc66dfe-e2fa-4993-b483-298c97c640e3.png) >"Warning: The selected font "Cascadia Mono" was not found. > "Consolas" was selected instead > Install missing fonts or choose a different one. Most suspiciously, looking in the Microsoft Windows Store, it shows that an update has been executed *just today*, so it heavily suggests that an update broke it. ![grafik](https://user-images.githubusercontent.com/26485477/162626137-90b61c79-0f98-49dc-86d8-5047585541e7.png) https://github.com/microsoft/terminal/issues/12420#issuecomment-1079498501 says this was fixed in the release version more than 2 weeks ago, can this land in the stable release?
claunia added the Issue-QuestionNeeds-TriageNeeds-Tag-FixResolution-Answered labels 2026-01-31 05:35:48 +00:00
claunia commented 2026-01-31 05:35:49 +00:00
Author
Owner
Copy Link

@csi-lund commented on GitHub (Apr 11, 2022):

Interesting that seems to affect VS as well
image

restarting doesnt fix.

@csi-lund commented on GitHub (Apr 11, 2022): Interesting that seems to affect VS as well ![image](https://user-images.githubusercontent.com/1974225/162687506-2d5a574d-e076-49f3-9675-8dada0873006.png) restarting doesnt fix.
claunia commented 2026-01-31 05:35:50 +00:00
Author
Owner
Copy Link

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

The terminal in the preview version works for me (https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-13-release/) and when you look on disk where the preview terminal is there is also that font file. Maybe just installing the preview version fixes VisualStudio too?

@maxgerhardt commented on GitHub (Apr 11, 2022): The terminal in the preview version works for me (https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-13-release/) and when you look on disk where the preview terminal is there is also that font file. Maybe just installing the preview version fixes VisualStudio too?
claunia commented 2026-01-31 05:35:50 +00:00
Author
Owner
Copy Link

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

it shows that an update has been executed just today, so it heavily suggests that an update broke it.

Alas, that's actually how this issue occurs. Something about the update process leaves the font file locked in a way such that we can't read the file any longer.

As mentioned, this is already fixed in Preview, hopefully. I think we're gonna let this one bake there for a little while to make sure it A. actually worked and B. doesn't make things worse somehow.

... Though, looking at #12554, I think we ended up servicing that to a 1.12 version, but I'm not sure which. @DHowett we may want to push the latest 1.12 release actually to GH.

@zadjii-msft commented on GitHub (Apr 11, 2022): > it shows that an update has been executed _just today_, so it heavily suggests that an update broke it. Alas, that's actually how this issue occurs. Something about the update process leaves the font file locked in a way such that we can't read the file any longer. As mentioned, this is already fixed in Preview, _hopefully_. I think we're gonna let this one bake there for a little while to make sure it A. actually worked and B. doesn't make things worse somehow. ... Though, looking at #12554, I think we ended up servicing that to a 1.12 version, but I'm not sure which. @DHowett we may want to push the latest 1.12 release actually to GH.
claunia commented 2026-01-31 05:35:50 +00:00
Author
Owner
Copy Link

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

This issue is reproducible in Preview 1.13.10983.0 for me.

@srdjanjovcic commented on GitHub (Apr 13, 2022): This issue is reproducible in Preview 1.13.10983.0 for me.
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-Question Needs-Tag-Fix Needs-Triage Resolution-Answered
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#17218
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?