starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 07:54:35 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Add support for fonts installed at the user level #23100

New Issue
Closed
opened 2026-01-31 08:32:24 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 08:32:24 +00:00
Owner
Copy Link

Originally created by @tylerlowrey on GitHub (Mar 31, 2025).

Description of the new feature

Currently, the only supported fonts are those that are installed for all users in C:\Windows\Fonts

It would be nice to be able to use a user level font that lives in %localappdata%\Microsoft\Windows\Fonts

This is useful for users that do not have admin access and may not be able to easily get a font installed into C:\Windows\Fonts (Or whose company\organization may not allow installing new fonts to this location)

Proposed technical implementation details

No response

Originally created by @tylerlowrey on GitHub (Mar 31, 2025). ### Description of the new feature Currently, the only supported fonts are those that are installed for all users in `C:\Windows\Fonts` It would be nice to be able to use a user level font that lives in `%localappdata%\Microsoft\Windows\Fonts` This is useful for users that do not have admin access and may not be able to easily get a font installed into `C:\Windows\Fonts` (Or whose company\organization may not allow installing new fonts to this location) ### Proposed technical implementation details _No response_
claunia added the Issue-FeatureNeeds-Tag-Fix labels 2026-01-31 08:32:24 +00:00
claunia commented 2026-01-31 08:32:25 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 31, 2025):

Hey there!

Terminal already supports per-user fonts, as they're offered through the standard Windows Font APIs.

If you are not seeing fonts you've installed to the user folder your IT administrator may have disabled the usermode font cache service (which is tangentially related) or you're encountering a known issue where if Terminal starts too early in login the OS will never report that user-installed fonts exist.

If you have access to Terminal's installation directory--by using the portable or unpackaged builds--you can also place font files (only *.ttf) in the root of the package folder and refer to them by font name.

@DHowett commented on GitHub (Mar 31, 2025): Hey there! Terminal already supports per-user fonts, as they're offered through the standard Windows Font APIs. If you are not seeing fonts you've installed to the user folder your IT administrator may have disabled the usermode font cache service (which is tangentially related) or you're encountering a known issue where if Terminal starts too early in login the OS will never report that user-installed fonts exist. If you have access to Terminal's installation directory--by using the portable or unpackaged builds--you can also place font files (only `*.ttf`) in the root of the package folder and refer to them by font name.
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-Feature Needs-Tag-Fix
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#23100
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?