Profile menu sometimes changes to a darker color #10489

Closed
opened 2026-01-31 02:22:58 +00:00 by claunia · 12 comments
Owner

Originally created by @KalleOlaviNiemitalo on GitHub (Sep 4, 2020).

Environment

Windows build number: 10.0.19041.450
Windows Terminal version (if applicable): Windows Terminal Preview 1.3.2382.0

The only color setting in my settings.json is "colorScheme": "Campbell" in one profile. Windows is using a light theme.

Steps to reproduce

Unknown. The problem happens occasionally, not every day. I tried opening new tabs, closing the previous tabs, and resizing the window, but that did not help. Then after I took a screen shot with Alt+PrtScr, the background color of the menu returned to correct, even though I had not restarted Windows Terminal Preview or edited settings.json.

Expected behavior

Light background in profile menu:

image

Actual behavior

Too dark background in profile menu:

image

Originally created by @KalleOlaviNiemitalo on GitHub (Sep 4, 2020). # Environment ```none Windows build number: 10.0.19041.450 Windows Terminal version (if applicable): Windows Terminal Preview 1.3.2382.0 ``` The only color setting in my `settings.json` is `"colorScheme": "Campbell"` in one profile. Windows is using a light theme. # Steps to reproduce Unknown. The problem happens occasionally, not every day. I tried opening new tabs, closing the previous tabs, and resizing the window, but that did not help. Then after I took a screen shot with Alt+PrtScr, the background color of the menu returned to correct, even though I had not restarted Windows Terminal Preview or edited settings.json. # Expected behavior Light background in profile menu: ![image](https://user-images.githubusercontent.com/46201428/92226326-3a1db600-eead-11ea-8187-07ad8375d4e7.png) # Actual behavior Too dark background in profile menu: ![image](https://user-images.githubusercontent.com/46201428/92226300-2f632100-eead-11ea-975d-725786c82c49.png)
Author
Owner

@KalleOlaviNiemitalo commented on GitHub (Sep 4, 2020):

If the problem recurs, what should I do to collect information that would help fix it?

@KalleOlaviNiemitalo commented on GitHub (Sep 4, 2020): If the problem recurs, what should I do to collect information that would help fix it?
Author
Owner

@DHowett commented on GitHub (Sep 10, 2020):

This is fascinating!

If you hit this again, can you collect a process dump for WindowsTerminal.exe from task manager? You can stick it on OneDrive & send it to my microsoft address (on my GitHub profile).

If you're not comfortable sharing whatever might be in that dump (including any text in the output buffer, etc.) I understand.

I'm guessing this is in the parts of Windows.UI.Xaml that are not open-source, so local debugging might prove to be an issue.

@DHowett commented on GitHub (Sep 10, 2020): This is fascinating! If you hit this again, can you collect a process dump for WindowsTerminal.exe from task manager? You can stick it on OneDrive & send it to my microsoft address (on my GitHub profile). If you're not comfortable sharing whatever might be in that dump (including any text in the output buffer, etc.) I understand. I'm guessing this is in the parts of Windows.UI.Xaml that are not open-source, so local debugging might prove to be an issue.
Author
Owner

@zadjii-msft commented on GitHub (Oct 1, 2020):

Hey so for the record, I hit this once before, but when it happened to me, it wasn't Terminal specific - a bunch of the shadows across the system seemed to be at the wrong z-order. I had a thread with the XAML team about this (titled "Shadow on MenuFlyouts?"), but there wasn't really ever a root cause found, since it stopped happening to me and it hasn't happened since.

@zadjii-msft commented on GitHub (Oct 1, 2020): Hey so for the record, I hit this once before, but when it happened to me, it wasn't Terminal specific - a _bunch_ of the shadows across the system seemed to be at the wrong z-order. I had a thread with the XAML team about this (titled "Shadow on MenuFlyouts?"), but there wasn't really ever a root cause found, since it stopped happening to me and it hasn't happened since.
Author
Owner

@LuanVSO commented on GitHub (Nov 13, 2020):

this also happens to me seemingly at random from time to time, I've noted that it goes away after opening and closing one of the shell menus (start menu, action center)

@LuanVSO commented on GitHub (Nov 13, 2020): this also happens to me seemingly at random from time to time, I've noted that it goes away after opening and closing one of the shell menus (start menu, action center)
Author
Owner

@KalleOlaviNiemitalo commented on GitHub (Dec 3, 2020):

