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

Set 'Default terminal application' to Windows Terminal break 'Get-Credential' cmdlets in Windows PowerShell #20407

New Issue
Open
opened 2026-01-31 07:12:51 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 07:12:51 +00:00
Owner
Copy Link

Originally created by @doggy8088 on GitHub (Aug 25, 2023).

Windows Terminal version

1.17.11461.0

Windows build number

10.0.19045.3324

Other Software

No response

Steps to reproduce

  1. Configure Default terminal application from Let Windows decide to Windows Terminal.

    image

  2. Open Windows PowerShell (5.1.19041.3031)

    image

  3. Execute Get-Credential cmdlet

    Get-Credential -Message "AzureAD Login" -UserName "user@example.com"

    I expected to show up Windows PowerShell credential request. window, but it doesn't.

    image

  4. If I open another new tab with Windows PowerShell, the problem solved.

    image

Expected Behavior

I expected to show up Windows PowerShell credential request. window, but it doesn't.

Actual Behavior

The first Windows PowerShell session in the Windows Terminal window will not be able to execute Get-Credential correctly. There is no error occurred. I also tried Get-Credential -Message "AzureAD Login" -UserName "user@example.com" -Verbose command. It still nothing show up.

Originally created by @doggy8088 on GitHub (Aug 25, 2023). ### Windows Terminal version 1.17.11461.0 ### Windows build number 10.0.19045.3324 ### Other Software _No response_ ### Steps to reproduce 1. Configure `Default terminal application` from `Let Windows decide` to `Windows Terminal`. ![image](https://github.com/microsoft/terminal/assets/88981/b9b5b29d-f221-4605-9bf1-444d0537d56a) 2. Open Windows PowerShell (5.1.19041.3031) ![image](https://github.com/microsoft/terminal/assets/88981/80248396-3e5d-4fab-843f-2a952f879341) 3. Execute `Get-Credential` cmdlet ```ps1 Get-Credential -Message "AzureAD Login" -UserName "user@example.com" ``` I expected to show up **Windows PowerShell credential request.** window, but it doesn't. ![image](https://github.com/microsoft/terminal/assets/88981/5aeddad8-ed97-4a66-9529-fcc114b31abf) 4. If I open another new tab with Windows PowerShell, the problem solved. ![image](https://github.com/microsoft/terminal/assets/88981/4dcd19e5-4212-4882-80c5-279a3da31bdd) ### Expected Behavior I expected to show up **Windows PowerShell credential request.** window, but it doesn't. ### Actual Behavior The first Windows PowerShell session in the Windows Terminal window will not be able to execute `Get-Credential` correctly. There is no error occurred. I also tried `Get-Credential -Message "AzureAD Login" -UserName "user@example.com" -Verbose` command. It still nothing show up.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 07:12:51 +00:00
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 Issue-Bug 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#20407
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?