starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Missing cursor when experimental text rendering engine is enabled in HDR enabled monitor #16795

New Issue
Closed
opened 2026-01-31 05:22:56 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 05:22:56 +00:00
Owner
Copy Link

Originally created by @okibcn on GitHub (Feb 16, 2022).

Originally assigned to: @lhecker on GitHub.

Windows Terminal version

1.13.10395.0

Windows build number

10.0.22000

Other Software

Plain vanilla Powershell

Steps to reproduce

  1. Enable Experimental text rendering engine in the advanced submenu of the Powershell profile and save config.
  2. Open a Windows Powershell, Powershell Core, or Command Prompt tab. on an HDR monitor.

Expected Behavior

The cursor should appear and blink.

Actual Behavior

No cursor at all, not even a solid cursor shows up.

Disabling experimental rendering brings back a fully functional blinking cursor.
Moving the Terminal window to a monitor without HDR brings the cursor back.

Originally created by @okibcn on GitHub (Feb 16, 2022). Originally assigned to: @lhecker on GitHub. ### Windows Terminal version 1.13.10395.0 ### Windows build number 10.0.22000 ### Other Software Plain vanilla Powershell ### Steps to reproduce 1. Enable Experimental text rendering engine in the advanced submenu of the Powershell profile and save config. 2. Open a Windows Powershell, Powershell Core, or Command Prompt tab. **on an HDR monitor.** ### Expected Behavior The cursor should appear and blink. ### Actual Behavior No cursor at all, not even a solid cursor shows up. **Disabling experimental rendering brings back a fully functional blinking cursor. Moving the Terminal window to a monitor without HDR brings the cursor back.**
claunia commented 2026-01-31 05:22:58 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Feb 18, 2022):

If you don't mind, could you post your config file (a minimal one that reproduces your issue is enough), as well as a screenshot of your terminal while you've got input focus?

@lhecker commented on GitHub (Feb 18, 2022): If you don't mind, could you post your config file (a minimal one that reproduces your issue is enough), as well as a screenshot of your terminal while you've got input focus?
claunia commented 2026-01-31 05:22:58 +00:00
Author
Owner
Copy Link

@zamadatix commented on GitHub (Feb 19, 2022):

Interestingly if I print-screen the cursor isn't there (which is also what I see during use):

image

and if I unfocus the window and print-screen the cursor isn't there:

image

but if I snipping-tool the window while it is focused the cursor renders:

image

settings.json for reference:

settings.json.txt

@zamadatix commented on GitHub (Feb 19, 2022): Interestingly if I print-screen the cursor isn't there (which is also what I see during use): ![image](https://user-images.githubusercontent.com/343550/154822144-c3d105f9-77c5-4b07-84cb-c67717962265.png) and if I unfocus the window and print-screen the cursor isn't there: ![image](https://user-images.githubusercontent.com/343550/154822152-914fece1-fb0f-4503-accc-43c309c657a7.png) but if I snipping-tool the window while it is focused the cursor renders: ![image](https://user-images.githubusercontent.com/343550/154822159-10e37545-2a96-4d9b-ac6d-aab629f8fd9a.png) settings.json for reference: [settings.json.txt](https://github.com/microsoft/terminal/files/8103140/settings.json.txt)
claunia commented 2026-01-31 05:22:59 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Feb 20, 2022):

Your settings work for me:
image

I wonder how I can reproduce your issue...
It's especially concerning that your cursor shows up if the snipping tool is running, which suggests that something must work in Windows Terminal (otherwise it would be consistently invisible).

