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

Menu option 'Defaults' does not restore terminal properties to factory settings in non-legacy mode #4799

New Issue
Closed
opened 2026-01-30 23:56:52 +00:00 by claunia · 1 comment
claunia commented 2026-01-30 23:56:52 +00:00
Owner
Copy Link

Originally created by @wpqs on GitHub (Nov 4, 2019).

Environment

Microsoft Windows [Version 10.0.18362.418]

Steps to reproduce

  1. Open Command Prompt - i.e. run cmd
  2. Open properties dialog and ensure 'Use Legacy Console' is unchecked, then close dialog
  3. Select menu option 'defaults'

Expected behavior

The terminal properties should be set to their factory defaults.

Actual behavior

Property window opens and properties have not been changed. What are the factory defaults? Who knows?

Originally created by @wpqs on GitHub (Nov 4, 2019). # Environment Microsoft Windows [Version 10.0.18362.418] # Steps to reproduce 1. Open Command Prompt - i.e. run cmd 2. Open properties dialog and ensure 'Use Legacy Console' is unchecked, then close dialog 3. Select menu option 'defaults' # Expected behavior The terminal properties should be set to their factory defaults. # Actual behavior Property window opens and properties have not been changed. What are the factory defaults? Who knows?
claunia commented 2026-01-30 23:56:53 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 4, 2019):

Hey thanks for the feedback! I definitely understand that UX is especially confusing. However, the "defaults" menu has literally never worked that way. When it comes to console settings, they're layered from a variety of locations, starting with the first here and successively applying subsequent layers:

  1. The hardcoded defaults embedded in the application itself.
  2. "Defaults" storen in the registry under HKCU\Console
  3. Optionally, one of the following:
  • Properties that are stored in the shortcut
  • per-title settings that can be stored in HKCU\Console\<title>
  1. Runtime settings passed in through STARTUPINFO.

When you open the "Defaults" propsheet, what you're actually doing is opening the menu to edit the defaults in item 2, the "registry defaults".

If you really want to "reset to factory defaults", you can just delete all the the keys under HKCU\Console.

@zadjii-msft commented on GitHub (Nov 4, 2019): Hey thanks for the feedback! I definitely understand that UX is especially confusing. However, the "defaults" menu has literally never worked that way. When it comes to console settings, they're layered from a variety of locations, starting with the first here and successively applying subsequent layers: 1. The hardcoded defaults embedded in the application itself. 2. "Defaults" storen in the registry under `HKCU\Console` 3. Optionally, one of the following: * Properties that are stored in the shortcut * per-title settings that can be stored in `HKCU\Console\<title>` 4. Runtime settings passed in through `STARTUPINFO`. When you open the "Defaults" propsheet, what you're actually doing is opening the menu to edit the defaults in item 2, the "registry defaults". If you _really_ want to "reset to factory defaults", you can just delete all the the keys under `HKCU\Console`.
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-Question Needs-Triage Product-Conhost Resolution-Answered
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#4799
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?