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

Updates via the Microsoft Store break Visual Studio 2022 due to font sharing #18052

New Issue
Closed
opened 2026-01-31 06:02:24 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 06:02:24 +00:00
Owner
Copy Link

Originally created by @IanKemp on GitHub (Jul 27, 2022).

Windows Terminal version

1.14.1962.0

Windows build number

10.0.19044.0

Other Software

Visual Studio 2022 17.2.6

Steps to reproduce

Whenever Windows Terminal updates via the MS Store it modifies the installed Cascadia fonts on the machine. As Visual Studio 2022 also uses these fonts, this breaks VS (all code windows render as white with no text) and VS can only be fixed by restarting the machine. This is an extremely poor developer/productivity experience.

I am not filing this as a VS bug because it is Terminal that is pulling the rug out from under VS and causing the latter to fall over. VS may need to be fixed to be more tolerant, but that is the Terminal team's conversation to have with the VS team, not mine.

Possibly related to/dupe of #10482, which was closed because... the team doesn't care about developer experience? I dunno.

Expected Behavior

VS2022 works.

Actual Behavior

VS2022 does not work.

Originally created by @IanKemp on GitHub (Jul 27, 2022). ### Windows Terminal version 1.14.1962.0 ### Windows build number 10.0.19044.0 ### Other Software Visual Studio 2022 17.2.6 ### Steps to reproduce Whenever Windows Terminal updates via the MS Store it modifies the installed Cascadia fonts on the machine. As Visual Studio 2022 also uses these fonts, this breaks VS (all code windows render as white with no text) and VS can only be fixed by restarting the machine. This is an extremely poor developer/productivity experience. I am not filing this as a VS bug because it is Terminal that is pulling the rug out from under VS and causing the latter to fall over. VS may need to be fixed to be more tolerant, but that is the Terminal team's conversation to have with the VS team, not mine. Possibly related to/dupe of #10482, which was closed because... the team doesn't care about developer experience? I dunno. ### Expected Behavior VS2022 works. ### Actual Behavior VS2022 does not work.
claunia commented 2026-01-31 06:02:26 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 27, 2022):

closed because... the team doesn't care about developer experience?

We've pursued this issue to the ends of the earth--seriously, the people who own packaged fonts are tired of hearing from us--but as it stands today we're just in a bind.

Terminal ships with Windows 11, and the inclusion of Cascadia in the package has made Cascadia a de-facto system font. If we remove the font from the package, we're risking breaking any application that has taken a dependency on it as a system font (VS, Teams comes to mind, Stack Overflow and a few other sites have also chosen to depend on it but that's neither here nor there as they're a website.) If we don't remove the font from the package, older versions of the OS have an issue with the font being locked during upgrade.

If we remove it from the package and add it as a dependency package (there's no such thing as an optional dependency, for what it's worth), we complicate distribution and OS ingestion. We've gotten enough bug reports from people who cannot find the VCLibs package that we ship as part of our own releases to know that installing dependency packages is nearly a no-go for some folks. The downstream effect is that everybody gets a deployment error because they haven't installed the font first.

I guess we could just remove it, get it into an OS update (Windows 12?), and take the heat.

Of note is that it's fixed in Windows 11, and reports like yours help us work up the organizational will to get that fix backported to Windows 10.

@DHowett commented on GitHub (Jul 27, 2022): > closed because... the team doesn't care about developer experience? We've pursued this issue to the ends of the earth--seriously, the people who own packaged fonts are tired of hearing from us--but as it stands today we're just _in a bind_. Terminal ships with Windows 11, and the inclusion of Cascadia in the package has made Cascadia a de-facto system font. If we remove the font from the package, we're risking breaking any application that has taken a dependency on it as a system font (VS, Teams comes to mind, Stack Overflow and a few other sites have also chosen to depend on it but that's neither here nor there as they're a website.) If we _don't_ remove the font from the package, older versions of the OS have an issue with the font being locked during upgrade. If we remove it from the package and add it as a dependency package (there's no such thing as an optional dependency, for what it's worth), we complicate distribution _and_ OS ingestion. We've gotten enough bug reports from people who cannot find the VCLibs package that we ship as part of our own releases to know that installing dependency packages is nearly a no-go for some folks. The downstream effect is that everybody gets a deployment error because they haven't installed the font first. I guess we could just remove it, get it into an OS update (Windows 12?), and take the heat. Of note is that it's fixed in Windows 11, and reports like yours help us work up the organizational will to get that fix backported to Windows 10.
claunia commented 2026-01-31 06:02:26 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 31, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Jul 31, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
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-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity
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#18052
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?