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

Terminal opens behind other windows #22902

New Issue
Open
opened 2026-01-31 08:26:40 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 08:26:40 +00:00
Owner
Copy Link

Originally created by @andyc56-mso on GitHub (Feb 11, 2025).

Windows Terminal version

1.22.10352.0

Windows build number

19045.5371

Other Software

PowerShell 7.5.0
clink for cmd.exe

Steps to reproduce

With both of my Windows 10 machines, Terminal 1.22.10352.0 opens up behind other windows when launched from the "Open in Terminal" context menu. This appears to be the same issue or very similar to the now-closed 16260. When launching from the Start menu, it behaves normally, starting above other windows. Both behaviors are completely repeatable, not intermittent.

Reinstalling 1.21.10351.0 fixed the problem on both Windows 10 machines.

My default profile uses PowerShell 7.5.0, but this also happens when cmd.exe is the default.

My one Windows 11 machine does not do this.

Expected Behavior

Expected behavior is for Terminal to open up on top of other windows both when launched from the "Open in Terminal" context menu and when launched from the Start menu.

Actual Behavior

Terminal 1.22.10352.0 incorrectly opens up behind other windows when launched from the "Open in Terminal" context menu, and correctly opens up on top of other windows when launched from the Start menu.

Originally created by @andyc56-mso on GitHub (Feb 11, 2025). ### Windows Terminal version 1.22.10352.0 ### Windows build number 19045.5371 ### Other Software PowerShell 7.5.0 clink for cmd.exe ### Steps to reproduce With both of my Windows 10 machines, Terminal 1.22.10352.0 opens up behind other windows when launched from the "Open in Terminal" context menu. This appears to be the same issue or very similar to the now-closed 16260. When launching from the Start menu, it behaves normally, starting above other windows. Both behaviors are completely repeatable, not intermittent. Reinstalling 1.21.10351.0 fixed the problem on both Windows 10 machines. My default profile uses PowerShell 7.5.0, but this also happens when cmd.exe is the default. My one Windows 11 machine does not do this. ### Expected Behavior Expected behavior is for Terminal to open up on top of other windows both when launched from the "Open in Terminal" context menu and when launched from the Start menu. ### Actual Behavior Terminal 1.22.10352.0 incorrectly opens up behind other windows when launched from the "Open in Terminal" context menu, and correctly opens up on top of other windows when launched from the Start menu.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 08:26:41 +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#22902
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?