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

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

New Issue
Closed
opened 2026-01-31 02:42:40 +00:00 by claunia · 14 comments
claunia commented 2026-01-31 02:42:40 +00:00
Owner
Copy Link

Originally created by @Onyx-Official on GitHub (Nov 2, 2020).

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).
Originally created by @Onyx-Official on GitHub (Nov 2, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # 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). ``` <!-- What's actually happening? -->
claunia added the Resolution-Duplicate label 2026-01-31 02:42:40 +00:00
claunia commented 2026-01-31 02:42:41 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 2, 2020):

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.

@zadjii-msft commented on GitHub (Nov 2, 2020): 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.
claunia commented 2026-01-31 02:42:41 +00:00
Author
Owner
Copy Link

@Onyx-Official commented on GitHub (Nov 2, 2020):

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 commented on GitHub (Nov 2, 2020): > 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.
claunia commented 2026-01-31 02:42:42 +00:00
Author
Owner
Copy Link

@Onyx-Official commented on GitHub (Nov 2, 2020):

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 commented on GitHub (Nov 2, 2020): > > 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
claunia commented 2026-01-31 02:42:42 +00:00
Author
Owner
Copy Link

@Onyx-Official commented on GitHub (Nov 2, 2020):

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 commented on GitHub (Nov 2, 2020): > > 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
claunia commented 2026-01-31 02:42:42 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 2, 2020):

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

@zadjii-msft commented on GitHub (Nov 2, 2020): > 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
claunia commented 2026-01-31 02:42:42 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 2, 2020):

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!

@ghost commented on GitHub (Nov 2, 2020): 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!
claunia commented 2026-01-31 02:42:43 +00:00
Author
Owner
Copy Link

@Onyx-Official commented on GitHub (Nov 2, 2020):

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?

@Onyx-Official commented on GitHub (Nov 2, 2020): > > 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?
claunia commented 2026-01-31 02:42:43 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 2, 2020):

  1. In the run dialog, run services.msc
    image

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

  3. Open the "Properties" for this service
    image

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

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

@zadjii-msft commented on GitHub (Nov 2, 2020): 1. In the run dialog, run `services.msc` ![image](https://user-images.githubusercontent.com/18356694/97891741-c81eed00-1cf4-11eb-9d48-7b94fede5294.png) 2. Find the "Touch Keyboard and Handwriting Panel Service" ![image](https://user-images.githubusercontent.com/18356694/97891813-e1279e00-1cf4-11eb-91c8-69a5c6da6c3d.png) 3. Open the "Properties" for this service ![image](https://user-images.githubusercontent.com/18356694/97891923-03212080-1cf5-11eb-90cc-821a4fbf16ba.png) 4. Change the "startup type" to "Automatic" ![image](https://user-images.githubusercontent.com/18356694/97892043-25b33980-1cf5-11eb-8833-a2e65a306a79.png) 5. Hit "Ok", and restart the PC.
claunia commented 2026-01-31 02:42:43 +00:00
Author
Owner
Copy Link

@Onyx-Official commented on GitHub (Nov 2, 2020):

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

@Onyx-Official commented on GitHub (Nov 2, 2020): I just typed in command but its fixed! Yay! Thanks @zadjii-msft !
claunia commented 2026-01-31 02:42:44 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 2, 2020):

Happy to help!

@zadjii-msft commented on GitHub (Nov 2, 2020): Happy to help!
claunia commented 2026-01-31 02:42:44 +00:00
Author
Owner
Copy Link

@androidacy-user commented on GitHub (Oct 30, 2021):

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

@androidacy-user commented on GitHub (Oct 30, 2021): That service keeps going back to manual for me, any idea why?
claunia commented 2026-01-31 02:42:44 +00:00
Author
Owner
Copy Link

@cebaa commented on GitHub (Aug 12, 2022):

@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.

@cebaa commented on GitHub (Aug 12, 2022): @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.
claunia commented 2026-01-31 02:42:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 12, 2022):

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

@zadjii-msft commented on GitHub (Aug 12, 2022): Basically, no. Your admin shouldn't have disabled that service in the first place - it's a critical OS service
claunia commented 2026-01-31 02:42:45 +00:00
Author
Owner
Copy Link

@cebaa commented on GitHub (Aug 12, 2022):

@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!

@cebaa commented on GitHub (Aug 12, 2022): @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](https://github.com/microsoft/terminal/issues/8697), 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!
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 Resolution-Duplicate
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#11256
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?