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

Windows Terminal not showing on top and various issues with opening default Terminal #13995

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

Originally created by @nitishvijai on GitHub (May 27, 2021).

Windows Terminal version (or Windows build number)

1.9.1445.0 (Windows Version 10.0.21387.1)

Other Software

Windows PowerShell (and other command shells)

Steps to reproduce

  1. Open PowerShell/CMD/any other shell. Make sure that Windows Terminal is set as the default terminal application in Settings.

Expected Behavior

The Windows Terminal should open (or create a new tab) and be on top of other windows (as it is now in focus), and the tab title should ideally be the default PowerShell/CMD tab text or any name you set for it ("Windows PowerShell", for example).

Actual Behavior

Windows Terminal launches a new window/tab, but it does not bring it to the front. It remains behind other windows.

In addition, the title of the tab is the file location of the shortcut that launched the new Terminal instance. For example, if I launched PowerShell via the Win+X menu, the tab text is:
"Ubuntu: C:\Users\nitis\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Windows PowerShell\Windows PowerShell.lnk"

Originally created by @nitishvijai on GitHub (May 27, 2021). ### Windows Terminal version (or Windows build number) 1.9.1445.0 (Windows Version 10.0.21387.1) ### Other Software Windows PowerShell (and other command shells) ### Steps to reproduce 1. Open PowerShell/CMD/any other shell. Make sure that Windows Terminal is set as the default terminal application in Settings. ### Expected Behavior The Windows Terminal should open (or create a new tab) and be on top of other windows (as it is now in focus), and the tab title should ideally be the default PowerShell/CMD tab text or any name you set for it ("Windows PowerShell", for example). ### Actual Behavior Windows Terminal launches a new window/tab, but it does not bring it to the front. It remains behind other windows. In addition, the title of the tab is the file location of the shortcut that launched the new Terminal instance. For example, if I launched PowerShell via the Win+X menu, the tab text is: "Ubuntu: C:\Users\nitis\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Windows PowerShell\Windows PowerShell.lnk"
claunia added the Resolution-Duplicate label 2026-01-31 03:57:58 +00:00
claunia commented 2026-01-31 03:57:59 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (May 28, 2021):

/dup #9460
/dup #9458

@miniksa commented on GitHub (May 28, 2021): /dup #9460 /dup #9458
claunia commented 2026-01-31 03:57:59 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 28, 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 (May 28, 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!
claunia commented 2026-01-31 03:57:59 +00:00
Author
Owner
Copy Link

@Stanfield911 commented on GitHub (Oct 20, 2023):

Hi, the titles of the referenced threads 9460 and 9458 above do not appear to have anything having to do with this Windows Terminal issue!

I'm currently working with W11 Pro, 22H2 OS build 22621.2428. This issue has recently appeared on my PC, presumably after a recent Windows 11 update. I have never seen it before, in +2 years of using W11. The problem: If I already have an active Windows Terminal window open (i.e. wt.exe), and then I activate a new terminals window by means of a desktop shortcut, the new terminals window is hidden behind the previous one, and I have to minimize or move the original one to see the new one in behind, or use ALT-TAB to get there. This is clearly wrong. Does anyone have any ideas what screwed up my windows terminal?

@Stanfield911 commented on GitHub (Oct 20, 2023): Hi, the titles of the referenced threads 9460 and 9458 above do not appear to have anything having to do with this Windows Terminal issue! I'm currently working with W11 Pro, 22H2 OS build 22621.2428. This issue has recently appeared on my PC, presumably after a recent Windows 11 update. I have never seen it before, in +2 years of using W11. The problem: If I already have an active Windows Terminal window open (i.e. wt.exe), and then I activate a new terminals window by means of a desktop shortcut, the new terminals window is hidden behind the previous one, and I have to minimize or move the original one to see the new one in behind, or use ALT-TAB to get there. This is clearly wrong. Does anyone have any ideas what screwed up my windows terminal?
claunia commented 2026-01-31 03:57:59 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 24, 2023):

@Stanfield911 what you're undoubtably seeing is #15479, a more recent regression in 1.18+. These linked threads here are from two years ago.

@zadjii-msft commented on GitHub (Oct 24, 2023): @Stanfield911 what you're undoubtably seeing is #15479, a more recent regression in 1.18+. These linked threads here are from _two years ago_.
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#13995
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?