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

Bug Report: ColorTool and changing colours causes strange behaviour since Windows 10 1903 #1524

New Issue
Open
opened 2026-01-30 22:29:34 +00:00 by claunia · 5 comments
claunia commented 2026-01-30 22:29:34 +00:00
Owner
Copy Link

Originally created by @fgimian on GitHub (Jun 5, 2019).

Environment

Microsoft Windows [Version 10.0.18362.30]

Steps to reproduce

You should be able to use any color scheme, but I'll provide mine specifically below.

Fotsies Colors.ini

[table]
DARK_BLACK = 30,30,30
DARK_BLUE = 0,0,128
DARK_GREEN = 0,128,0
DARK_CYAN = 0,128,128
DARK_RED = 128,75,75
DARK_MAGENTA = 128,0,128
DARK_YELLOW = 238,237,240
DARK_WHITE = 192,192,192
BRIGHT_BLACK = 128,128,128
BRIGHT_BLUE = 0,0,255
BRIGHT_GREEN = 0,255,0
BRIGHT_CYAN = 0,255,255
BRIGHT_RED = 255,75,75
BRIGHT_MAGENTA = 255,0,255
BRIGHT_YELLOW = 255,255,0
BRIGHT_WHITE = 255,255,255

[screen]
FOREGROUND = DARK_WHITE
BACKGROUND = DARK_BLACK

