No keyboard input #4448

privacyguy123 · 2020-02-03T15:13:36Z

You may experience an issue with Windows Terminal where keyboard input does not work. By and large, we've determined that this is caused by the "Touch Keyboard and Handwriting Service" being disabled.

If you're hitting this issue, make sure that the "Touch Keyboard and Handwriting Service" is not disabled. Certain "de-bloating" software (and apparently MSI Afterburner) likes to disable it or suppress it in the name of making your machine less understandable and "faster".

If you're experiencing an input issue that is not helped by exiting MSI Afterburner or re-enabling the "Touch Keyboard and Handwriting Service", please file a new issue.

Original issue content

Latest version of Windows Terminal.

Tried clean installing multiple times, keyboard input works on everything else (as I am typing with it here ...) yes that includes powershell.exe and cmd.exe.

What gives?

korotky · 2020-09-09T14:41:27Z

On my system(Win10 x64 19041.508) running MSI Afterburner 4.6.2 beta 2 disables input in Windows terminal. Closing this app resolves problem.

OlivierDoriath · 2020-09-13T15:39:53Z

I confirm that I was able to prevent the bug by

setting TabletInputService (Touch Keyboard and Handwriting Panel Service) from Disabled to Manual;

setting HKLM\SOFTWARE\Microsoft\Input values back to their prior values (above); and,

rebooting.

Now I have yet another seeminly unnecessary service running, but Terminal is working. 🎉
Off-topic: I'd pay good money for a first-party way to slim down Windows to just the bare essentials, then add things back as needed, with ultra-fine granularity. Call it Windows 10 Modular. I used to run a 'workstationized' Windows Server for this purpose, but that's not possible these days, as I need to run a few things that are specific to non-Server Windows.
@zadjii-msft IIRC, the only UWP application I had a problem with was Terminal. The others worked.

I can confirm enabling that service completely fixes the problem, without creating any other problem. Thanks a lot @sharpjs for that find!

On a side note, this also seems to fix the emoji panel showing up but not working issue!

DHowett · 2020-09-22T18:20:30Z

No, in order to make your system work you must enable the service that everyone is talking about. Recommending that people set InputServiceEnabled to 0 in the registry is dangerous.

UtmostCreator · 2020-09-22T18:22:07Z

But it was a default setup, and it did not work, let me try once again.

UtmostCreator · 2020-09-22T18:24:25Z

After I reloaded my PC, it does not work.

DHowett · 2020-09-22T18:25:17Z

What is the status of the touch keyboard and handwriting service?

UtmostCreator · 2020-09-22T18:26:37Z

Startup type is set to "Disabled"

DHowett · 2020-09-22T18:27:27Z

Set it to something other than disabled. That is what the last 15 comments on this thread are about.

UtmostCreator · 2020-09-22T18:28:57Z

Yeah, Sorry about it 😞.

Thank you so much for this. Should I delete my comments?

DHowett · 2020-09-22T18:30:57Z

I will handle cleanup. Thank you!

benfavre · 2020-10-10T09:38:39Z

On my system(Win10 x64 19041.508) running MSI Afterburner 4.6.2 beta 2 disables input in Windows terminal. Closing this app resolves problem.

Same here

DHowett · 2020-10-11T01:52:54Z

@LoboTormenta This is not the repository for VSCode or Manjaro. Even though it has "Terminal" in the name, it is not the catch-all repository for filing issues on terminals in general.

DHowett · 2020-10-11T01:55:25Z

Since this thread has run its course and has a known root cause, and people have taken to driving by to say unkind things to/about us (hi @benfavre, thank you for deleting your comment), I'm going to lock this thread.

If you're hitting this issue, make sure that the "Touch Keyboard and Handwriting Service" is not disabled. Certain "de-bloating" software (and apparently MSI Afterburner) likes to disable it or suppress it in the name of making your machine less understandable and "faster".

If you're experiencing an input issue that is not helped by exiting MSI Afterburner or re-enabling the "Touch Keyboard and Handwriting Service", please file a new issue.

@cornem

This changes the keyboard warning from a dialog to an `InfoBar`, which we just got in MUX 2.5. Some users were unhappy that we'd always display the dialog. We learned from the input team that this service _should_ always be enabled. We're also learing from users that they don't always want it enabled. We're working with the Input team to help us figure out how this service can be disabled _and the Terminal work just fine_. They're confident that it _shouldn't_. For 99% of our users, they're right. So we don't want to get rid of the dialog entirely, we want to understand how this is possible. While we wait, let's make the message less aggressive. This is instead of making a `iKnowWhatImDoingDisableTheKeyboardWarning` setting to disable the dialog. Props to @cornem for suggesting the less aggressive solution. ## Validation Steps Performed Tested manually, but by forcing the message to always display. Disabling the service requires two full reboots, and _ain't nobody got time for that_. Closes #8228 Closes #4448, for now

@cornem

This changes the keyboard warning from a dialog to an `InfoBar`, which we just got in MUX 2.5. Some users were unhappy that we'd always display the dialog. We learned from the input team that this service _should_ always be enabled. We're also learing from users that they don't always want it enabled. We're working with the Input team to help us figure out how this service can be disabled _and the Terminal work just fine_. They're confident that it _shouldn't_. For 99% of our users, they're right. So we don't want to get rid of the dialog entirely, we want to understand how this is possible. While we wait, let's make the message less aggressive. This is instead of making a `iKnowWhatImDoingDisableTheKeyboardWarning` setting to disable the dialog. Props to @cornem for suggesting the less aggressive solution. ## Validation Steps Performed Tested manually, but by forcing the message to always display. Disabling the service requires two full reboots, and _ain't nobody got time for that_. Closes #8228 Closes #4448, for now (cherry picked from commit ff5b2b8)

@cornem

This changes the keyboard warning from a dialog to an `InfoBar`, which we just got in MUX 2.5. Some users were unhappy that we'd always display the dialog. We learned from the input team that this service _should_ always be enabled. We're also learing from users that they don't always want it enabled. We're working with the Input team to help us figure out how this service can be disabled _and the Terminal work just fine_. They're confident that it _shouldn't_. For 99% of our users, they're right. So we don't want to get rid of the dialog entirely, we want to understand how this is possible. While we wait, let's make the message less aggressive. This is instead of making a `iKnowWhatImDoingDisableTheKeyboardWarning` setting to disable the dialog. Props to @cornem for suggesting the less aggressive solution. ## Validation Steps Performed Tested manually, but by forcing the message to always display. Disabling the service requires two full reboots, and _ain't nobody got time for that_. Closes microsoft#8228 Closes microsoft#4448, for now

ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Feb 3, 2020