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

powershell login screens pop-under / don't show on taskbar #8899

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

Originally created by @dakink on GitHub (Jun 8, 2020).

When using commands that normally pop-up a login screen like connect-azuread or connect-msolservice, the pop-up doesn't show as a pop-up but is hidden as the bottom app. In the case of connect-azuread there is no icon displayed on the taskbar either.

Running the following system:
Windows Terminal Version: 1.0.1401.0

Windows 10 Pro
10 0 19640 1
10 0 18362 752

With Connect-AzureAD the popup is normally hidden by the application. In this case there is no taskbar icon to show that the popup has come up. This appears to be by design from the module. The cursor in Powershell will be blinking but it becomes non-responsive as far as keypresses go.
connect-azuread

With connect-msolservice the login window is in the center of the screen, and an icon on the taskbar shows that the login window is there, but it doesn't pop-up over the terminal screen.
connect-msolservice

When run directly in powershell (without terminal) the popups do come up in front of all open instances.

powershell-connect-azuread
powershell-connect-msolservice

I would expect the behaviour between powershell and terminal to be the same in these cases. If you need any other info, please let me know and i'll do my best to provide it.

Originally created by @dakink on GitHub (Jun 8, 2020). When using commands that normally pop-up a login screen like connect-azuread or connect-msolservice, the pop-up doesn't show as a pop-up but is hidden as the bottom app. In the case of connect-azuread there is no icon displayed on the taskbar either. Running the following system: Windows Terminal Version: 1.0.1401.0 Windows 10 Pro 10 0 19640 1 10 0 18362 752 With Connect-AzureAD the popup is normally hidden by the application. In this case there is no taskbar icon to show that the popup has come up. This appears to be by design from the module. The cursor in Powershell will be blinking but it becomes non-responsive as far as keypresses go. ![connect-azuread](https://user-images.githubusercontent.com/17966027/84010818-7c4e5e80-a975-11ea-8c1d-bee5a3b4c17b.png) With connect-msolservice the login window is in the center of the screen, and an icon on the taskbar shows that the login window is there, but it doesn't pop-up over the terminal screen. ![connect-msolservice](https://user-images.githubusercontent.com/17966027/84010821-7ce6f500-a975-11ea-8b6c-ca05c81ea9c8.png) When run directly in powershell (without terminal) the popups do come up in front of all open instances. ![powershell-connect-azuread](https://user-images.githubusercontent.com/17966027/84011441-69885980-a976-11ea-9dee-bf4c9c270857.png) ![powershell-connect-msolservice](https://user-images.githubusercontent.com/17966027/84011444-6a20f000-a976-11ea-9696-3d2048926bf8.png) I would expect the behaviour between powershell and terminal to be the same in these cases. If you need any other info, please let me know and i'll do my best to provide it.
claunia added the Resolution-Duplicate label 2026-01-31 01:40:48 +00:00
claunia commented 2026-01-31 01:40:49 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 8, 2020):

I'm gonna guess that this is is actually #2988. That's the issue tracking most of the z-order problems the Terminal sometimes has.

/dup #2988

@zadjii-msft commented on GitHub (Jun 8, 2020): I'm gonna guess that this is is actually #2988. That's the issue tracking most of the [z-order](https://github.com/microsoft/terminal/issues?q=is%3Aissue+%22z-order%3A+is%3Aclosed) problems the Terminal sometimes has. /dup #2988
claunia commented 2026-01-31 01:40:49 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 8, 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 (Jun 8, 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!
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#8899
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?