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

Cascadia Mono font not found #20572

New Issue
Closed
opened 2026-01-31 07:18:00 +00:00 by claunia · 10 comments
claunia commented 2026-01-31 07:18:00 +00:00
Owner
Copy Link

Originally created by @HunterZ on GitHub (Sep 29, 2023).

Windows Terminal version

1.18.2681.0

Windows build number

10.0.22621.2283

Other Software

winget v1.6.2701

Steps to reproduce

Install an older version of Terminal. Upgrade to 1.18.2681.0 using winget.

Expected Behavior

Upgrade succeeds.

Actual Behavior

Terminal says it can't find a font named Cascadia Mono, and falls back to Consolas

Originally created by @HunterZ on GitHub (Sep 29, 2023). ### Windows Terminal version 1.18.2681.0 ### Windows build number 10.0.22621.2283 ### Other Software winget v1.6.2701 ### Steps to reproduce Install an older version of Terminal. Upgrade to 1.18.2681.0 using winget. ### Expected Behavior Upgrade succeeds. ### Actual Behavior Terminal says it can't find a font named Cascadia Mono, and falls back to Consolas
claunia added the Issue-BugIn-PRNeeds-Tag-FixProduct-TerminalArea-Fonts labels 2026-01-31 07:18:01 +00:00
claunia commented 2026-01-31 07:18:03 +00:00
Author
Owner
Copy Link

@HunterZ commented on GitHub (Sep 29, 2023):

I know this has been reported a million times, but it just happened to me and all of the previous issues on it seem to be closed, so I've written this to capture the fact that it clearly isn't resolved.

I do not see Cascadia Mono in the Windows Fonts UI or in C:\Windows\Fonts or in %localappdata%\Microsoft\Windows\Fonts, so something either uninstalled it, or it is not included in Windows 11 Home.

I tried doing a Repair, but it didn't accomplish anything.

Edit: Seems like someone should make a Cascadia Mono winget package and make Windows Terminal's package depend on it. Ironically, Chocolatey has a Cascadia Code package that probably includes this font.

Edit 2: Downloading the font from https://github.com/microsoft/cascadia-code and installing it manually for all users, then resetting Terminal works, but it seems like Terminal shouldn't depend on the user to do this.

@HunterZ commented on GitHub (Sep 29, 2023): I know this has been reported a million times, but it just happened to me and all of the previous issues on it seem to be closed, so I've written this to capture the fact that it clearly isn't resolved. I do not see Cascadia Mono in the Windows Fonts UI or in C:\Windows\Fonts or in %localappdata%\Microsoft\Windows\Fonts, so something either uninstalled it, or it is not included in Windows 11 Home. I tried doing a Repair, but it didn't accomplish anything. Edit: Seems like someone should make a Cascadia Mono winget package and make Windows Terminal's package depend on it. Ironically, Chocolatey has a Cascadia Code package that probably includes this font. Edit 2: Downloading the font from https://github.com/microsoft/cascadia-code and installing it manually for all users, then resetting Terminal works, but it seems like Terminal shouldn't depend on the user to do this.
claunia commented 2026-01-31 07:18:03 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 4, 2023):

This is wacky and very unexpected. The other issues are all closed, because we thought we fixed this a few releases ago. We added a final fallback to try and load the font directly from a file in our package (not from the font cache).

What rendering engine are you using (could you share your settings.json file)? (we're pretty sure the rendering engine shouldn't matter here.)

Our only theory right now is that the way we detect a failure to load the font might not be working anymore?

23d45a7e3a was the last touch here, which only shipped in 1.18 preview. That we might need to revert 😞