@lhecker commented on GitHub (Feb 20, 2022): Your settings work for me: ![image](https://user-images.githubusercontent.com/2256941/154823376-2a62e40c-d4f4-47c7-8312-4ce5644e6ef9.png) I wonder how I can reproduce your issue... It's especially concerning that your cursor shows up if the snipping tool is running, which suggests that something must work in Windows Terminal (otherwise it would be consistently invisible).
claunia commented 2026-01-31 05:22:59 +00:00
Author
Owner
Copy Link

@zamadatix commented on GitHub (Feb 20, 2022):

I think I bisected the issue, the trigger seems to be HDR. In this video I start the bottom monitor with HDR disabled and the top monitor with HDR enabled. The cursor blinks on the non-HDR monitor and stops blinking when the window is moved to the HDR monitor. If I enable HDR on the bottom monitor the issue occurs on both monitors:

https://user-images.githubusercontent.com/343550/154824156-f3d0cdf9-6684-4223-9db1-8ca2859d5906.mp4

Snipping tool takes a non-HDR snapshot of the display buffer during the "freeze-frame" where you can select the portion of the screen to snip. Print-screen on the other hand takes an immediate HDR copy of the output buffer. This explains why the 2 modes behaved differently.

Finally this occurs on a machine with an AMD GPU and a machine with an Nvidia GPU and does not change if software rendering is used. This makes me feel it's not a hardware/driver specific issue rather something with the experimental renderer and HDR directly.

@zamadatix commented on GitHub (Feb 20, 2022): I think I bisected the issue, the trigger seems to be HDR. In this video I start the bottom monitor with HDR disabled and the top monitor with HDR enabled. The cursor blinks on the non-HDR monitor and stops blinking when the window is moved to the HDR monitor. If I enable HDR on the bottom monitor the issue occurs on both monitors: https://user-images.githubusercontent.com/343550/154824156-f3d0cdf9-6684-4223-9db1-8ca2859d5906.mp4 Snipping tool takes a non-HDR snapshot of the display buffer during the "freeze-frame" where you can select the portion of the screen to snip. Print-screen on the other hand takes an immediate HDR copy of the output buffer. This explains why the 2 modes behaved differently. Finally this occurs on a machine with an AMD GPU and a machine with an Nvidia GPU and does not change if software rendering is used. This makes me feel it's not a hardware/driver specific issue rather something with the experimental renderer and HDR directly.
claunia commented 2026-01-31 05:22:59 +00:00
Author
Owner
Copy Link

@okibcn commented on GitHub (Feb 20, 2022):

If you don't mind, could you post your config file (a minimal one that reproduces your issue is enough), as well as a screenshot of your terminal while you've got input focus?

I am attaching the settings file and a screenshot of an active session. As you can see the cursor shows up in the capture, but it is not actually rendered on the screen. I am attaching the settings file. It fails both Windows Powershell and Powershell core.
It must be related to the screen resolution and bit depth. When I move the terminal window to another monitor without HDR 4K, it works perfectly both with the new experimental text rendering activated and deactivated. The system uses an Intel GPU, but as far as I read, it was duplicated also with AMD and Nvidia GPUs.

settings.json.txt
Win+S

@okibcn commented on GitHub (Feb 20, 2022): > If you don't mind, could you post your config file (a minimal one that reproduces your issue is enough), as well as a screenshot of your terminal while you've got input focus? I am attaching the settings file and a screenshot of an active session. As you can see the cursor shows up in the capture, but it is not actually rendered on the screen. I am attaching the settings file. It fails both Windows Powershell and Powershell core. It must be related to the screen resolution and bit depth. When I move the terminal window to another monitor without HDR 4K, it works perfectly both with the new experimental text rendering activated and deactivated. The system uses an Intel GPU, but as far as I read, it was duplicated also with AMD and Nvidia GPUs. [settings.json.txt](https://github.com/microsoft/terminal/files/8103287/settings.json.txt) ![Win+S](https://user-images.githubusercontent.com/22417711/154824681-2acd84fa-d329-4702-a8e9-d7a33d269e5e.jpg)
claunia commented 2026-01-31 05:22:59 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 25, 2022):

:tada:This issue was addressed in #12548, which has now been successfully released as Windows Terminal Preview v1.13.1073.🎉

Handy links:

@ghost commented on GitHub (Mar 25, 2022): :tada:This issue was addressed in #12548, which has now been successfully released as `Windows Terminal Preview v1.13.1073`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.13.1073) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-AtlasEngine Issue-Bug Needs-Attention Needs-Tag-Fix Priority-3 Product-Terminal Resolution-Fix-Committed
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#16795
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?