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

Ctrl key can be stuck in Windows Terminal #19451

New Issue
Closed
opened 2026-01-31 06:43:42 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 06:43:42 +00:00
Owner
Copy Link

Originally created by @devlie on GitHub (Feb 24, 2023).

Windows Terminal version

1.17.1023

Windows build number

10.0.25300.1000

Other Software

No response

Steps to reproduce

Not sure. Most of the time I'm just typing typical stuffs.

Expected Behavior

Ctrl key is not stuck.

Actual Behavior

I'm reopening #14343, which was suspected to be dupe of #14345/#14129, but those are supposedly fixed on the build I'm on.

After some times, Ctrl key will be stuck for a particular tab. I usually find out when hitting Backspace would delete the whole word even though I'm not pressing down Ctrl key, or typing some alphabets would produce something like ^A

I'm positive the problem is scoped to a Terminal tab:

  • If I open a new tab, the issue doesn't persist.
  • The problem doesn't repro on Windows Run dialog (WIN+R) while issue is happening.
Originally created by @devlie on GitHub (Feb 24, 2023). ### Windows Terminal version 1.17.1023 ### Windows build number 10.0.25300.1000 ### Other Software _No response_ ### Steps to reproduce Not sure. Most of the time I'm just typing typical stuffs. ### Expected Behavior `Ctrl` key is not stuck. ### Actual Behavior I'm reopening #14343, which was suspected to be dupe of #14345/#14129, but those are supposedly fixed on the build I'm on. After some times, Ctrl key will be stuck for a particular tab. I usually find out when hitting Backspace would delete the whole word even though I'm not pressing down Ctrl key, or typing some alphabets would produce something like ^A I'm positive the problem is scoped to a Terminal tab: - If I open a new tab, the issue doesn't persist. - The problem doesn't repro on Windows Run dialog (WIN+R) while issue is happening.
claunia added the Needs-TriageIssue-BugNeeds-Author-Feedback labels 2026-01-31 06:43:43 +00:00
claunia commented 2026-01-31 06:43:44 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Feb 25, 2023):

Can you try the solution of the other issue that was linked (#14338)? In other words, if you're using PowerShell, try running this:

echo "`e[?67;9999l"
@lhecker commented on GitHub (Feb 25, 2023): Can you try the solution of the other issue that was linked (#14338)? In other words, if you're using PowerShell, try running this: ```pwsh echo "`e[?67;9999l" ```
claunia commented 2026-01-31 06:43:44 +00:00
Author
Owner
Copy Link

@devlie commented on GitHub (Feb 27, 2023):

@lhecker / @j4james what's the command for cmd.exe? I'm reproing this issue in regular cmd, not just powershell. I tried those on cmd and it didn't work so I figured the escape chars might be different.

@devlie commented on GitHub (Feb 27, 2023): @lhecker / @j4james what's the command for cmd.exe? I'm reproing this issue in regular cmd, not just powershell. I tried those on cmd and it didn't work so I figured the escape chars might be different.
claunia commented 2026-01-31 06:43:44 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Feb 27, 2023):

In the cmd shell you can use the echo command with no quotes, but you need to press Ctrl+[ to get an escape, then follow that with [?67;9999l. The escape will show up as ^[, so the full command will look like this:

echo ^[[?67;9999l
@j4james commented on GitHub (Feb 27, 2023): In the cmd shell you can use the `echo` command with no quotes, but you need to press <kbd>Ctrl</kbd>+<kbd>[</kbd> to get an escape, then follow that with `[?67;9999l`. The escape will show up as `^[`, so the full command will look like this: echo ^[[?67;9999l
claunia commented 2026-01-31 06:43:44 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Feb 27, 2023):

I'm just thinking it might also help opening the shell with a debug tap, so we can see what key sequences the terminal is generating.

@j4james commented on GitHub (Feb 27, 2023): I'm just thinking it might also help opening the shell with a [debug tap](https://github.com/microsoft/terminal/wiki/Enabling-the-debug-tap), so we can see what key sequences the terminal is generating.
claunia commented 2026-01-31 06:43:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 1, 2023):

(OP responded to us on an internal mail thread - we're waiting for another repro to get the text of a debug tap. I didn't see any ?67h's in the output of the tap, but I was just scanning a screenshot. There were a couple git commands around the time of the repro, maybe there's some other API that triggers it?)

@zadjii-msft commented on GitHub (Mar 1, 2023): (OP responded to us on an internal mail thread - we're waiting for another repro to get the text of a debug tap. I didn't see any `?67h`'s in the output of the tap, but I was just scanning a screenshot. There were a couple git commands around the time of the repro, maybe there's some other API that triggers it?)
claunia commented 2026-01-31 06:43:45 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Mar 1, 2023):

Bear in mind that the issue reported by the OP was that the Ctrl key was stuck in general, e.g. seeing ^A when typing an A, so it's not just BkSp becoming Ctrl+BkSp. That makes me think it's unlikely to be related to DECBKM.

@j4james commented on GitHub (Mar 1, 2023): Bear in mind that the issue reported by the OP was that the <kbd>Ctrl</kbd> key was stuck in general, e.g. seeing `^A` when typing an <kbd>A</kbd>, so it's not just <kbd>BkSp</kbd> becoming <kbd>Ctrl</kbd>+<kbd>BkSp</kbd>. That makes me think it's unlikely to be related to `DECBKM`.
claunia commented 2026-01-31 06:43:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 10, 2023):

OP replied in email and this issue hasn't come back since they recently paved their machine. We'll close till it comes back (if it ever does)

@zadjii-msft commented on GitHub (Mar 10, 2023): OP replied in email and this issue hasn't come back since they recently paved their machine. We'll close till it comes back (if it ever does)
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-Author-Feedback 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#19451
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?