Windows Terminal's new windows is not at foreground. #17560

Closed
opened 2026-01-31 05:45:59 +00:00 by claunia · 5 comments
Owner

Originally created by @nanoric on GitHub (May 25, 2022).

If there is a background windows terminal instance. A new instance of Windows Terminal run by Win+R as "wt" does not come to the foreground.
So we have to use ALT+Tab multiple times or use the mouse to see which one is new.
This action is really annoying.

So I suggest adding a new launch mode "default foreground" which will start in default mode and then focus (bring to foreground, not meaning WT's Focus mode!) immediately.

Originally created by @nanoric on GitHub (May 25, 2022). If there is a background windows terminal instance. A new instance of Windows Terminal run by Win+R as "wt" does not come to the foreground. So we have to use ALT+Tab multiple times or use the mouse to see which one is new. This action is really annoying. So I suggest adding a new launch mode "default foreground" which will start in default mode and then focus (bring to foreground, not meaning WT's Focus mode!) immediately.
claunia added the Needs-TriageNeeds-Tag-FixResolution-No-Repro labels 2026-01-31 05:46:00 +00:00
Author
Owner

@zadjii-msft commented on GitHub (May 25, 2022):

  • Which version of Terminal/?
  • Which version of the OS?
  • How are you launching the Terminal?
  • What app is in the foreground when you notice this behavior?

This is generally supposed to work by default.

@zadjii-msft commented on GitHub (May 25, 2022): * Which version of Terminal/? * Which version of the OS? * How are you launching the Terminal? * What app is in the foreground when you notice this behavior? This is generally supposed to work by default.
Author
Owner

@ghost commented on GitHub (May 29, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (May 29, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Author
Owner

@nanoric commented on GitHub (Jun 10, 2022):

Which version of Terminal/?

Preview Version.
I have just uninstalled it, so i'm not able to find out the version number. But because wt is updated with windows update, it should always be the newest version.

Which version of the OS?

Edition Windows Server 2022 Standard
Version 21H2
Installed on ‎11/‎30/‎2021
OS build 20348.740

How are you launching the Terminal?

Win+R : wt

What app is in the foreground when you notice this behavior?

This might be the problem
I'm face this problem usually when I'm coding, which means i'm running Visual Stuio or Clion, maximumed windowed(not fullscreen). And I have two screen. If coding with Visual Studio, it uses both of them. If coding with Clion, it uses only the primary screen, another one is always used by Visual Studio.

@nanoric commented on GitHub (Jun 10, 2022): ### Which version of Terminal/? Preview Version. I have just uninstalled it, so i'm not able to find out the version number. But because wt is updated with windows update, it should always be the newest version. ### Which version of the OS? Edition Windows Server 2022 Standard Version 21H2 Installed on ‎11/‎30/‎2021 OS build 20348.740 ### How are you launching the Terminal? Win+R : wt ### What app is in the foreground when you notice this behavior? **This might be the problem** I'm face this problem usually when I'm coding, which means i'm running Visual Stuio or Clion, maximumed windowed(not fullscreen). And I have two screen. If coding with Visual Studio, it uses both of them. If coding with Clion, it uses only the primary screen, another one is always used by Visual Studio.
Author
Owner

@zadjii-msft commented on GitHub (Jun 10, 2022):

Well, if you ever re-install the Terminal and would like to help further debug, we can always reopen this in the future. I certainly haven't seen this behavior while using VS, and I don't believe my colleague @lhecker has seen this when using CLion either. It also could be an OS version issue - I know there were some quirks with how the OS would launch packaged applications on Windows 10 (that are seemingly resolved in Windows 11).

@zadjii-msft commented on GitHub (Jun 10, 2022): Well, if you ever re-install the Terminal and would like to help further debug, we can always reopen this in the future. I certainly haven't seen this behavior while using VS, and I don't believe my colleague @lhecker has seen this when using CLion either. It also could be an OS version issue - I know there were some quirks with how the OS would launch packaged applications on Windows 10 (that are seemingly resolved in Windows 11).
Author
Owner

@IT-CASADO commented on GitHub (Jan 31, 2025):

Same for me.

Window 11 24H2 (fresh install), but I had this also with my old installation.

@IT-CASADO commented on GitHub (Jan 31, 2025): Same for me. Window 11 24H2 (fresh install), but I had this also with my old installation.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#17560