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

Black screen in legacy mode #1714

New Issue
Closed
opened 2026-01-30 22:34:26 +00:00 by claunia · 4 comments
claunia commented 2026-01-30 22:34:26 +00:00
Owner
Copy Link

Originally created by @eElor on GitHub (Jun 16, 2019).

Today Ubuntu (WSL) opened just a black window.

I re-installed it and tried different things to get it to work properly again. I noticed that using the legacy mode caused that black/blank window. However, by turning it off, all the other windows consoles (cmd, powershell) became black as well.

Re-installing Ubuntu and using it seems to require the legacy mode to be off, but cmd and powershell on... That wasn't the case not long ago.

my WSL was always up to date. I wrote this issue after it completely stopped working. I still do not know the reason. But after playing around, I discovered the issue with the legacy mode. I just tried it again: I updated and upgraded WSL and turned on legacy mode (was off before, since WSL won’t work otherwise).

WSL stopped working altogether. It won’t even start... However, CMD and Powershell are working now (were before only black windows). And they only do in legacy mode ( right click on any console > properties > Options >Use legacy console (requires relaunch...) ). As soon as I turn legacy mode off in cmd/powershell, WSL starts working again, but the other two appear just as black windows.

image

image

Originally created by @eElor on GitHub (Jun 16, 2019). Today Ubuntu (WSL) opened just a black window. I re-installed it and tried different things to get it to work properly again. I noticed that using the legacy mode caused that black/blank window. However, by turning it off, all the other windows consoles (cmd, powershell) became black as well. Re-installing Ubuntu and using it seems to require the legacy mode to be off, but cmd and powershell on... That wasn't the case not long ago. my WSL was always up to date. I wrote this issue after it completely stopped working. I still do not know the reason. But after playing around, I discovered the issue with the legacy mode. I just tried it again: I updated and upgraded WSL and turned on legacy mode (was off before, since WSL won’t work otherwise). WSL stopped working altogether. It won’t even start... However, CMD and Powershell are working now (were before only black windows). And they only do in legacy mode ( `right click on any console > properties > Options >Use legacy console (requires relaunch...) `). As soon as I turn legacy mode off in cmd/powershell, WSL starts working again, but the other two appear just as black windows. ![image](https://user-images.githubusercontent.com/39239890/59568421-c3638580-907a-11e9-80c2-8bd33c988e8f.png) ![image](https://user-images.githubusercontent.com/39239890/59568416-b6469680-907a-11e9-8221-33390a43b6f8.png)
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-30 22:34:26 +00:00
claunia commented 2026-01-30 22:34:28 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 18, 2019):

You're gonna want to look at the "Terminal" tab in your propsheet. I'm gonna go out on a limb and guess that the "Default Foreground" and "Default background" colors somehow got set to 0,0,0 for each of them. You could probably just uncheck those boxes to fix powershell and cmd.

@zadjii-msft commented on GitHub (Jun 18, 2019): You're gonna want to look at the "Terminal" tab in your propsheet. I'm gonna go out on a limb and guess that the "Default Foreground" and "Default background" colors somehow got set to 0,0,0 for each of them. You could probably just uncheck those boxes to fix powershell and cmd.
claunia commented 2026-01-30 22:34:28 +00:00
Author
Owner
Copy Link

@eElor commented on GitHub (Jun 18, 2019):

Thanks @zadjii-msft, that was it. Unchecking "Use Separate Background / Foreground" solved the problem. However I don't remember having checking them...

@eElor commented on GitHub (Jun 18, 2019): Thanks @zadjii-msft, that was it. Unchecking "Use Separate Background / Foreground" solved the problem. However I don't remember having checking them...
claunia commented 2026-01-30 22:34:28 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 18, 2019):

That's a good point. It seems to happen sometimes on updates to the latest Windows build, but we've never been able to get a solid repro case.

@zadjii-msft commented on GitHub (Jun 18, 2019): That's a good point. It seems to happen sometimes on updates to the latest Windows build, but we've never been able to get a solid repro case.
claunia commented 2026-01-30 22:34:28 +00:00
Author
Owner
Copy Link

@Richard004 commented on GitHub (Feb 11, 2020):

Same for me. I had the default value of 0,0,0 for both Terminal Colors and Use Separate Foreground was on. The same scenario happened on both my machines.
I did not explicitly mess with this part of settings.
I was lost also.
But I've installed the experimental Terminal before, so I 'kind-of' took the blame on my experimenting there.

@Richard004 commented on GitHub (Feb 11, 2020): Same for me. I had the default value of 0,0,0 for both Terminal Colors and Use Separate Foreground was on. The same scenario happened on both my machines. I did not explicitly mess with this part of settings. I was lost also. But I've installed the experimental Terminal before, so I 'kind-of' took the blame on my experimenting there.
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-Attention 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#1714
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?