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

Terminal loses custom font after PC restart #18886

New Issue
Closed
opened 2026-01-31 06:27:14 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 06:27:14 +00:00
Owner
Copy Link

Originally created by @onsamyj on GitHub (Nov 13, 2022).

Windows Terminal version

7.3.0

Windows build number

22000.1219

Other Software

No response

Steps to reproduce

Install custom font (typeface), for example "SauceCodePro Nerd Font Mono" (for use with Oh My Posh).
Set it as default in Terminal settings.
Everything works fine.

Restart the PC.
Terminal throws up an error message:

Warning
Unable to find the selected font "SauceCodePro Nerd Font Mono".
"Consolas" has been selected instead.
Please either install the missing font or choose another one.

Reinstall the font, everything works fine until the next reboot.

Same bug on two 22H1 laptops. Not sure if it is specifically a Terminal problem, but other apps, like WordPad, see the font fine. It was also fine in 21H2.

Expected Behavior

Custom font is working after reboot.

Actual Behavior

Error message.

Originally created by @onsamyj on GitHub (Nov 13, 2022). ### Windows Terminal version 7.3.0 ### Windows build number 22000.1219 ### Other Software _No response_ ### Steps to reproduce Install custom font (typeface), for example "SauceCodePro Nerd Font Mono" (for use with Oh My Posh). Set it as default in Terminal settings. Everything works fine. Restart the PC. Terminal throws up an error message: > Warning > Unable to find the selected font "SauceCodePro Nerd Font Mono". > "Consolas" has been selected instead. > Please either install the missing font or choose another one. Reinstall the font, everything works fine until the next reboot. Same bug on two 22H1 laptops. Not sure if it is specifically a Terminal problem, but other apps, like WordPad, see the font fine. It was also fine in 21H2. ### Expected Behavior Custom font is working after reboot. ### Actual Behavior Error message.
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 06:27:14 +00:00
claunia commented 2026-01-31 06:27:16 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 13, 2022):

Did you install the font for all users?

<aside for the team>: Is there any way for us to detect if a font is only installed for the current user when the user picks it? So we can flash a InfoBar or something at them? Or at the very least, we need to update the help text for that warning, because we've gotten like five of these bugs reports in the last week.

@zadjii-msft commented on GitHub (Nov 13, 2022): Did you install the font for all users? \<aside for the team>: Is there any way for us to detect if a font is only installed for the current user when the user picks it? So we can flash a InfoBar or something at them? Or at the very least, we need to update the help text for that warning, because we've gotten like five of these bugs reports in the last week.
claunia commented 2026-01-31 06:27:16 +00:00
Author
Owner
Copy Link

@onsamyj commented on GitHub (Nov 13, 2022):

Installing for all users fixed it. Thanks.

Behavior changed between 21H2 and 22H2? Then yes, you need a warning of some kind.

@onsamyj commented on GitHub (Nov 13, 2022): Installing for all users fixed it. Thanks. Behavior changed between 21H2 and 22H2? Then yes, you need a warning of some kind.
claunia commented 2026-01-31 06:27:16 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 13, 2022):

Behavior changed between 21H2 and 22H2?

By all accounts, it shouldn't have. We'll have to go darken some doorways and find out what happened.

@zadjii-msft commented on GitHub (Nov 13, 2022): > Behavior changed between 21H2 and 22H2? By all accounts, it _shouldn't have_. We'll have to go darken some doorways and find out what happened.
claunia commented 2026-01-31 06:27:16 +00:00
Author
Owner
Copy Link

@onsamyj commented on GitHub (Nov 13, 2022):

Hm. Not sure that I can be of a help with that, but to be clear:
On 21H1 installing font for a user works fine, even after reboot.
On 22H2 installing font for a user also works, but only until reboot.
Installing font for all users works fine for both 21H1 and 22H1.

@onsamyj commented on GitHub (Nov 13, 2022): Hm. Not sure that I can be of a help with that, but to be clear: On 21H1 installing font for _a user_ works fine, even after reboot. On 22H2 installing font for _a user_ also works, but only until reboot. Installing font for _all users_ works fine for both 21H1 and 22H1.
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#18886
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?