Cannot type or interact with terminal #10391

Closed
opened 2026-01-31 02:20:21 +00:00 by claunia · 10 comments
Owner

Originally created by @lucasyvas on GitHub (Aug 29, 2020).

Environment

Windows build number:  Win32NT 10.0.19041.0 Microsoft Windows NT 10.0.19041.0
Windows Terminal version (if applicable): Version: 1.2.2381.0

Steps to reproduce

Try to type or click into the terminal

Expected behavior

Can type characters in the terminal, right-click, etc.

Actual behavior

Cannot type any character or interact with the terminal in any way. Previously it worked fine, but something has changed and now I cannot do anything with the terminal.

Originally created by @lucasyvas on GitHub (Aug 29, 2020). # Environment ```none Windows build number: Win32NT 10.0.19041.0 Microsoft Windows NT 10.0.19041.0 Windows Terminal version (if applicable): Version: 1.2.2381.0 ``` # Steps to reproduce Try to type or click into the terminal # Expected behavior Can type characters in the terminal, right-click, etc. # Actual behavior Cannot type any character or interact with the terminal in any way. Previously it worked fine, but something has changed and now I cannot do anything with the terminal.
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 02:20:21 +00:00
Author
Owner

@KalleOlaviNiemitalo commented on GitHub (Aug 29, 2020):

https://github.com/microsoft/terminal/issues/4448 suggests that disabling "Touch Keyboard and Handwriting Panel Service" could cause this.

@KalleOlaviNiemitalo commented on GitHub (Aug 29, 2020): <https://github.com/microsoft/terminal/issues/4448> suggests that disabling "Touch Keyboard and Handwriting Panel Service" could cause this.
Author
Owner

@lucasyvas commented on GitHub (Aug 30, 2020):

@KalleOlaviNiemitalo Thanks for the suggestion, but that service is already set to Manual and has the recommended default registry values from that post. I've not ever messed with that.

@lucasyvas commented on GitHub (Aug 30, 2020): @KalleOlaviNiemitalo Thanks for the suggestion, but that service is already set to Manual and has the recommended default registry values from that post. I've not ever messed with that.
Author
Owner

@FenderBaba commented on GitHub (Sep 1, 2020):

#4448 suggests that disabling "Touch Keyboard and Handwriting Panel Service" could cause this.

Thanks a lot !
That was the tip. Everything is ok now.

@FenderBaba commented on GitHub (Sep 1, 2020): > #4448 suggests that disabling "Touch Keyboard and Handwriting Panel Service" could cause this. Thanks a lot ! That was the tip. Everything is ok now.
Author
Owner

@DHowett commented on GitHub (Sep 3, 2020):

@lucasyvas If you explicitly start that service, does keyboard input start working?

@DHowett commented on GitHub (Sep 3, 2020): @lucasyvas If you explicitly _start_ that service, does keyboard input start working?
Author
Owner

@FenderBaba commented on GitHub (Sep 3, 2020):

After, enable the Ink Workspace and the Tablet Input Service again, the Terminal works as it should. It's strange to understand, why this 2 services should be enabled on a pure Desktop machine.
Because i was looking for un-needed resource eater on my DAW, I did this "cleanup task" to disable some services, and the receipt followed immediately: "punishment after self-experiment".

@FenderBaba commented on GitHub (Sep 3, 2020): After, enable the **Ink Workspace** and the **Tablet Input Service** again, the Terminal works as it should. It's strange to understand, why this 2 services should be enabled on a pure Desktop machine. Because i was looking for un-needed resource eater on my DAW, I did this "cleanup task" to disable some services, and the receipt followed immediately: "punishment after self-experiment".
Author
Owner

@lucasyvas commented on GitHub (Sep 6, 2020):

@DHowett Nope... is it possible this is permission related? I may have recently altered some innocuous looking Windows privacy settings, but that's all I can think off.

@lucasyvas commented on GitHub (Sep 6, 2020): @DHowett Nope... is it possible this is permission related? I may have recently altered some innocuous looking Windows privacy settings, but that's all I can think off.
Author
Owner

@lucasyvas commented on GitHub (Sep 6, 2020):

OK weird it now works. Everything looks the same but I did it once more and tossed in a reboot for good measure. Maybe at that to the list of recommended steps after flipping all the correct switches :)

Edit: NO... stopped working again. When bringing the computer out of sleep, it stops working again. Thoughts? If we assume the service is the culprit...

image

I cannot actually stop or start the service now either. I can set it to disabled and back, but no ability to start/stop.

@lucasyvas commented on GitHub (Sep 6, 2020): OK weird it now works. Everything looks the same but I did it once more and tossed in a reboot for good measure. Maybe at that to the list of recommended steps after flipping all the correct switches :) **Edit**: NO... stopped working again. When bringing the computer out of sleep, it stops working again. Thoughts? If we assume the service is the culprit... ![image](https://user-images.githubusercontent.com/3365616/92332355-41ba9780-f032-11ea-983a-22044a16df12.png) I cannot actually stop or start the service now either. I can set it to disabled and back, but no ability to start/stop.
Author
Owner

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

That's really quite strange, and I'm not sure where to go from here.

Somebody mentioned that they've got MSI Afterburner running, and exiting it made input start working again. That doesn't seem like a completely reasonable thing to do, but ... you know. Software is rarely reasonable!

@DHowett commented on GitHub (Sep 10, 2020): That's really quite strange, and I'm not sure where to go from here. Somebody mentioned that they've got MSI Afterburner running, and exiting it made input start working again. That doesn't seem like a completely reasonable thing to do, but ... you know. Software is rarely reasonable!
Author
Owner

@lucasyvas commented on GitHub (Sep 10, 2020):

I'll take a look at what else is running and report back. I'd like to avoid turning this into a "tech support" issue for everyone's sake, but just trying to get through the weeds.

@lucasyvas commented on GitHub (Sep 10, 2020): I'll take a look at what else is running and report back. I'd like to avoid turning this into a "tech support" issue for everyone's sake, but just trying to get through the weeds.
Author
Owner

@lucasyvas commented on GitHub (Sep 14, 2020):

I believe this is caused by running Rivatuner Statistics Server in my case, which is a utility that caps framerate to smooth frame times.

@lucasyvas commented on GitHub (Sep 14, 2020): I believe this is caused by running Rivatuner Statistics Server in my case, which is a utility that caps framerate to smooth frame times.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#10391