Menu shade changed after latest W10 update #11041

Closed
opened 2026-01-31 02:37:01 +00:00 by claunia · 8 comments
Owner

Originally created by @mwpowellhtx on GitHub (Oct 15, 2020).

After the 20-10-15 W10 update, something changed in the menu. It was previously a solid color, now is an awful shaded color.

image

Originally created by @mwpowellhtx on GitHub (Oct 15, 2020). After the 20-10-15 W10 update, something changed in the menu. It was previously a solid color, now is an awful shaded color. ![image](https://user-images.githubusercontent.com/1824187/96144079-c5895e80-0ed1-11eb-902e-159507aaecfe.png)
claunia added the Resolution-Duplicate label 2026-01-31 02:37:01 +00:00
Author
Owner

@ghost commented on GitHub (Oct 15, 2020):

You mean version 20H2?

run winver

image

@ghost commented on GitHub (Oct 15, 2020): You mean version 20H2? run `winver` ![image](https://user-images.githubusercontent.com/67918878/96145527-eded7900-0f22-11eb-99de-952b04ee1875.png)
Author
Owner

@mwpowellhtx commented on GitHub (Oct 15, 2020):

Nope.

image

@mwpowellhtx commented on GitHub (Oct 15, 2020): Nope. ![image](https://user-images.githubusercontent.com/1824187/96152067-1d2bc800-0eda-11eb-976a-f43848a6eaae.png)
Author
Owner

@ghost commented on GitHub (Oct 15, 2020):

Ok. An internal team member will have to deal with this.

@ghost commented on GitHub (Oct 15, 2020): Ok. An internal team member will have to deal with this.
Author
Owner

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

Huh, you're the second person to report this recently, though we're really not sure what's causing it. The thread we're using to track this is over at /dup #7532. From my experience with this bug, it went away after a reboot, and hasn't come back since, so it's terribly difficult to investigate. You might also be able to mitigate this by rebooting.

@zadjii-msft commented on GitHub (Oct 15, 2020): Huh, you're the second person to report this recently, though we're really not sure what's causing it. The thread we're using to track this is over at /dup #7532. From my experience with this bug, it went away after a reboot, and hasn't come back since, so it's terribly difficult to investigate. You might also be able to mitigate this by rebooting.
Author
Owner

@ghost commented on GitHub (Oct 15, 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 (Oct 15, 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!
Author
Owner

@ghost commented on GitHub (Oct 15, 2020):

I thought that I was the master of finding duplicate issues. 😭

@ghost commented on GitHub (Oct 15, 2020): I thought that I was the master of finding duplicate issues. 😭
Author
Owner

@mwpowellhtx commented on GitHub (Oct 15, 2020):

@zadjii-msft I will try to "mitigate" when I reboot. But to be honest, why is it occurring in the first place?

@mwpowellhtx commented on GitHub (Oct 15, 2020): @zadjii-msft I will try to "mitigate" when I reboot. But to be honest, why is it occurring in the first place?
Author
Owner

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

@mwpowellhtx Honestly, I've got no idea. I'm thinking it's an OS bug where ThemeShadows get composited in the wrong z-order. In this case, the shadow from the MenuFlyout is appearing above the MenuFlyout. From what I recall, it was affecting all shadows cast by MenuFlyouts in apps across the OS, including ones in the Xaml Controls Gallery. I wasn't ever able to drive it to a root cause with the composition team, and since it went away for me, I assumed it was just a transient bug that popped up in the middle of a OS release cycle. Apparently, the bug wasn't just transient, and made its way out to users 😢

@zadjii-msft commented on GitHub (Oct 15, 2020): @mwpowellhtx Honestly, I've got no idea. I'm thinking it's an OS bug where `ThemeShadow`s get composited in the wrong z-order. In this case, the shadow from the `MenuFlyout` is appearing _above_ the `MenuFlyout`. From what I recall, it was affecting _all_ shadows cast by `MenuFlyout`s in apps across the OS, including ones in the Xaml Controls Gallery. I wasn't ever able to drive it to a root cause with the composition team, and since it went away for me, I assumed it was just a transient bug that popped up in the middle of a OS release cycle. Apparently, the bug wasn't just transient, and made its way out to users 😢
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#11041