It happened again, with Windows Terminal Preview Version: 1.5.3242.0 on Microsoft Windows [Version 10.0.19042.630]. I then started Task Manager and made a dump file. The problem continued. I started another instance of Windows Terminal Preview, hoping that I'd be able to get a dump file with less proprietary information, but the new instance did not have the problem, and then neither did the original instance.

@KalleOlaviNiemitalo commented on GitHub (Dec 3, 2020): It happened again, with Windows Terminal Preview Version: 1.5.3242.0 on Microsoft Windows \[Version 10.0.19042.630]. I then started Task Manager and made a dump file. The problem continued. I started another instance of Windows Terminal Preview, hoping that I'd be able to get a dump file with less proprietary information, but the new instance did not have the problem, and then neither did the original instance.
Author
Owner

@LuanVSO commented on GitHub (Jan 28, 2021):

hey so I'm getting something like this. every time i save the settings.json with wt in the background the tab changes to this:

image
which is a similar look

@LuanVSO commented on GitHub (Jan 28, 2021): hey so I'm getting something like this. every time i save the settings.json with wt in the background the tab changes to this: ![image](https://user-images.githubusercontent.com/43626415/106211871-336b4480-61a8-11eb-8d62-2fee69317836.png) which is a similar look
Author
Owner

@zadjii-msft commented on GitHub (Jan 29, 2021):

Holy crap me too. This is crazy consistent on the latest release, but I don't recall seeing it at all in the lead up to the release. Weird. I'm gonna move that to it's own issue, since I'm expecting the issue with the TabViewItem to be different from the one in the menu flyout.

@zadjii-msft commented on GitHub (Jan 29, 2021): Holy crap me too. This is crazy consistent on the latest release, but I don't recall seeing it at all in the lead up to the release. Weird. I'm gonna move that to it's own issue, since I'm expecting the issue with the TabViewItem to be different from the one in the menu flyout.
Author
Owner

@LuanVSO commented on GitHub (Aug 4, 2021):

so, this is happening system wide on build 22000.100 persisting through reboots on my machine, how can i help with the diagnosis?

@LuanVSO commented on GitHub (Aug 4, 2021): so, this is happening system wide on build 22000.100 persisting through reboots on my machine, how can i help with the diagnosis?
Author
Owner

@zadjii-msft commented on GitHub (Aug 4, 2021):

@LuanVSO this is something that's more widespread in Windows 11 builds than it was before. I think this is also tracked over in https://github.com/microsoft/microsoft-ui-xaml/issues/5133, and upstream of even that at MSFT:33411893 which then got duped to MSFT:34432192, which is apparently fixed, but I have no idea how to read the internal build numbers anymore. This might be fixed in 22000.130?

also for linking: #10773, #10741

@zadjii-msft commented on GitHub (Aug 4, 2021): @LuanVSO this is something that's more widespread in Windows 11 builds than it was before. I think this is also tracked over in https://github.com/microsoft/microsoft-ui-xaml/issues/5133, and upstream of even that at MSFT:33411893 which then got duped to MSFT:34432192, which is apparently fixed, but I have no idea how to read the internal build numbers anymore. This might be fixed in 22000.130? also for linking: #10773, #10741
Author
Owner

@ealap commented on GitHub (Aug 6, 2021):

I just updated to Win11 build 22000.120 and it seems fixed

@ealap commented on GitHub (Aug 6, 2021): I just updated to Win11 build 22000.120 and it seems fixed
Author
Owner

@zadjii-msft commented on GitHub (Mar 8, 2022):

Okay yea this was MSFT:33411893 which should have been fixed in KB5004300, which I think corresponds to 22000.100. Thanks everyone!

@zadjii-msft commented on GitHub (Mar 8, 2022): Okay yea this was MSFT:33411893 which should have been fixed in KB5004300, which I think corresponds to [22000.100](https://blogs.windows.com/windows-insider/2021/07/22/announcing-windows-11-insider-preview-build-22000-100/). Thanks everyone!
Author
Owner

@DrPepperBianco commented on GitHub (Nov 22, 2022):

This still happens to me. I'm on 22H2 (Build 19045.2130) [That is Windows 10, for those who wonder].

What can I do to fix this? Someone said this would be a OS bug. Is the KB-Update or something to fix this?

@DrPepperBianco commented on GitHub (Nov 22, 2022): This still happens to me. I'm on 22H2 (Build 19045.2130) [That is Windows 10, for those who wonder]. What can I do to fix this? Someone said this would be a OS bug. Is the KB-Update or something to fix this?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#10489