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

Turning legacy console on, then off, sets the defaultforeground to black #4128

New Issue
Open
opened 2026-01-30 23:38:55 +00:00 by claunia · 0 comments
claunia commented 2026-01-30 23:38:55 +00:00
Owner
Copy Link

Originally created by @fpqc on GitHub (Sep 29, 2019).

Windows Build: 18990.1 Insiders Fast Ring

I was messing around with the console, and I enabled the legacy console feature to test something with VT sequence processing. Bash wouldn't even launch, so I went to change it back to the modern console. When I did this, I was no longer able to run cmd at all from the Run dialog, producing a completely black window. I tried a logoff, then a reboot, and the problem still persisted. I am no longer able to run cmd from the Run Dialog

Please help!

Edit: I was able to fix this by deleting the regkey
HKEY_CURRENT_USER\Console\%SystemRoot%_System32_cmd.exe

I suspect that turning the legacy console on and off is writing a bad key that puts the console in a bad state.

Edit 2: I was just able to reproduce it by performing the same sequence of actions again. Turning legacy console on then off creates the following values in the registry:

image

Something here breaks the modern console.

Edit 3: I found the culprit. The default foreground color is being set to black (0) when you disable legacy console.

Originally created by @fpqc on GitHub (Sep 29, 2019). Windows Build: 18990.1 Insiders Fast Ring I was messing around with the console, and I enabled the legacy console feature to test something with VT sequence processing. Bash wouldn't even launch, so I went to change it back to the modern console. When I did this, I was no longer able to run cmd at all from the Run dialog, producing a completely black window. I tried a logoff, then a reboot, and the problem still persisted. I am no longer able to run cmd from the Run Dialog Please help! Edit: I was able to fix this by deleting the regkey ``HKEY_CURRENT_USER\Console\%SystemRoot%_System32_cmd.exe`` I suspect that turning the legacy console on and off is writing a bad key that puts the console in a bad state. Edit 2: I was just able to reproduce it by performing the same sequence of actions again. Turning legacy console on then off creates the following values in the registry: ![image](https://user-images.githubusercontent.com/6083371/65824841-375f1d80-e267-11e9-8069-c9aa872ae36e.png) Something here breaks the modern console. Edit 3: I found the culprit. The default foreground color is being set to black (0) when you disable legacy console.
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-30 23:38:55 +00:00
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#4128
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?