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

Font loading faults after Windows update KB5039212 #21872

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

Originally created by @i-e-b on GitHub (Jun 14, 2024).

Windows Terminal version

1.20.11381.0

Windows build number

10.0.22631.0

Other Software

No response

Steps to reproduce

Note: This is not the same as https://github.com/microsoft/terminal/issues/9375 , and the fix for that issue does not apply

  1. Have a custom font set as the terminal font
  2. Apply the Windows update "2024-06 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5039212)"
  3. Restart system
  4. Open the terminal app

Expected Behavior

Terminal app should open, using the previously set font

Actual Behavior

Terminal app opens with a new tab, showing this error message:
image

Any subsequent tabs opened show the same error.

However, if you open the Settings tab, subsequent tabs will open with the configured font.
This does not require any action to be taken inside the settings tab.

If the terminal app is closed and re-opened, the warning comes back.

At the same time this error started, opening "Powershell 7" as administrator no longer uses the Terminal app, but the old Windows Console instead.

Video of fault: https://youtu.be/W8RPSTKoh8Q

Custom font being used: https://github.com/i-e-b/Dave

Originally created by @i-e-b on GitHub (Jun 14, 2024). ### Windows Terminal version 1.20.11381.0 ### Windows build number 10.0.22631.0 ### Other Software _No response_ ### Steps to reproduce Note: This is not the same as https://github.com/microsoft/terminal/issues/9375 , and the fix for that issue does not apply 1. Have a custom font set as the terminal font 2. Apply the Windows update "2024-06 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5039212)" 3. Restart system 4. Open the terminal app ### Expected Behavior Terminal app should open, using the previously set font ### Actual Behavior Terminal app opens with a new tab, showing this error message: ![image](https://github.com/microsoft/terminal/assets/576220/670fe7e7-334a-4fb8-8cd7-9f34963ee18c) Any subsequent tabs opened show the same error. **However**, if you open the `Settings` tab, subsequent tabs will open with the configured font. This does not require any action to be taken inside the settings tab. If the terminal app is closed and re-opened, the warning comes back. At the same time this error started, opening "Powershell 7" as administrator no longer uses the Terminal app, but the old Windows Console instead. Video of fault: https://youtu.be/W8RPSTKoh8Q Custom font being used: https://github.com/i-e-b/Dave
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 07:57:04 +00:00
claunia commented 2026-01-31 07:57:05 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jun 14, 2024):

Note: This is not the same as https://github.com/microsoft/terminal/issues/9375 , and the fix for that issue does not apply

For my understanding: You did install the font for all users and, if you previously installed for your user only, you made sure to remove it from AppData again, right?

@lhecker commented on GitHub (Jun 14, 2024): > Note: This is not the same as https://github.com/microsoft/terminal/issues/9375 , and the fix for that issue does not apply For my understanding: You _did_ install the font for all users and, if you previously installed for your user only, you made sure to remove it from AppData again, right?
claunia commented 2026-01-31 07:57:05 +00:00
Author
Owner
Copy Link

@i-e-b commented on GitHub (Jun 14, 2024):

Hi.

Yes, the font is installed for all users. It is not installed in AppData, only in C:\Windows\Fonts.

I have also tried multiple reboots, and have run "Repair" for the Terminal app in Settings.

@i-e-b commented on GitHub (Jun 14, 2024): Hi. Yes, the font is installed for all users. It is not installed in `AppData`, only in `C:\Windows\Fonts`. I have also tried multiple reboots, and have run "Repair" for the Terminal app in Settings.
claunia commented 2026-01-31 07:57:05 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jun 14, 2024):

Did you already try to remove the font and reinstall it? If not, I'd check both the old control panel

image

as well as the new one

image

If you already tried this, please let me know. 🙂

