Windows terminal's light/dark window theme does not change automatically when changed in windows settings #8596

Closed
opened 2026-01-31 01:33:23 +00:00 by claunia · 2 comments
Owner

Originally created by @skypaint96 on GitHub (May 26, 2020).

Environment

Windows build number: Microsoft Windows NT 10.0.19631.0
Windows Terminal version (if applicable): 1.0.1401.0

Steps to reproduce

  1. open windows terminal, keep this open
  2. in PowerShell(either in that terminal window or elsewhere) type Start-Process -FilePath 'ms-settings:personalization-colors'
  3. use the dropdown menu to change the value of the 'change your colour' option
  4. notice that all the windows on your screen(setting, windows store apps, chromium Microsoft edge) change from a whatever light/dark theme they were set to, to its opposite. windows terminal does not.

Expected behavior

I would expect that the light/dark theme of open windows terminal windows would change automatically when it is changed in the system settings.

Actual behavior

Windows terminal will not change its light/dark theme automatically, instead for it to change you will have to close the window, clearing all session variables, and open a new window where the light/dark theme is as changed in system settings

Originally created by @skypaint96 on GitHub (May 26, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment Windows build number: Microsoft Windows NT 10.0.19631.0 Windows Terminal version (if applicable): 1.0.1401.0 # Steps to reproduce 1. open windows terminal, keep this open 2. in PowerShell(either in that terminal window or elsewhere) type `Start-Process -FilePath 'ms-settings:personalization-colors'` 3. use the dropdown menu to change the value of the 'change your colour' option 4. notice that all the windows on your screen(setting, windows store apps, chromium Microsoft edge) change from a whatever light/dark theme they were set to, to its opposite. windows terminal does not. # Expected behavior I would expect that the light/dark theme of open windows terminal windows would change automatically when it is changed in the system settings. # Actual behavior Windows terminal will not change its light/dark theme automatically, instead for it to change you will have to close the window, clearing all session variables, and open a new window where the light/dark theme is as changed in system settings
claunia added the Resolution-Duplicate label 2026-01-31 01:33:23 +00:00
Author
Owner

@zadjii-msft commented on GitHub (May 26, 2020):

Thanks for the report! This is actually already being tracked by another issue on our repo - please refer to #1230 for more discussion.

/dup #1230

@zadjii-msft commented on GitHub (May 26, 2020): Thanks for the report! This is actually already being tracked by another issue on our repo - please refer to #1230 for more discussion. /dup #1230
Author
Owner

@ghost commented on GitHub (May 26, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (May 26, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#8596