Cannot type at all | This has not got to do with touch keyboard

[Onyx-Official]

Issue

I cannot type at all on Windows Terminal. I have reset, repaired and reinstalled the app. I checked if the Touch keyboard service was enabled and it was. This is for all shells that windows terminal runs (Debain, Ubuntu, Powershell, and Cmd).

[zadjii-msft]

Can you give us any details about your system?

• Your Windows version number?
• The version number of the Terminal?
• Are you using remote desktop?
• What keyboard layout are you using?

There's nothing in your post that I can use to investigate this, nor is there anything differentiating your report from #4448 or #8045. I'm inclined to just close this because there's nothing actionable here.

[Onyx-Official]

Can you give us any details about your system?

• Your Windows version number?
• The version number of the Terminal?
• Are you using remote desktop?
• What keyboard layout are you using?

There's nothing in your post that I can use to investigate this, nor is there anything differentiating your report from #4448 or #8045. I'm inclined to just close this because there's nothing actionable here.

I am using a United States Keyboard layout (qwerty) my windows version number is 10.0.19042. My windows terminal version is the one available on the micrsosft store. I should also say my keyboard is a USB keyboard (ASUS Raygamore) and its only the windows terminal application it does not work on.

[Onyx-Official]

Can you give us any details about your system?

• Your Windows version number?
• The version number of the Terminal?
• Are you using remote desktop?
• What keyboard layout are you using?

There's nothing in your post that I can use to investigate this, nor is there anything differentiating your report from #4448 or #8045. I'm inclined to just close this because there's nothing actionable here.

I am using a United States Keyboard layout (qwerty) my windows version number is 10.0.19042. My windows terminal version is the one available on the micrsosft store. I should also say my keyboard is a USB keyboard (ASUS Raygamore) and its only the windows terminal application it does not work on.

I also forgot again, I can paste right click on my mouse

[Onyx-Official]

Can you give us any details about your system?

• Your Windows version number?
• The version number of the Terminal?
• Are you using remote desktop?
• What keyboard layout are you using?

There's nothing in your post that I can use to investigate this, nor is there anything differentiating your report from #4448 or #8045. I'm inclined to just close this because there's nothing actionable here.

I am using a United States Keyboard layout (qwerty) my windows version number is 10.0.19042. My windows terminal version is the one available on the micrsosft store. I should also say my keyboard is a USB keyboard (ASUS Raygamore) and its only the windows terminal application it does not work on.

I also forgot again, I can paste right click on my mouse

[zadjii-msft]

My windows terminal version is the one available on the micrsosft store.

FYI "The version available on the store" is not a useful version number. There's both Stable and Preview release channels available on the Store (with different version numbers), and the Store isn't always the most reliable at updating every user simultaneously. Sometimes it takes a few days for an update to roll out to everyone. So an actual version number would be important here.

Since there's nothing particularly unique about your setup, I'm just going to dupe this to the discussion in #8045. That's the new bucket for "mysteriously, we don't know why the Terminal isn't receiving keyboard input". Thanks!

/dup #8045

[ghost]

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!

[Onyx-Official]

My windows terminal version is the one available on the micrsosft store.

FYI "The version available on the store" is not a useful version number. There's both Stable and Preview release channels available on the Store (with different version numbers), and the Store isn't always the most reliable at updating every user simultaneously. Sometimes it takes a few days for an update to roll out to everyone. So an actual version number would be important here.

Since there's nothing particularly unique about your setup, I'm just going to dupe this to the discussion in #8045. That's the new bucket for "mysteriously, we don't know why the Terminal isn't receiving keyboard input". Thanks!

/dup #8045

SERVICE_NAME: TabletInputService
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

how do i enable this service?

[zadjii-msft]

1. In the run dialog, run services.msc
   

2. Find the "Touch Keyboard and Handwriting Panel Service"
   

3. Open the "Properties" for this service
   

4. Change the "startup type" to "Automatic"
   

5. Hit "Ok", and restart the PC.

[Onyx-Official]

I just typed in command but its fixed! Yay! Thanks @zadjii-msft !

[zadjii-msft]

Happy to help!

[androidacy-user]

That service keeps going back to manual for me, any idea why?

[cebaa]

@zadjii-msft No way to use Windows Terminal without this service? Asking because starting it requires admin privileges, which I don't have on the particular machine I'm trying to use Windows Terminal on.

[zadjii-msft]

Basically, no. Your admin shouldn't have disabled that service in the first place - it's a critical OS service

[cebaa]

@zadjii-msft

Your admin shouldn't have disabled that service in the first place - it's a critical OS service

I don't know why they disabled it, but it's unlikely they just blindly disabled it on a whim. My best guess is it's secops trying to minimize the attack surface. That kind of makes sense I guess, given these are desktops, so no need for anything touch-related. Another guess is perhaps they ran into an issue with remote access or some old piece of software or something along those lines. I bet there was a reason for them disabling it is my point I guess.

Calling it "a critical OS service" is quite a leap. Perhaps it's critical for Windows Terminal, but it's literally the only app that I've tried so far that required it. From my standpoint, it's pretty much the opposite of critical. Looking at the other thread, looks like I'm not the only one.

It's a shame, I really wanted to test WT today :) I hope you guys can get to the bottom of it on the other thread. Cheers!