microsoft / microsoft/terminal
Mouse pointer flickers/disappears and selection/copy hangs in plain PowerShell
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 105k
- Forks
- 9.6k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 29
Description
Windows Terminal version
1.24.11911.0 (Stable); 1.25.1912.0 (Preview)
Windows build number
Windows 11 Pro 25H2, 10.0.26200.9168
Other Software
- Plain Windows PowerShell 5.1 (no WSL, SSH, Codex, Claude Code, vim, or other TUI)
- NVIDIA GeForce RTX 5070 Ti, driver 610.88
- Intel integrated GPU
- ToDesk Virtual Display Adapter
- Multiple monitors with mixed 180 Hz / 60 Hz refresh rates and landscape / portrait orientations
- ToDesk, Wallpaper Engine, and Armoury Crate are installed/running
Steps to reproduce
- Open Windows Terminal Stable or Windows Terminal Preview.
- Start a fresh plain Windows PowerShell tab.
- Move the mouse pointer from outside the window into the terminal content area.
- Move the pointer around or drag across text to select it.
- Try to copy the selection.
The problem reproduces immediately after starting Terminal and after a reboot. No terminal application or TUI is required.
Expected Behavior
The mouse pointer should remain visible and stable. Text selection and copy should complete normally without flickering, hanging, or losing the selection.
Actual Behavior
As soon as the mouse enters the terminal content area, the pointer starts flickering and intermittently disappears. Dragging to select text causes additional flashing; selection/copy can stop rendering or hang, and the copied content may not appear.
The issue reproduces in both Stable and Preview.
| Host / configuration | Result |
|---|---|
| Windows Terminal 1.24.11911.0 | Reproduces |
| Windows Terminal Preview 1.25.1912.0 | Reproduces |
| Classic Console Host (conhost.exe) | Does not reproduce |
| Windows Terminal software rendering enabled | Reproduces |
| Windows Terminal software rendering disabled | Reproduces |
| HAGS enabled / disabled | Reproduces |
| MPO default / disabled through OverlayTestMode | Reproduces |
Additional observations:
- Terminal settings are close to defaults; Acrylic/transparency is not enabled.
- Windows clipboard APIs work normally outside Windows Terminal.
- There are no observed Terminal renderer crashes, GPU reset events, or DWM crashes.
- This does not appear to be the OSC 52 deadlock in #20467: the reproduction uses a fresh plain PowerShell tab and no application emits OSC 52.
- A 21-second screen recording is attached below.
https://github.com/user-attachments/assets/61015237-6fa8-4aaa-8a40-5e8b7f5ad7d5
https://github.com/user-attachments/assets/d6b5427d-151d-44b7-91b7-367d73ef65c5
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. First reproduce in Windows Terminal Stable or Preview with a fresh plain PowerShell tab, then compare the behavior with conhost.exe and the listed rendering, HAGS, and MPO configurations. Done means the pointer remains stable and text selection and copying complete normally in the reported setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, powershell
- Domain
- cli, computer-graphics, desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100