Ctrl key can be stuck in Windows Terminal #18830

Closed
opened 2026-01-31 06:25:39 +00:00 by claunia · 4 comments
Owner

Originally created by @devlie on GitHub (Nov 4, 2022).

Windows Terminal version

1.15.2875.0

Windows build number

10.0.25231.1000

Other Software

No response

Steps to reproduce

I don't have concrete repro steps. I'm just using running cmd.exe inside Windows Terminal Preview as usual.

Expected Behavior

Ctrl key is not stuck.

Actual Behavior

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 (Nov 4, 2022). ### Windows Terminal version 1.15.2875.0 ### Windows build number 10.0.25231.1000 ### Other Software _No response_ ### Steps to reproduce I don't have concrete repro steps. I'm just using running cmd.exe inside Windows Terminal Preview as usual. ### Expected Behavior `Ctrl` key is not stuck. ### Actual Behavior 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 Issue-BugResolution-Duplicate labels 2026-01-31 06:25:39 +00:00
Author
Owner

@lhecker commented on GitHub (Nov 5, 2022):

Wow that sounds eerily similar to #14338, which was submitted just hours ago.

@lhecker commented on GitHub (Nov 5, 2022): Wow that sounds eerily similar to #14338, which was submitted just hours ago.
Author
Owner

@zadjii-msft commented on GitHub (Nov 7, 2022):

I'm gonna go out on a limb and guess that this is the same root cause as #14345. We'll tentatively call this a dupe for now, push out a hotfix, and if that release doesn't fix this, we can reopen. Thanks!

/dup #14129

@zadjii-msft commented on GitHub (Nov 7, 2022): I'm gonna go out on a limb and guess that this is the same root cause as #14345. We'll tentatively call this a dupe for now, push out a hotfix, and if that release doesn't fix this, we can reopen. Thanks! /dup #14129
Author
Owner

@ghost commented on GitHub (Nov 7, 2022):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Nov 7, 2022): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Author
Owner

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

@zadjii-msft I'm still reproing this issue on WT Preview 1.17.1023. That build should have the fix for this issue, right?

@devlie commented on GitHub (Feb 14, 2023): @zadjii-msft I'm still reproing this issue on WT Preview 1.17.1023. That build should have the fix for this issue, right?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#18830