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

Any shortcut prints random signs (even when window is not active) #23824

New Issue
Closed
opened 2026-01-31 08:53:36 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 08:53:36 +00:00
Owner
Copy Link

Originally created by @marcinbjorn on GitHub (Nov 22, 2025).

Windows Terminal version

1.25.3251.0

Windows build number

26100.7171

Other Software

No response

Steps to reproduce

Press any shortcut key (e.g., Ctrl+I, Ctrl+K, Alt+key)
Prints random signs on the terminal: "2R4R4R0R0R4R4R"
Repeat inside SSH or tmux — same behaviour
Press shortcuts while the WT window is not active — still reproduces

Expected Behavior

No output in the terminal

Actual Behavior

Unexpected terminal output: 2R4R4R0R0R4R4R or ;3R;6R;9R.

Originally created by @marcinbjorn on GitHub (Nov 22, 2025). ### Windows Terminal version 1.25.3251.0 ### Windows build number 26100.7171 ### Other Software _No response_ ### Steps to reproduce Press any shortcut key (e.g., Ctrl+I, Ctrl+K, Alt+key) Prints random signs on the terminal: "2R4R4R0R0R4R4R" Repeat inside SSH or tmux — same behaviour Press shortcuts while the WT window is not active — still reproduces ### Expected Behavior No output in the terminal ### Actual Behavior Unexpected terminal output: 2R4R4R0R0R4R4R or ;3R;6R;9R.
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 08:53:36 +00:00
claunia commented 2026-01-31 08:53:37 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Nov 24, 2025):

Please update your "Steps to reproduce" to include what you did before pressing those shortcut keys as I'm fairly certain you can't reproduce this in a plain "Command Prompt" profile.

@lhecker commented on GitHub (Nov 24, 2025): Please update your "Steps to reproduce" to include what you did before pressing those shortcut keys as I'm fairly certain you can't reproduce this in a plain "Command Prompt" profile.
claunia commented 2026-01-31 08:53:37 +00:00
Author
Owner
Copy Link

@marcinbjorn commented on GitHub (Nov 25, 2025):

You're right - I can't reproduce it in a plain Command Prompt profile either. The problem is that I’m not sure how to update the “Steps to reproduce” because this happens all the time, regardless of what I do beforehand.

It doesn’t matter whether the shortcut is a system shortcut or a Windows Terminal shortcut. WT reacts to almost any Ctrl or Alt key combination, but not Win key combinations. WT even displays a buffered shortcut: if I press a random shortcut while WT is closed and then launch it, the shortcut appears immediately before the Ubuntu profile loads.

It also happens on my second Redhat profile, which was installed about a year ago and hasn’t been touched since. I can’t reproduce it at all on stable WT 1.23.12811.0, only on Canary.

Because it triggers even with WT closed, I’m not sure what reliable steps I can list before “press shortcut.”

@marcinbjorn commented on GitHub (Nov 25, 2025): You're right - I can't reproduce it in a plain Command Prompt profile either. The problem is that I’m not sure how to update the “Steps to reproduce” because this happens all the time, regardless of what I do beforehand. It doesn’t matter whether the shortcut is a system shortcut or a Windows Terminal shortcut. WT reacts to almost any Ctrl or Alt key combination, but not Win key combinations. WT even displays a buffered shortcut: if I press a random shortcut while WT is closed and then launch it, the shortcut appears immediately before the Ubuntu profile loads. It also happens on my second Redhat profile, which was installed about a year ago and hasn’t been touched since. I can’t reproduce it at all on stable WT 1.23.12811.0, only on Canary. Because it triggers even with WT closed, I’m not sure what reliable steps I can list before “press shortcut.”
claunia commented 2026-01-31 08:53:38 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Nov 25, 2025):

The problem is that I’m not sure how to update the “Steps to reproduce” because this happens all the time, regardless of what I do beforehand.

But it doesn't happen all the time as you confirmed yourself. It only happens in specific profiles.

It also happens on my second Redhat profile, [...]

Does this imply your issue happens only with Ubuntu and Redhat profiles? Are you using WSL, SSH, etc.? Please be specific.

@lhecker commented on GitHub (Nov 25, 2025): > The problem is that I’m not sure how to update the “Steps to reproduce” because this happens all the time, regardless of what I do beforehand. But it doesn't happen all the time as you confirmed yourself. It only happens in specific profiles. > It also happens on my second Redhat profile, [...] Does this imply your issue happens only with Ubuntu and Redhat profiles? Are you using WSL, SSH, etc.? Please be specific.
claunia commented 2026-01-31 08:53:38 +00:00
Author
Owner
Copy Link

@marcinbjorn commented on GitHub (Nov 25, 2025):

I can reproduce it in:

  • All WSL profiles: Ubuntu and Red Hat
  • All SSH profiles: multiple remote hosts

I cannot reproduce it in:

  • PowerShell
  • Command Prompt

It also doesn’t happen with every shortcut, only some of them.

Example:

  • In a WSL profile, pressing Ctrl+I (bound to Terminal Chat) produces repeated output like:
    RRRRRRRRRRR0R1R2R0R0R2R4R6R6R0R2R6R8R0R0R4R

  • In an SSH profile, the same Ctrl+I prints sequences such as:
    ;16R;16R;16R;16R;20R;24R;32R;32R;40R;44R;44R;44R;18R;55R;72R;17R;1R;57R;66R

The only recent system change that could have affected this was installing AutoHotkey v2, but I have since uninstalled it and the issue still persists.

@marcinbjorn commented on GitHub (Nov 25, 2025): I can reproduce it in: - **All WSL profiles**: Ubuntu and Red Hat - **All SSH profiles**: multiple remote hosts I **cannot** reproduce it in: - **PowerShell** - **Command Prompt** It also doesn’t happen with every shortcut, only some of them. **Example:** - In a **WSL profile**, pressing **Ctrl+I** (bound to *Terminal Chat*) produces repeated output like: `RRRRRRRRRRR0R1R2R0R0R2R4R6R6R0R2R6R8R0R0R4R` - In an **SSH profile**, the same **Ctrl+I** prints sequences such as: `;16R;16R;16R;16R;20R;24R;32R;32R;40R;44R;44R;44R;18R;55R;72R;17R;1R;57R;66R` The only recent system change that could have affected this was installing **AutoHotkey v2**, but I have since **uninstalled** it and the issue still persists.
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 Issue-Bug Needs-Attention Needs-Triage
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#23824
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?