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 Window isn't able to be brought to forefront sporadically after switching to a different window #18163

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

Originally created by @erikumhoefer on GitHub (Aug 12, 2022).

Windows Terminal version

1.14.1962.0

Windows build number

10.0.19044.0

Other Software

No response

Steps to reproduce

  • Have windows terminal open
  • Switch to other windows
  • Try to reopen Terminal again by clicking on icon in task bar, or attempting to ALT + Tab to window
  • Realize Windows terminal window will not pull back up
  • Close Windows Terminal Instance and reopen
  • Terminal will work as expected for some time but then issue reappears

Expected Behavior

I am able to bring the window for the terminal back into view so I can use it, as expected when bringing up windows for any other application.

Actual Behavior

Unable to bring windows terminal back to forefront, despite the icon still showing an instance of terminal is running.

When using windows terminal, when switching to different windows (FireFox, VSCode, Outlook, etc. haven't been able to get a correlation between what application is interfering (if it is only one)), occasionally I am unable to bring back the Terminal window back into forefront. So, in order to use Terminal again, even though the icon is on the taskbar showing that the instance is running, I will have to close the "running" instance, and reopen to use it. This has recently started happening and occurs almost daily.

How to reproduce:

  • Use terminal with other applications open (doesn't matter if in full screen or windowed)
  • switch between terminal and other apps
  • Eventually, won't be able to switch back to Terminal and will need to restart it in order to use it.

Development environment: Laptop with screen closed connected to two monitors. Only using two monitors. Alt+Tabbing to try and bring window back does not work.

Originally created by @erikumhoefer on GitHub (Aug 12, 2022). ### Windows Terminal version 1.14.1962.0 ### Windows build number 10.0.19044.0 ### Other Software _No response_ ### Steps to reproduce * Have windows terminal open * Switch to other windows * Try to reopen Terminal again by clicking on icon in task bar, or attempting to ALT + Tab to window * Realize Windows terminal window will not pull back up * Close Windows Terminal Instance and reopen * Terminal will work as expected for some time but then issue reappears ### Expected Behavior I am able to bring the window for the terminal back into view so I can use it, as expected when bringing up windows for any other application. ### Actual Behavior Unable to bring windows terminal back to forefront, despite the icon still showing an instance of terminal is running. When using windows terminal, when switching to different windows (FireFox, VSCode, Outlook, etc. haven't been able to get a correlation between what application is interfering (if it is only one)), occasionally I am unable to bring back the Terminal window back into forefront. So, in order to use Terminal again, even though the icon is on the taskbar showing that the instance is running, I will have to close the "running" instance, and reopen to use it. This has recently started happening and occurs almost daily. How to reproduce: * Use terminal with other applications open (doesn't matter if in full screen or windowed) * switch between terminal and other apps * Eventually, won't be able to switch back to Terminal and will need to restart it in order to use it. Development environment: Laptop with screen closed connected to two monitors. Only using two monitors. Alt+Tabbing to try and bring window back does not work.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:05:31 +00:00
claunia commented 2026-01-31 06:05:32 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 12, 2022):

Thanks for the report! This is actually already being tracked by another issue on our repo - please refer to #13589 for more discussion.

/dup #13589

@zadjii-msft commented on GitHub (Aug 12, 2022): Thanks for the report! This is actually already being tracked by another issue on our repo - please refer to #13589 for more discussion. /dup #13589
claunia commented 2026-01-31 06:05:32 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 12, 2022):

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 (Aug 12, 2022): 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 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#18163
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?