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

I get a warning that makes no sense on a desktop PC #11935

New Issue
Closed
opened 2026-01-31 03:01:33 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 03:01:33 +00:00
Owner
Copy Link

Originally created by @mdcclxv on GitHub (Jan 2, 2021).

Windows build number: Microsoft Windows NT 10.0.18363.0
Windows Terminal version (if applicable): 1.4.3243.0

Steps to reproduce

Disable the "Touch Keyboard and Handwriting Panel" service.

Expected behavior

No warning if I don't have a touchscreen device.

Actual behavior

Every time I start the terminal I get the following warning when running on a desktop machine, with no touchscreen:

image

A simple solution

If testing for a touchscreen device is too complicated code-wise then at least provide a setting to disable this warning for good.

Originally created by @mdcclxv on GitHub (Jan 2, 2021). Windows build number: Microsoft Windows NT 10.0.18363.0 Windows Terminal version (if applicable): 1.4.3243.0 # Steps to reproduce Disable the "Touch Keyboard and Handwriting Panel" service. # Expected behavior No warning if I don't have a touchscreen device. # Actual behavior Every time I start the terminal I get the following warning when running on a desktop machine, with no touchscreen: ![image](https://user-images.githubusercontent.com/33668915/103467212-6232fe00-4d55-11eb-8e1f-d2a008702c6b.png) # A simple solution If testing for a touchscreen device is too complicated code-wise then at least provide a setting to disable this warning for good.
claunia added the Resolution-Duplicate label 2026-01-31 03:01:33 +00:00
claunia commented 2026-01-31 03:01:35 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Jan 2, 2021):

Well it’s actually more complicated than you think. See #8228 and #8524. Is there a particular reason why you wanna disable the service?

@skyline75489 commented on GitHub (Jan 2, 2021): Well it’s actually more complicated than you think. See #8228 and #8524. Is there a particular reason why you wanna disable the service?
claunia commented 2026-01-31 03:01:35 +00:00
Author
Owner
Copy Link

@mdcclxv commented on GitHub (Jan 2, 2021):

Browsed the two tickets you just indicated, and I still think that an option in the settings json file to disable the warning would do just good and no harm. People who don't have the input issue will use that option, people who have it won't.
If that InfoBar has to be dismissed manually then it's not any better than a popup. Is still annoying.

My reason is basic PC optimization. You will tell me now that disabling services at random is not optimization, but I'm not doing it randomly. Whenever MS introduces a new service (and it does that on almost any feature update), if the service sounds like I don't need it I disable it, look for issues in Event Viewer and use my machine like that for like a week. I only disable one service at a time. I've been doing this for years now and it never failed me. I had situations when errors popped up in Event Viewer, I had situations when some apps went bezerk and I had to re-enable the service.

@mdcclxv commented on GitHub (Jan 2, 2021): Browsed the two tickets you just indicated, and I still think that an option in the settings json file to disable the warning would do just good and no harm. People who don't have the input issue will use that option, people who have it won't. If that InfoBar has to be dismissed manually then it's not any better than a popup. Is still annoying. My reason is basic PC optimization. You will tell me now that disabling services at random is not optimization, but I'm not doing it randomly. Whenever MS introduces a new service (and it does that on almost any feature update), if the service sounds like I don't need it I disable it, look for issues in Event Viewer and use my machine like that for like a week. I only disable one service at a time. I've been doing this for years now and it never failed me. I had situations when errors popped up in Event Viewer, I had situations when some apps went bezerk and I had to re-enable the service.
claunia commented 2026-01-31 03:01:35 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 3, 2021):

/cc @ebadger as an fyi

I would really recommend not just disabling random services, just because you think they don't do anything relevant. It may seem like disabling it does nothing at first, but clearly, disabling this service has the unintended side-effect of breaking keyboard input to the Terminal. Plus, who knows if other functionality will be added in future OS updates that depend on services that you've disabled.

In my opinion, this service's name might be slightly misleading. I think it should be more correctly the "Touch, Keyboard, and Handwriting Panel Service". Even if you're on a desktop PC, this service helps control keyboard input to UWP (and XAML Islands) applications.

We've already discussed this to death in the aformentioned thread, so I'll close this one as a dupe, and we can continue the discussion in that thread. Thanks!

/dup #8228

@zadjii-msft commented on GitHub (Jan 3, 2021): /cc @ebadger as an fyi I would really recommend not just disabling random services, just because you _think_ they don't do anything relevant. It may seem like disabling it does nothing at first, but clearly, disabling this service has the unintended side-effect of breaking keyboard input to the Terminal. Plus, who knows if other functionality will be added in future OS updates that depend on services that you've disabled. In my opinion, this service's name might be slightly misleading. I think it should be more correctly the "Touch<strong>,</strong> Keyboard<strong>,</strong> and Handwriting Panel Service". Even if you're on a desktop PC, this service helps control keyboard input to UWP (and XAML Islands) applications. We've already discussed this to death in the aformentioned thread, so I'll close this one as a dupe, and we can continue the discussion in that thread. Thanks! /dup #8228
claunia commented 2026-01-31 03:01:35 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 3, 2021):

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 (Jan 3, 2021): 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!
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#11935
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?