CursorColor changed on its own #278

Open
opened 2026-01-30 21:47:50 +00:00 by claunia · 0 comments
Owner

Originally created by @mqudsi on GitHub (May 26, 2018).

Originally assigned to: @zadjii-msft on GitHub.

Running 17672, I suddenly found (with two terminal windows open) that one terminal window's cursor had turned black instead of gray. From that point onwards, all my terminals (Windows or WSL) have had a black cursor (even after DECSCUSR calls).

I imagine this might be related to the newly landed support for setting cursor shape, but I'm unable to get this color change to revert.

Deleting CursorColor in the Console registry key took care of the issue, but I'm not sure how it could have come to be in the first place. This option isn't exposed userland, is it? Black is DWORD 0, so it could be that the value was simply created with a default integer for its content, but again, not sure how that happened.

Originally created by @mqudsi on GitHub (May 26, 2018). Originally assigned to: @zadjii-msft on GitHub. Running 17672, I suddenly found (with two terminal windows open) that one terminal window's cursor had turned black instead of gray. From that point onwards, all my terminals (Windows or WSL) have had a black cursor (even after DECSCUSR calls). I imagine this might be related to the newly landed support for setting cursor shape, but I'm unable to get this color change to revert. Deleting `CursorColor` in the `Console` registry key took care of the issue, but I'm not sure how it could have come to be in the first place. This option isn't exposed userland, is it? Black is DWORD `0`, so it _could_ be that the value was simply created with a default integer for its content, but again, not sure how that happened.
claunia added the Product-ConhostResolution-Fix-AvailableWork-Item labels 2026-01-30 21:47:50 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#278