@zadjii-msft commented on GitHub (Oct 4, 2023): This is wacky and very unexpected. The other issues are all closed, because we _thought_ we fixed this a few releases ago. We added a final fallback to try and load the font directly from a file in our package (not from the font cache). What rendering engine are you using (could you share your [settings.json file](https://github.com/microsoft/terminal/wiki/Frequently-Asked-Questions-(FAQ)#where-can-i-find-the-settings-file))? (we're pretty sure the rendering engine _shouldn't_ matter here.) Our only theory right now is that the way we detect a failure to load the font might not be working anymore? 23d45a7e3a286f37924fd68d222168fce631282d was the last touch here, which only shipped in 1.18 preview. That we _might_ need to revert 😞
claunia commented 2026-01-31 07:18:03 +00:00
Author
Owner
Copy Link

@duckinator commented on GitHub (Oct 11, 2023):

I just encountered this after upgrading using winget.

  • Windows Terminal version (after upgrading): 1.18.2822.0
  • Windows build number: 10.0.19045.0
  • winget version: v1.6.2771
@duckinator commented on GitHub (Oct 11, 2023): I just encountered this after upgrading using winget. * Windows Terminal version (after upgrading): 1.18.2822.0 * Windows build number: 10.0.19045.0 * winget version: v1.6.2771
claunia commented 2026-01-31 07:18:04 +00:00
Author
Owner
Copy Link

@vpal12 commented on GitHub (Oct 14, 2023):

yes

@vpal12 commented on GitHub (Oct 14, 2023): yes
claunia commented 2026-01-31 07:18:04 +00:00
Author
Owner
Copy Link

@HunterZ commented on GitHub (Oct 14, 2023):

This is wacky and very unexpected. The other issues are all closed, because we thought we fixed this a few releases ago. We added a final fallback to try and load the font directly from a file in our package (not from the font cache).

What rendering engine are you using (could you share your settings.json file)? (we're pretty sure the rendering engine shouldn't matter here.)

Here it is: settings.json

Reminder that Cascadia Mono did not seem to be installed in Windows 11 for some reason (which is weird because I was using an old version of Terminal without having ever seen that error), so it seems to be Terminal depending on something which isn't guaranteed to be present?

@HunterZ commented on GitHub (Oct 14, 2023): > This is wacky and very unexpected. The other issues are all closed, because we _thought_ we fixed this a few releases ago. We added a final fallback to try and load the font directly from a file in our package (not from the font cache). > > What rendering engine are you using (could you share your [settings.json file](https://github.com/microsoft/terminal/wiki/Frequently-Asked-Questions-(FAQ)#where-can-i-find-the-settings-file))? (we're pretty sure the rendering engine _shouldn't_ matter here.) Here it is: [settings.json](https://github.com/microsoft/terminal/files/12907483/settings.json) Reminder that Cascadia Mono did not seem to be installed in Windows 11 for some reason (which is weird because I was using an old version of Terminal without having ever seen that error), so it seems to be Terminal depending on something which isn't guaranteed to be present?
claunia commented 2026-01-31 07:18:04 +00:00
Author
Owner
Copy Link

@duckinator commented on GitHub (Oct 15, 2023):

Here's my settings.json, too.

I've not reconfigured anything related to rendering engines, fonts, or anything like that.

@duckinator commented on GitHub (Oct 15, 2023): Here's my [settings.json](https://github.com/microsoft/terminal/files/12908917/settings.json), too. I've not reconfigured anything related to rendering engines, fonts, or anything like that.
claunia commented 2026-01-31 07:18:05 +00:00
Author
Owner
Copy Link

@duckinator commented on GitHub (Oct 15, 2023):

The plot thickens: I have C:\Windows\Fonts\CascadiaMono.ttf, and I was also able to use the Cascadia Mono font in Notepad without issue.

image

image

@duckinator commented on GitHub (Oct 15, 2023): The plot thickens: I have `C:\Windows\Fonts\CascadiaMono.ttf`, and I was also able to use the Cascadia Mono font in Notepad without issue. ![image](https://github.com/microsoft/terminal/assets/39698/073f6820-92ff-4143-b2b7-6a1a069998dc) ![image](https://github.com/microsoft/terminal/assets/39698/abcb4f43-c6f0-40b3-a847-77667aa80016)
claunia commented 2026-01-31 07:18:05 +00:00
Author
Owner
Copy Link

@RedTail72 commented on GitHub (Oct 23, 2023):

I'm not sure if this is what #16196 is addressing, but I decided to run Process Monitor while starting up Terminal and saw it was trying to load C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.17.11461.0_x64__8wekyb3d8bbwe\CascadiaMono.ttf, but I'm currently running v1.18.2822.0. Just thought I'd share incase the PR doesn't address this.

image
image

@RedTail72 commented on GitHub (Oct 23, 2023): I'm not sure if this is what #16196 is addressing, but I decided to run Process Monitor while starting up Terminal and saw it was trying to load `C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.17.11461.0_x64__8wekyb3d8bbwe\CascadiaMono.ttf`, but I'm currently running v1.18.2822.0. Just thought I'd share incase the PR doesn't address this. ![image](https://github.com/microsoft/terminal/assets/15264370/5aa65165-d450-484d-89f6-f2c7fca56605) ![image](https://github.com/microsoft/terminal/assets/15264370/66dcbcd9-d712-4672-baf8-53db6f3e89e5)
claunia commented 2026-01-31 07:18:05 +00:00
Author
Owner
Copy Link

@RedTail72 commented on GitHub (Oct 23, 2023):

I'm not sure if this is what #16196 is addressing, but I decided to run Process Monitor while starting up Terminal and saw it was trying to load C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.17.11461.0_x64__8wekyb3d8bbwe\CascadiaMono.ttf, but I'm currently running v1.18.2822.0. Just thought I'd share incase the PR doesn't address this.

I should have waited to post until I did this, but after restarting my machine, I am no longer having issues with the Cascadia Mono font not found message. My font is still set to Cascadia Mono, just no more error messages.

@RedTail72 commented on GitHub (Oct 23, 2023): > I'm not sure if this is what #16196 is addressing, but I decided to run Process Monitor while starting up Terminal and saw it was trying to load `C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.17.11461.0_x64__8wekyb3d8bbwe\CascadiaMono.ttf`, but I'm currently running v1.18.2822.0. Just thought I'd share incase the PR doesn't address this. > > I should have waited to post until I did this, but after restarting my machine, I am no longer having issues with the _Cascadia Mono font not found_ message. My font is still set to Cascadia Mono, just no more error messages.
claunia commented 2026-01-31 07:18:05 +00:00
Author
Owner
Copy Link

@eduarddejong commented on GitHub (Oct 28, 2023):

I'm not sure if this is what #16196 is addressing, but I decided to run Process Monitor while starting up Terminal and saw it was trying to load C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.17.11461.0_x64__8wekyb3d8bbwe\CascadiaMono.ttf, but I'm currently running v1.18.2822.0. Just thought I'd share incase the PR doesn't address this.

I should have waited to post until I did this, but after restarting my machine, I am no longer having issues with the Cascadia Mono font not found message. My font is still set to Cascadia Mono, just no more error messages.

I can confirm your experience. I haven't booted this Windows system frequently the last days. So my system started updating several "things".
After a while I opened the Terminal and god this strange error message. So I checked Github here.

Before rebooting, I could enter the exact directory that you mention in my Explorer. The font files where vissible there, but not possible to open at all.
Double click failed.
But also trying to open it with Notepad failed, which I often do to see what happens. It gave me a permissions related error.

After rebooting, this entire directory path did not exist anymore, but the Terminal was working fine again and the font just loads without any issues.

So my conclusion is that the Terminal still tried to load the font from an old directory that was being uninstalled by the update. But somehow that process was not fully complete until reboot (the Store showed that the update was completed a couple of minutes ago though).

Which may not be strange at all though, but it's not what you expect from an App Store based app in general.

So it seems that some kind of proper warning system warning the user that he really needs to reboot is missing here.

@eduarddejong commented on GitHub (Oct 28, 2023): > > I'm not sure if this is what #16196 is addressing, but I decided to run Process Monitor while starting up Terminal and saw it was trying to load `C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.17.11461.0_x64__8wekyb3d8bbwe\CascadiaMono.ttf`, but I'm currently running v1.18.2822.0. Just thought I'd share incase the PR doesn't address this. > > I should have waited to post until I did this, but after restarting my machine, I am no longer having issues with the _Cascadia Mono font not found_ message. My font is still set to Cascadia Mono, just no more error messages. I can confirm your experience. I haven't booted this Windows system frequently the last days. So my system started updating several "things". After a while I opened the Terminal and god this strange error message. So I checked Github here. Before rebooting, I could enter the exact directory that you mention in my Explorer. The font files where vissible there, but not possible to open at all. Double click failed. But also trying to open it with Notepad failed, which I often do to see what happens. It gave me a permissions related error. After rebooting, this entire directory path did not exist anymore, but the Terminal was working fine again and the font just loads without any issues. So my conclusion is that the Terminal still tried to load the font from an old directory that was being uninstalled by the update. But somehow that process was not fully complete until reboot (the Store showed that the update was completed a couple of minutes ago though). Which may not be strange at all though, but it's not what you expect from an App Store based app in general. So it seems that some kind of proper warning system warning the user that he really needs to reboot is missing here.
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 Area-Fonts In-PR Issue-Bug Needs-Tag-Fix Product-Terminal
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#20572
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?