@lhecker commented on GitHub (Jun 14, 2024): Did you already try to remove the font and reinstall it? If not, I'd check both the old control panel ![image](https://github.com/microsoft/terminal/assets/2256941/b2e38b4c-222c-418f-b46e-28fcc8566b2c) as well as the new one ![image](https://github.com/microsoft/terminal/assets/2256941/6ac7fa15-2526-49cb-a556-8b14182bf398) If you already tried this, please let me know. 🙂
claunia commented 2026-01-31 07:57:05 +00:00
Author
Owner
Copy Link

@i-e-b commented on GitHub (Jun 17, 2024):

Hi.

So, the font was showing in the old control panel, but not in Windows->Settings->Personalisation->Fonts.
I deleted via the old control panel, and re-installed via settings.

The font is now loaded at the start up of Terminal, as expected.

I guess there are multiple ways of enumerating the fonts, and something got damaged during the update? This would make sense if the start-up process was checking in a different way to the Terminal->Settings tab.

@i-e-b commented on GitHub (Jun 17, 2024): Hi. So, the font was showing in the old control panel, but not in Windows->Settings->Personalisation->Fonts. I deleted via the old control panel, and re-installed via settings. The font is now loaded at the start up of Terminal, as expected. I guess there are multiple ways of enumerating the fonts, and something got damaged during the update? This would make sense if the start-up process was checking in a different way to the Terminal->Settings tab.
claunia commented 2026-01-31 07:57:06 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jun 17, 2024):

So, the font was showing in the old control panel, but not in Windows->Settings->Personalisation->Fonts.

I have encountered broken font caches before, but definitely not like that. Hopefully this isn't a common bug.

The font is now loaded at the start up of Terminal, as expected.

I'm glad to hear that this fixed the problem! I'll close this issue for now and hope that this is just a rare bug in Windows. This is because...

I guess there are multiple ways of enumerating the fonts, and something got damaged during the update? This would make sense if the start-up process was checking in a different way to the Terminal->Settings tab.

...your assumption is sort of correct. We have a number of problems with the font caching service on Windows and we're tracking the worst one in issue #3257: Per-user fonts simply don't work. That's internally tracked as MSFT:42103854. Font support is definitely more robust for unpackaged applications unfortunately.

@lhecker commented on GitHub (Jun 17, 2024): > So, the font was showing in the old control panel, but not in Windows->Settings->Personalisation->Fonts. I have encountered broken font caches before, but definitely not like that. Hopefully this isn't a common bug. > The font is now loaded at the start up of Terminal, as expected. I'm glad to hear that this fixed the problem! I'll close this issue for now and hope that this is just a rare bug in Windows. This is because... > I guess there are multiple ways of enumerating the fonts, and something got damaged during the update? This would make sense if the start-up process was checking in a different way to the Terminal->Settings tab. ...your assumption is sort of correct. We have a number of problems with the font caching service on Windows and we're tracking the worst one in issue #3257: Per-user fonts simply don't work. That's internally tracked as MSFT:42103854. Font support is definitely more robust for unpackaged applications unfortunately.
claunia commented 2026-01-31 07:57:06 +00:00
Author
Owner
Copy Link

@i-e-b commented on GitHub (Jun 29, 2024):

This fault has re-occurred
image

Looks like it might be a bug in Windows -- I have made no font changes, but my chosen font was lost from the 'new style' Windows Settings, but was present in the 'old style' Fonts.

Re-installing in the Settings app triggered the 'This font is already installed' warning from the old side, but then the Console issue stopped.

@i-e-b commented on GitHub (Jun 29, 2024): This fault has re-occurred ![image](https://github.com/microsoft/terminal/assets/576220/11d14166-4360-41ac-b807-69bea25610ae) Looks like it might be a bug in Windows -- I have made no font changes, but my chosen font was lost from the 'new style' Windows Settings, but was present in the 'old style' Fonts. Re-installing in the Settings app triggered the 'This font is already installed' warning from the old side, but then the Console issue stopped.
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#21872
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?