Typing in search pop-up stopped working #23588

Closed
opened 2026-01-31 08:46:33 +00:00 by claunia · 7 comments
Owner

Originally created by @AndrejMitrovic on GitHub (Sep 4, 2025).

Windows Terminal version

1.22.12111.0

Windows build number

10.0.19045.6216

Other Software

No response

Steps to reproduce

The search command CTRL+SHIFT+F no longer accepts any keyboard input. I can still use the mouse to manually paste in text from the clipboard. But typing doesn't enter any characters in the input box.

I'm not sure how to debug this, any advice?

Expected Behavior

No response

Actual Behavior

Typing doesn't enter any characters in the input box.

Originally created by @AndrejMitrovic on GitHub (Sep 4, 2025). ### Windows Terminal version 1.22.12111.0 ### Windows build number 10.0.19045.6216 ### Other Software _No response_ ### Steps to reproduce The search command `CTRL+SHIFT+F` no longer accepts any keyboard input. I can still use the mouse to manually paste in text from the clipboard. But typing doesn't enter any characters in the input box. I'm not sure how to debug this, any advice? ### Expected Behavior _No response_ ### Actual Behavior Typing doesn't enter any characters in the input box.
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 08:46:33 +00:00
Author
Owner

@DHowett commented on GitHub (Sep 10, 2025):

Huh. When your terminal was in this state, were you still able to type into other text boxes (like the command palette, Ctrl+Shift+P) or the terminal itself?

@DHowett commented on GitHub (Sep 10, 2025): Huh. When your terminal was in this state, were you still able to type into other text boxes (like the command palette, <kbd>Ctrl+Shift+P</kbd>) or the terminal itself?
Author
Owner

@AndrejMitrovic commented on GitHub (Sep 11, 2025):

I can confirm I cannot type into the command palette either.

@AndrejMitrovic commented on GitHub (Sep 11, 2025): I can confirm I cannot type into the command palette either.
Author
Owner

@jamespack commented on GitHub (Sep 15, 2025):

Are you running terminal as admin? There is a very weird hang in some cases that deals with theming and differences between the logged in user and the user running the terminal. I'm pretty sure there is an open issue for it.

@jamespack commented on GitHub (Sep 15, 2025): Are you running terminal as admin? There is a very weird hang in some cases that deals with theming and differences between the logged in user and the user running the terminal. I'm pretty sure there is an open issue for it.
Author
Owner

@AndrejMitrovic commented on GitHub (Sep 16, 2025):

No, it happens in a regular terminal instance.

Is there an easy way for me to revert to a previous version so I can pinpoint the regression? I've installed the Terminal using the Store.

@AndrejMitrovic commented on GitHub (Sep 16, 2025): No, it happens in a regular terminal instance. Is there an easy way for me to revert to a previous version so I can pinpoint the regression? I've installed the Terminal using the Store.
Author
Owner

@AndrejMitrovic commented on GitHub (Sep 16, 2025):

Ok solved this, it looks like the "Touch Keyboard and Handwriting Panel Service" was deactivated, re-activating the service fixed it. Thanks all~

@AndrejMitrovic commented on GitHub (Sep 16, 2025): Ok solved this, it looks like the "Touch Keyboard and Handwriting Panel Service" was deactivated, re-activating the service fixed it. Thanks all~
Author
Owner

@DHowett commented on GitHub (Sep 16, 2025):

Thanks for following up!

We used to display a warning if we detected that this service was disabled. We removed that warning because some users found it very upsetting that we might tell them what to do. :)

@DHowett commented on GitHub (Sep 16, 2025): Thanks for following up! We used to display a warning if we detected that this service was disabled. We removed that warning because some users found it very upsetting that we might tell them what to do. :)
Author
Owner

@AndrejMitrovic commented on GitHub (Sep 16, 2025):

Oh the warning is there, it showed up after I reinstalled. I think I must have missed the warning the first time around and then it never re-appeared. No worries, thanks for your patience and your work!

@AndrejMitrovic commented on GitHub (Sep 16, 2025): Oh the warning is there, it showed up after I reinstalled. I think I must have missed the warning the first time around and then it never re-appeared. No worries, thanks for your patience and your work!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#23588