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

No keyboard input while the Get-Credential dialog is open #15150

New Issue
Open
opened 2026-01-31 04:29:55 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 04:29:55 +00:00
Owner
Copy Link

Originally created by @jaapvandervelde on GitHub (Sep 9, 2021).

I read issue #4448 and checked that the Touch Keyboard and Handwriting Panel Service is running correctly (restarts, etc.)

However I still have this issue: if I'm running a Terminal (PowerShell) and I start a second one with this command:

Start-Process -FilePath "powershell" -Credential $(Get-Credential -Message 'Domain admin password required.' -UserName <some valid username>) -ArgumentList '-NoExit', '-Command', "cd $(Get-Location)"

A new PowerShell window opens, but the behaviour of it is very odd. Keyboard input doesn't seem to arrive at it, but when I type something (for example whoami to check it worked), it does show up after I switch focus away from the new window. The same behaviour applies to the Terminal Windows I started it from. It now only shows entered input after switching focus away from it.

If I close either window, the other will start working normally again immediately. I do not have this issue when starting a separate PowerShell window from the Start menu, regardless of whether I start it as myself, as local admin or as the same other user.

Note that the user account I'm starting the new PowerShell as is a domain admin account, while the account running the original Terminal window is not. Not sure if it matters, I don't have a spare non-domain admin account on hand to try if the same problem occurs when using a non-admin account.

Originally created by @jaapvandervelde on GitHub (Sep 9, 2021). I read issue #4448 and checked that the `Touch Keyboard and Handwriting Panel Service` is running correctly (restarts, etc.) However I still have this issue: if I'm running a Terminal (PowerShell) and I start a second one with this command: ``` Start-Process -FilePath "powershell" -Credential $(Get-Credential -Message 'Domain admin password required.' -UserName <some valid username>) -ArgumentList '-NoExit', '-Command', "cd $(Get-Location)" ``` A new PowerShell window opens, but the behaviour of it is very odd. Keyboard input doesn't seem to arrive at it, but when I type something (for example `whoami` to check it worked), it does show up *after* I switch focus away from the new window. The same behaviour applies to the Terminal Windows I started it from. It now only shows entered input after switching focus away from it. If I close either window, the other will start working normally again immediately. I do not have this issue when starting a separate PowerShell window from the Start menu, regardless of whether I start it as myself, as local admin or as the same other user. Note that the user account I'm starting the new PowerShell as is a domain admin account, while the account running the original Terminal window is not. Not sure if it matters, I don't have a spare non-domain admin account on hand to try if the same problem occurs when using a non-admin account.
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 Area-Input Help Wanted Issue-Bug Needs-Author-Feedback Needs-Repro Needs-Triage No-Recent-Activity Priority-3 Product-Conpty
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#15150
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?