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

Input randomly gets ignored when applications wait for input #19671

New Issue
Open
opened 2026-01-31 06:50:20 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 06:50:20 +00:00
Owner
Copy Link

Originally created by @Gnbrkm41 on GitHub (Apr 8, 2023).

Windows Terminal version

1.17.1023

Windows build number

10.0.25330.0

Other Software

Powershell 7.4.0-preview.2

Steps to reproduce

Using Powershell, execute a program that waits for a user input (e.g. C#'s Console.ReadLine()).

There is no reliable reproduction steps, unfortunately (at least I haven't found any reliable way to do so) It really seems to happen randomly, and it has happened for... not exactly sure how long, the last 2 months or so?

Expected Behavior

Application should accept user inputs from keyboard just fine.

Actual Behavior

Any input made to that tab is ignored. This includes any sort of text input, and attempts to close the program using Ctrl+C is also ignored. If I open a new tab in the same terminal instance, that new tab would accept inputs just fine. There is no way to do anything about the seemingly frozen app; I need to close the offending tab and start all over again. (at least I haven't had it happen in a row, yet)

Some additional context:
I am using insider builds of Windows 11 Pro (Canary). Currently it's at 25330.
I am not using Remote Desktop.
I am using Windows' built-in Korean IME, the layout being Korean 101 key type 1 keyboard.

Regarding the TabletInputService service, I actually cannot locate the service under the name of 'Touch keyboard and handwriting service'; I found 'Text Input Management Service' instead which says it has to do with text inputs and touch keyboard so maybe it has changed its name in Windows 11? I haven't touched anything regarding that service, haven't ran any 'debloating' tools, do not have MSI Afterburner installed, and Terminal does not show any warnings about it (from what I've found it should show warnings when the service is not running? although I got Terminal from MS Store so maybe it wouldn't show that anyway). I think it's highly unlikely that this is the issue. ctfmon seems to be running just fine, which seems to be what really matters at the end. Plus, as I said above, it's only the offending tab that ignores inputs; if I open a new tab, I can type in just fine in that new tab, so it's not like inputs are not working all the time. I was able to type in the command to start executing that program in the first place!

There are three possible failure points I can see, one being the program itself, one being Powershell which I ran the command through, and the last one being the terminal. It's probably very unlikely that there is a problem with the program itself; I've had it happen with a program I wrote on my own, but also with well-known programs like FFMpeg. Not sure about Powershell and Terminal though. I am also not sure if this happens only when it's run through Powershell.

I understand this kind of problems are near impossible to diagnose on your side with no extra info. Is there any other useful debugging info I can provide (e.g. minidumps or full memory dumps)? I can try gathering extra info if someone could tell me what kind of stuffs I can do next time this happens.

Originally created by @Gnbrkm41 on GitHub (Apr 8, 2023). ### Windows Terminal version 1.17.1023 ### Windows build number 10.0.25330.0 ### Other Software Powershell 7.4.0-preview.2 ### Steps to reproduce Using Powershell, execute a program that waits for a user input (e.g. C#'s `Console.ReadLine()`). There is no reliable reproduction steps, unfortunately (at least I haven't found any reliable way to do so) It *really* seems to happen randomly, and it has happened for... not exactly sure how long, the last 2 months or so? ### Expected Behavior Application should accept user inputs from keyboard just fine. ### Actual Behavior Any input made to that tab is ignored. This includes any sort of text input, and attempts to close the program using Ctrl+C is also ignored. If I open a new tab in the same terminal instance, that new tab would accept inputs just fine. There is no way to do anything about the seemingly frozen app; I need to close the offending tab and start all over again. (at least I haven't had it happen in a row, *yet*) Some additional context: I am using insider builds of Windows 11 Pro (Canary). Currently it's at 25330. I am not using Remote Desktop. I am using Windows' built-in Korean IME, the layout being Korean 101 key type 1 keyboard. Regarding the TabletInputService service, I actually cannot locate the service under the name of 'Touch keyboard and handwriting service'; I found 'Text Input Management Service' instead which says it has to do with text inputs and touch keyboard so maybe it has changed its name in Windows 11? I haven't touched anything regarding that service, haven't ran any 'debloating' tools, do not have MSI Afterburner installed, and Terminal does not show any warnings about it (from what I've found it should show warnings when the service is not running? although I got Terminal from MS Store so maybe it wouldn't show that anyway). I think it's highly unlikely that this is the issue. ctfmon seems to be running just fine, which seems to be what really matters at the end. Plus, as I said above, it's only the offending tab that ignores inputs; if I open a new tab, I can type in just fine in that new tab, so it's not like inputs are not working all the time. I was able to type in the command to start executing that program in the first place! There are three possible failure points I can see, one being the program itself, one being Powershell which I ran the command through, and the last one being the terminal. It's probably very unlikely that there is a problem with the program itself; I've had it happen with a program I wrote on my own, but also with well-known programs like FFMpeg. Not sure about Powershell and Terminal though. I am also not sure if this happens only when it's run through Powershell. I understand this kind of problems are near impossible to diagnose on your side with no extra info. Is there any other useful debugging info I can provide (e.g. minidumps or full memory dumps)? I can try gathering extra info if someone could tell me what kind of stuffs I can do next time this happens.
claunia added the Needs-TriageIssue-BugNeeds-Author-Feedback labels 2026-01-31 06:50:20 +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 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#19671
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?