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

Bug Report - Powershell Get-Credential doesn't work #2684

New Issue
Closed
opened 2026-01-30 23:02:11 +00:00 by claunia · 3 comments
claunia commented 2026-01-30 23:02:11 +00:00
Owner
Copy Link

Originally created by @kevinteynor on GitHub (Jul 10, 2019).

Environment

Windows build number: 10.0.18362.175
Windows Terminal: built from master af1a4dd068

Steps to reproduce

In a powershell window, execute the command Get-Credential

Expected behavior

The credential dialog should open and be interactive; I should be able to enter inputs and close the dialog.

Actual behavior

The credential dialog appears and can be dragged around, but no buttons or input fields on it are responsive. It also blocks the rest of the terminal, requiring me to kill and restart the entire terminal.

This happens even when launching terminal as admin.

Other GUI dialogs (Show-Command) work as expected, but I haven't tried with any other blocking dialogs.

Originally created by @kevinteynor on GitHub (Jul 10, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> ## Environment Windows build number: 10.0.18362.175 Windows Terminal: built from master af1a4dd068171c7cbbca42c69082fef3ba501efc ## Steps to reproduce <!-- A description of how to trigger this bug. --> In a powershell window, execute the command ```Get-Credential``` ## Expected behavior The credential dialog should open and be interactive; I should be able to enter inputs and close the dialog. ## Actual behavior The credential dialog appears and can be dragged around, but no buttons or input fields on it are responsive. It also blocks the rest of the terminal, requiring me to kill and restart the entire terminal. This happens even when launching terminal as admin. Other GUI dialogs (Show-Command) work as expected, but I haven't tried with any other blocking dialogs.
claunia commented 2026-01-30 23:02:12 +00:00
Author
Owner
Copy Link

@oising commented on GitHub (Jul 10, 2019):

powershell 5.x or pwsh (powershell core)?

@oising commented on GitHub (Jul 10, 2019): powershell 5.x or pwsh (powershell core)?
claunia commented 2026-01-30 23:02:12 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Jul 12, 2019):

Not sure if this counts but using the Store release, it works in Windows Powershell. I have pwsh installed on Pengwin so this may be where things differ. After launching Pengwin from Terminal, I entered pwsh and executed the same command. Since it was launched in Pengwin, I don't get a dialog box, instead, you enter the credentials inside the Terminal. This works.

So if there's an issue, something changed between Store release and master af1a4dd

@WSLUser commented on GitHub (Jul 12, 2019): Not sure if this counts but using the Store release, it works in Windows Powershell. I have pwsh installed on Pengwin so this may be where things differ. After launching Pengwin from Terminal, I entered pwsh and executed the same command. Since it was launched in Pengwin, I don't get a dialog box, instead, you enter the credentials inside the Terminal. This works. So if there's an issue, something changed between Store release and master af1a4dd
claunia commented 2026-01-30 23:02:12 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 19, 2019):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Jul 19, 2019): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
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-Interop Issue-Bug Needs-Author-Feedback Needs-Repro No-Recent-Activity Product-Terminal
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#2684
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?