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

Not accepting keystrokes #11337

New Issue
Open
opened 2026-01-31 02:44:53 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 02:44:53 +00:00
Owner
Copy Link

Originally created by @opensslonzos-github on GitHub (Nov 11, 2020).

After the Windows update on 11/10, my machine restarted and now the Windows Terminal does not accept keystrokes.
I have tried all forms of input that I can think of including running OSK (on screen keyboard).
I can type into every other application on my system except Windows Terminal
I can drop down the menu containing "About",. "Settings", and all of the configured terminals I have. Once that is down, I can move up and down with arrows. I can select a terminal to open and a new window will be created and it will run whatever is configured to run (OpenSSH, PowerShell, CMD.exe) which will start up in a new tab as expected.
Once the tab is up and running, no keys are passed into the shell.
I have tried Powershell, CMD.exe and OpenSSH. None of them are getting anything I type.
Nothing.

Environment

Windows build number:   Win32NT             10.0.19041.0 Microsoft Windows NT 10.0.19041.0
Windows Terminal version (if applicable): 1.3.2651.0
Any other software?  I am a developer, so Visual Studio and about a hundred other things. None of them have updated recently.

Steps to reproduce

Start Windows Terminal. Allow the default window to be created (which is powershell for me)
Type "dir" or "ls" or anything. Nothing is echoed to the terminal window.
Run OSK and use it to type characters into the Windows Terminal window. Nothing happens.
Run Notepad. Type letters. All works as expected. I see letters appear in Notepad.
Run Powershell by itself (not inside Windows Terminal). All works as expected. Commands run, letters are echoed. Joy
Run CMD.exe by itself (not inside Windows Terminal). All works as expected. Commands run, letters are echoed. Joy

Expected behavior

Powershell starts normally and is sitting waiting for me to type a command.
There is a blinking cursor there.
I can select the text in the window.
I expect to type commands into the shell, see the commands echoed to the terminal and have them execute.

Actual behavior

Shell starts fine.
When I type, no characters appear in the shell, so no actions are taken.

Originally created by @opensslonzos-github on GitHub (Nov 11, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> After the Windows update on 11/10, my machine restarted and now the Windows Terminal does not accept keystrokes. I have tried all forms of input that I can think of including running OSK (on screen keyboard). I can type into every other application on my system except Windows Terminal I can drop down the menu containing "About",. "Settings", and all of the configured terminals I have. Once that is down, I can move up and down with arrows. I can select a terminal to open and a new window will be created and it will run whatever is configured to run (OpenSSH, PowerShell, CMD.exe) which will start up in a new tab as expected. Once the tab is up and running, no keys are passed into the shell. I have tried Powershell, CMD.exe and OpenSSH. None of them are getting anything I type. Nothing. <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ``` Windows build number: Win32NT 10.0.19041.0 Microsoft Windows NT 10.0.19041.0 Windows Terminal version (if applicable): 1.3.2651.0 Any other software? I am a developer, so Visual Studio and about a hundred other things. None of them have updated recently. ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> Start Windows Terminal. Allow the default window to be created (which is powershell for me) Type "dir" or "ls" or anything. Nothing is echoed to the terminal window. Run OSK and use it to type characters into the Windows Terminal window. Nothing happens. Run Notepad. Type letters. All works as expected. I see letters appear in Notepad. Run Powershell by itself (not inside Windows Terminal). All works as expected. Commands run, letters are echoed. Joy Run CMD.exe by itself (not inside Windows Terminal). All works as expected. Commands run, letters are echoed. Joy # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> Powershell starts normally and is sitting waiting for me to type a command. There is a blinking cursor there. I can select the text in the window. I expect to type commands into the shell, see the commands echoed to the terminal and have them execute. # Actual behavior Shell starts fine. When I type, no characters appear in the shell, so no actions are taken.
claunia added the Resolution-Duplicate label 2026-01-31 02:44:53 +00:00
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 Resolution-Duplicate
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#11337
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?