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 font family prevents Terminal from updating properly #22341

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

Originally created by @l-l-l-l-l-l on GitHub (Oct 3, 2024).

Windows Terminal version

1.21.2701.0

Windows build number

10.0.22631.0

Other Software

No response

Steps to reproduce

Use winget update or winget upgrade to update Terminal to the latest version (case 1).
Otherwise, either use Microsoft Store update function to do the same (case 2) or download the MSIX package and install it (case 3).

Expected Behavior

For case 1, the program should be updated.
For case 2, given a completely different, yet to be determined cause, I need to then manually register the newly downloaded folder after it fails the last step, then complete the task with Microsoft Store to update its app version database, after which the old version folders get erased.
For case 3, most likely for the same reason, I have to use add-appxpackage from a command line application instead of just double-clicking and installeng, after which the old version folders get erased.

Actual Behavior

For this app in particular, case 1 returns an error and does nothing bt add an almost empty folder with a different version numbering scheme (same version as the new one, but preceded by a 300 and replacing the "x64" by a "neutral"), which does nothing except preventing case 2 from even noticing the app isn't up to date, while cases 2 and 3 leave a trail of old version folders.

Checking those leftover folders, the reason they can't be erased is that CascadiaMono.ttf and CascadiaMonoItalic.ttf claim to be in use by SYSTEM (something the Resource Monitor cannot confirm) for all versions at the same time. Sometimes (it has happened to me once, seemingly after an attempt to get rid of the folder with a remove-appxpackage), a bunch of dlls plus OpenConsole.exe, WindowsTeminal.exe and Microsoft.Terminal.Remoting.winmd get readded to the folder, but those can be erased no issue.

I find it weird that everyone has issues with Cascadia not being found while my issue is that my System is hogging every single Cascadia font file in existence.

Originally created by @l-l-l-l-l-l on GitHub (Oct 3, 2024). ### Windows Terminal version 1.21.2701.0 ### Windows build number 10.0.22631.0 ### Other Software _No response_ ### Steps to reproduce Use winget update or winget upgrade to update Terminal to the latest version (case 1). Otherwise, either use Microsoft Store update function to do the same (case 2) or download the MSIX package and install it (case 3). ### Expected Behavior For case 1, the program should be updated. For case 2, given a completely different, yet to be determined cause, I need to then manually register the newly downloaded folder after it fails the last step, then complete the task with Microsoft Store to update its app version database, after which the old version folders get erased. For case 3, most likely for the same reason, I have to use add-appxpackage from a command line application instead of just double-clicking and installeng, after which the old version folders get erased. ### Actual Behavior For this app in particular, case 1 returns an error and does nothing bt add an almost empty folder with a different version numbering scheme (same version as the new one, but preceded by a 300 and replacing the "x64" by a "neutral"), which does nothing except preventing case 2 from even noticing the app isn't up to date, while cases 2 and 3 leave a trail of old version folders. Checking those leftover folders, the reason they can't be erased is that CascadiaMono.ttf and CascadiaMonoItalic.ttf claim to be in use by SYSTEM (something the Resource Monitor cannot confirm) for all versions at the same time. Sometimes (it has happened to me once, seemingly after an attempt to get rid of the folder with a remove-appxpackage), a bunch of dlls plus OpenConsole.exe, WindowsTeminal.exe and Microsoft.Terminal.Remoting.winmd get readded to the folder, but those can be erased no issue. I find it weird that everyone has issues with Cascadia not being found while my issue is that my System is hogging every single Cascadia font file in existence.
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:10:19 +00:00
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-Triage
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#22341
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?