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

fontFace settings reset to default after upgrading to 0.11.1072.0 #7461

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

Originally created by @jackhorton on GitHub (Apr 17, 2020).

Environment

Windows build number: 10.0.19608.0
Windows Terminal version (if applicable): 0.11.1072.0

Any other software? Lots, but nothing relevant to this issue

Steps to reproduce

I dont think its a reliable repro, but updating to 0.11.1072.0 through the Microsoft Store on my laptop this morning seems to have been what caused this. I am happy to provide logs if they exist, but I couldnt find any. After this happened, I updated on my desktop (which is on 19H2/non-insider, as opposed to my insider fast laptop) and this did not repro. However, while backing up my settings on my desktop, I noticed that the settings path did change during the upgrade - it went from profiles.json to settings.json transparently. Perhaps there was some data migration going on that was successful on my desktop but not on my laptop?

Expected behavior

fontFace setting is not reset to default

Actual behavior

fontFace setting is reset to default. I had only made two modifications to my terminal settings, and the other (the default profile guid) was unimpacted by the update.

Originally created by @jackhorton on GitHub (Apr 17, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.19608.0 Windows Terminal version (if applicable): 0.11.1072.0 Any other software? Lots, but nothing relevant to this issue ``` # Steps to reproduce I dont think its a reliable repro, but updating to 0.11.1072.0 through the Microsoft Store on my laptop this morning seems to have been what caused this. I am happy to provide logs if they exist, but I couldnt find any. After this happened, I updated on my desktop (which is on 19H2/non-insider, as opposed to my insider fast laptop) and this _did not_ repro. However, while backing up my settings on my desktop, I noticed that the settings path did change during the upgrade - it went from profiles.json to settings.json transparently. Perhaps there was some data migration going on that was successful on my desktop but not on my laptop? # Expected behavior fontFace setting is not reset to default # Actual behavior fontFace setting is reset to default. I had only made two modifications to my terminal settings, and the other (the default profile guid) was unimpacted by the update.
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 01:04:39 +00:00
claunia commented 2026-01-31 01:04:40 +00:00
Author
Owner
Copy Link

@tblut commented on GitHub (Apr 18, 2020):

I don't think resetting customizations after upgrading in a pre-release can be considered an issue. It's just what happens when using alpha/beta builds.

@tblut commented on GitHub (Apr 18, 2020): I don't think resetting customizations after upgrading in a pre-release can be considered an issue. It's just what happens when using alpha/beta builds.
claunia commented 2026-01-31 01:04:41 +00:00
Author
Owner
Copy Link

@jackhorton commented on GitHub (Apr 18, 2020):

Ah, this was likely caused by https://github.com/microsoft/terminal/pull/5190, and thus probably intentional. With that being said, I dont think its fair to say that you should expect settings to be lost in a beta build -- I am fine with losing settings, but losing them without knowing ahead of time means it might be a bug that needs fixing, hence the issue.

@jackhorton commented on GitHub (Apr 18, 2020): Ah, this was likely caused by https://github.com/microsoft/terminal/pull/5190, and thus probably intentional. With that being said, I dont think its fair to say that you should _expect_ settings to be lost in a beta build -- I am fine with losing settings, but losing them without knowing ahead of time means it might be a bug that needs fixing, hence the issue.
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 Needs-Tag-Fix 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#7461
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?