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

Profiles missing after resetting config #15054

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

Originally created by @ktremain on GitHub (Sep 2, 2021).

Originally assigned to: @zadjii-msft on GitHub.

Windows Terminal version (or Windows build number)

1.10.2383.0

Other Software

No response

Steps to reproduce

  1. have terminal ver 1.9 with default profiles including powershell/WSL/Azure shell
  2. upgrade to v1.10
  3. open settings.json
  4. delete contents of file and save
  5. reload terminal

as per notes at top of config file, i wanted to ensure that i had any new defaults now that v1.10 has been released
"..It should still be usable in newer versions, but newer versions might have additional
settings, help text, or changes that you will not see unless you clear this file
and let us generate a new one for you."

Expected Behavior

expected that all default profiles get regenerated

Actual Behavior

only "windows powershell" and "Command prompt" appear.

Also note that terminal did infact launch "powershell" (v7.1.4) and had an empty dropdown in the "default profile" box in settings as what was launched did not have any profile.

I had to reset the app to restore all my profiles

Originally created by @ktremain on GitHub (Sep 2, 2021). Originally assigned to: @zadjii-msft on GitHub. ### Windows Terminal version (or Windows build number) 1.10.2383.0 ### Other Software _No response_ ### Steps to reproduce 1. have terminal ver 1.9 with default profiles including powershell/WSL/Azure shell 2. upgrade to v1.10 3. open settings.json 4. delete contents of file and save 5. reload terminal as per notes at top of config file, i wanted to ensure that i had any new defaults now that v1.10 has been released "..It should still be usable in newer versions, but newer versions might have additional settings, help text, or changes that you will not see unless you clear this file and let us generate a new one for you." ### Expected Behavior expected that all default profiles get regenerated ### Actual Behavior only "windows powershell" and "Command prompt" appear. Also note that terminal did infact launch "powershell" (v7.1.4) and had an empty dropdown in the "default profile" box in settings as what was launched did not have any profile. I had to reset the app to restore all my profiles
claunia commented 2026-01-31 04:27:07 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 2, 2021):

HMMMMMM This is a good point. In 1.11 (and backported to 1.10), we added the ability to just delete dynamic profiles from the settings, and have them not auto-regenerate. But if you totally blow away the settings file, that's kinda a different case now.

@DHowett @lhecker for discussion: if settings.json is totally empty, or missing, should we clear out state.json too? Or is that just a bad heuristic? Is there a reason we would want to keep state.json even if they blow away their settings?

@zadjii-msft commented on GitHub (Sep 2, 2021): HMMMMMM This is a good point. In 1.11 (and backported to 1.10), we added the ability to just delete dynamic profiles from the settings, and have them not auto-regenerate. But if you totally blow away the settings file, that's kinda a different case now. @DHowett @lhecker for discussion: if `settings.json` is _totally empty_, or missing, should we clear out `state.json` too? Or is that just a bad heuristic? Is there a reason we would want to keep `state.json` even if they blow away their settings?
claunia commented 2026-01-31 04:27:07 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Sep 2, 2021):

@DHowett @lhecker for discussion: if settings.json is totally empty, or missing, should we clear out state.json too?

Sounds good to me actually.

@lhecker commented on GitHub (Sep 2, 2021): > @DHowett @lhecker for discussion: if settings.json is totally empty, or missing, should we clear out state.json too? Sounds good to me actually.
claunia commented 2026-01-31 04:27:07 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Oct 6, 2021):

@zadjii-msft Is there anything left to do here after merging that docs change?

@carlos-zamora commented on GitHub (Oct 6, 2021): @zadjii-msft Is there anything left to do here after merging that docs change?
claunia commented 2026-01-31 04:27:07 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 6, 2021):

Oh we were going to change the Terminal so that when we encounter a missing or empty settings.json, we'll also make sure to manually clear out state.json. That way any state from the previous settings instance isn't used accidentally.

@zadjii-msft commented on GitHub (Oct 6, 2021): Oh we were going to change the Terminal so that when we encounter a missing or empty `settings.json`, we'll also make sure to manually clear out `state.json`. That way any state from the previous settings instance isn't used accidentally.
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 Area-Settings Issue-Bug Needs-Triage Product-Terminal Resolution-Fix-Committed
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#15054
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?