[popup]
FOREGROUND = DARK_CYAN
BACKGROUND = DARK_BLACK
  1. Open PowerShell as a regular user (I'm using 5.1 that comes with Windows 10)
  2. Obtain the latest ColorTool release and extract it
  3. Place the scheme above in the schemes sub-directory under ColorTool.exe
  4. Load the scheme: .\ColorTool.exe 'Fotsies Colors.ini'
  5. Notice the scheme is not applied correctly and that colors are not consistent as they should be

Expected behavior

As per the previous stable Windows release, colors should be applied correctly and continue to function while using the terminal

Actual behavior

Best way to demonstrate this is with some screenshots:

image

I tested this with a completely fresh install of windows 10 1903 just now to confirm it's nothing that I've done wrong. I can confirm that everything works perfectly in the previous October 2018 Windows 10 release.

Honestly, the terminal in this new release is unusable for me given all the problems I've been finding and I don't really have much choice but to reinstall the older Windows release as I depend on PowerShell. Unless of course any workarounds may be suggested?

Any help is greatly appreciated.

Originally created by @fgimian on GitHub (Jun 5, 2019). # Environment ```none Microsoft Windows [Version 10.0.18362.30] ``` # Steps to reproduce You should be able to use any color scheme, but I'll provide mine specifically below. **Fotsies Colors.ini** ```ini [table] DARK_BLACK = 30,30,30 DARK_BLUE = 0,0,128 DARK_GREEN = 0,128,0 DARK_CYAN = 0,128,128 DARK_RED = 128,75,75 DARK_MAGENTA = 128,0,128 DARK_YELLOW = 238,237,240 DARK_WHITE = 192,192,192 BRIGHT_BLACK = 128,128,128 BRIGHT_BLUE = 0,0,255 BRIGHT_GREEN = 0,255,0 BRIGHT_CYAN = 0,255,255 BRIGHT_RED = 255,75,75 BRIGHT_MAGENTA = 255,0,255 BRIGHT_YELLOW = 255,255,0 BRIGHT_WHITE = 255,255,255 [screen] FOREGROUND = DARK_WHITE BACKGROUND = DARK_BLACK [popup] FOREGROUND = DARK_CYAN BACKGROUND = DARK_BLACK ``` 1. Open PowerShell as a regular user (I'm using 5.1 that comes with Windows 10) 2. Obtain the latest ColorTool release and extract it 3. Place the scheme above in the schemes sub-directory under ColorTool.exe 4. Load the scheme: `.\ColorTool.exe 'Fotsies Colors.ini'` 5. Notice the scheme is not applied correctly and that colors are not consistent as they should be # Expected behavior As per the previous stable Windows release, colors should be applied correctly and continue to function while using the terminal # Actual behavior Best way to demonstrate this is with some screenshots: ![image](https://user-images.githubusercontent.com/1811813/58951600-e2d5f500-87d4-11e9-8fe7-b64155970648.png) I tested this with a completely fresh install of windows 10 1903 just now to confirm it's nothing that I've done wrong. I can confirm that everything works perfectly in the previous October 2018 Windows 10 release. Honestly, the terminal in this new release is unusable for me given all the problems I've been finding and I don't really have much choice but to reinstall the older Windows release as I depend on PowerShell. Unless of course any workarounds may be suggested? Any help is greatly appreciated.
claunia added the Product-ColortoolHelp WantedIssue-BugNeeds-Tag-Fix labels 2026-01-30 22:29:34 +00:00
claunia commented 2026-01-30 22:29:34 +00:00
Author
Owner
Copy Link

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

This is probably due to us adding default background color support to conhost in 1903. Could you open the property sheet, and show me what the following tab looks like?
image

As a workaround, I'd suggest switching to the "Colors" tab, and with "Screen Background" selected, click on the first box, to make your background color DARK_BLACK, instead of DARK_MAGENTA (which is the powershell default)

@zadjii-msft commented on GitHub (Jun 5, 2019): This is probably due to us adding default background color support to conhost in 1903. Could you open the property sheet, and show me what the following tab looks like? ![image](https://user-images.githubusercontent.com/18356694/58962678-4fb7a380-8771-11e9-91a9-c6f94986c3ef.png) As a workaround, I'd suggest switching to the "Colors" tab, and with "Screen Background" selected, click on the first box, to make your background color DARK_BLACK, instead of DARK_MAGENTA (which is the powershell default)
claunia commented 2026-01-30 22:29:35 +00:00
Author
Owner
Copy Link

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

I'm going to leave this open to investigate, however. We might need to update colortool to make sure to set FOREGROUND and BACKGROUND properly, because it doesn't seem to be doing that right.

@zadjii-msft commented on GitHub (Jun 5, 2019): I'm going to leave this open to investigate, however. We might need to update colortool to make sure to set FOREGROUND and BACKGROUND properly, because it doesn't seem to be doing that right.
claunia commented 2026-01-30 22:29:35 +00:00
Author
Owner
Copy Link

@fgimian commented on GitHub (Jun 6, 2019):

Thanks so much for your help, sorry for the late reply, I'm in a different timezone (Australia).

Here's a screenshot as requested:

image

Indeed it apperas that you are correct, when setting the background color to the first box (Dark Black), it seems to help. However, ColorTool doesn't seem to make a persistent change.

e.g.

Here's what my PowerShell console looks after I switch to the first checkbox for the background color:

image

I then apply my colors with ColorTool:

image

At this point, things seem to be ok, but then when I close and re-open PowerShell, I am back to black:

image

All colors seem to be reset too so the change doesn't appear to stay persistent.

As a sidenote, the terminal in PowerShell 7 preview 1 works perfectly with all of these scenarios too.

Kindest regards
Fotis

@fgimian commented on GitHub (Jun 6, 2019): Thanks so much for your help, sorry for the late reply, I'm in a different timezone (Australia). Here's a screenshot as requested: ![image](https://user-images.githubusercontent.com/1811813/58998380-c91fc680-8843-11e9-91eb-255b7d2722bf.png) Indeed it apperas that you are correct, when setting the background color to the first box (Dark Black), it seems to help. However, ColorTool doesn't seem to make a persistent change. e.g. Here's what my PowerShell console looks after I switch to the first checkbox for the background color: ![image](https://user-images.githubusercontent.com/1811813/58998419-02583680-8844-11e9-9bcc-f0c1b6d1215d.png) I then apply my colors with ColorTool: ![image](https://user-images.githubusercontent.com/1811813/58998425-0a17db00-8844-11e9-843e-a055c2ef30e8.png) At this point, things seem to be ok, but then when I close and re-open PowerShell, I am back to black: ![image](https://user-images.githubusercontent.com/1811813/58998437-1dc34180-8844-11e9-8a69-6b458aa6282b.png) All colors seem to be reset too so the change doesn't appear to stay persistent. As a sidenote, the terminal in PowerShell 7 preview 1 works perfectly with all of these scenarios too. Kindest regards Fotis
claunia commented 2026-01-30 22:29:35 +00:00
Author
Owner
Copy Link

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

You need to open the propsheet and hit "ok" to make sure to persist the colors. --both just means colortool will apply the color both to the active console window and the registry defaults. However, if you're launching the console from a shortcut, or from an exe that has it's own console entry in the registry (which powershell does), then the console will use the shortcut/registry for the app instead of the defaults. So, you need to open and save the propsheet again, to make sure the settings are persisted to the shortcut.

@zadjii-msft commented on GitHub (Jun 6, 2019): You need to open the propsheet and hit "ok" to make sure to persist the colors. `--both` just means colortool will apply the color both to the active console window and the registry defaults. However, if you're launching the console from a shortcut, or from an exe that has it's own console entry in the registry (which powershell does), then the console will use the shortcut/registry for the app instead of the defaults. So, you need to open and save the propsheet again, to make sure the settings are persisted to the shortcut.
claunia commented 2026-01-30 22:29:35 +00:00
Author
Owner
Copy Link

@fgimian commented on GitHub (Jun 8, 2019):

You need to open the propsheet and hit "ok" to make sure to persist the colors. --both just means colortool will apply the color both to the active console window and the registry defaults. However, if you're launching the console from a shortcut, or from an exe that has it's own console entry in the registry (which powershell does), then the console will use the shortcut/registry for the app instead of the defaults. So, you need to open and save the propsheet again, to make sure the settings are persisted to the shortcut.

Thanks a lot, that seemed to do the trick 😄

@fgimian commented on GitHub (Jun 8, 2019): > You need to open the propsheet and hit "ok" to make sure to persist the colors. `--both` just means colortool will apply the color both to the active console window and the registry defaults. However, if you're launching the console from a shortcut, or from an exe that has it's own console entry in the registry (which powershell does), then the console will use the shortcut/registry for the app instead of the defaults. So, you need to open and save the propsheet again, to make sure the settings are persisted to the shortcut. Thanks a lot, that seemed to do the trick 😄
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 Help Wanted Issue-Bug Needs-Tag-Fix Product-Colortool
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#1524
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?