This is a repost per the DM I received:
“You say in your post that it's not a new issue which implies that it isn't something introduced in an update. If you disagree, feel free to repost with more information on when the issue started, the update it was introduced in, and the version you are on now.”
The removal doesn’t really support a cohesive Insider feedback loop, so here’s the clarified version with the requested timeline. (Also, 'flair'ed as a potential issue, NOT a support request.)
I first saw this issue in February 2025, during the Alpha Skip‑Ahead 2504.250220‑2200 period — the same window when Microsoft was actively working on CEC behavior and video‑pipeline changes. The timing matters because this wasn’t a random glitch; it appeared exactly when both systems were being touched simultaneously.
My current build is Alpha Skip‑Ahead 2610.260825‑2200. Listing it is technically unnecessary, since Insider participation doesn’t require tracking regressions across builds, but I’m including it per the DM request.
The issue itself is straightforward and intermittently reproducible:
When the Xbox (Energy Saving Mode) powers on the TV (also Energy Saving Mode) via CEC, the HDMI handshake comes up with a completely broken color gamut. Blues become Reds. Reds become Blues. It’s not subtle — it’s a full inversion.
A TV restart fixes it.
A forced HDMI handshake (format switch, or simply input a→b→a) also fixes it.
This strongly suggests the startup handshake is mistimed, incomplete, or failing under CEC‑initiated power‑on. Multiple cables tested. Same result.
<Image Link> — the failure is visually obvious.
Anyone else seeing this? I'm seeking confirmation, not workarounds.
Edit: Thought I wanted to add; This (theoretical) handshake issue is strangely specific. I'm not experiencing any other historical handshake issues with EDID, like black screens, audio drops, or resolution mismatching (like 'unsupported')