Terminal opens new windows which can not be closed #20740

Closed
opened 2026-01-31 07:22:42 +00:00 by claunia · 3 comments
Owner

Originally created by @DanielHabenicht on GitHub (Oct 27, 2023).

Windows Terminal version

1.18.2822.0

Windows build number

10.0.19044.0

Other Software

nothing special I suppose
I have some custom script that run on logon, which might explain why there are more terminals opening.

Steps to reproduce

  1. Open Terminal
  2. Lock Windows
  3. Unlock Windows
    ==> One Empty Terminal Window with no content

Expected Behavior

Terminal does not open more windows (or if it is actually my script that opens the terminals it should display them like any other window)

Actual Behavior

Each Lock/Unlock Cycle one (or more) Terminal windows are spawned.
The new Terminal window is not closable via the close button, but have to be terminated via Task Manager.
(or I just found another way: one has to open a new tab and then it can be closed like any other window)

image

Originally created by @DanielHabenicht on GitHub (Oct 27, 2023). ### Windows Terminal version 1.18.2822.0 ### Windows build number 10.0.19044.0 ### Other Software nothing special I suppose I have some custom script that run on logon, which might explain why there are more terminals opening. ### Steps to reproduce 1. Open Terminal 2. Lock Windows 3. Unlock Windows ==> One Empty Terminal Window with no content ### Expected Behavior Terminal does not open more windows (or if it is actually my script that opens the terminals it should display them like any other window) ### Actual Behavior Each Lock/Unlock Cycle one (or more) Terminal windows are spawned. The new Terminal window is not closable via the close button, but have to be terminated via Task Manager. (or I just found another way: one has to open a new tab and then it can be closed like any other window) ![image](https://github.com/microsoft/terminal/assets/13590797/a2312dc1-c9c7-4dcd-9acb-8e42f29d7960)
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 07:22:42 +00:00
Author
Owner

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

This is kinda like #15936... you know what this is most definitely close enough to that.

/dup #15936

Thanks!

@zadjii-msft commented on GitHub (Oct 27, 2023): This is kinda like #15936... you know what this is most definitely close enough to that. /dup #15936 Thanks!
Author
Owner

@microsoft-github-policy-service[bot] commented on GitHub (Oct 27, 2023):

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!

@microsoft-github-policy-service[bot] commented on GitHub (Oct 27, 2023): 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! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
Author
Owner

@DanielHabenicht commented on GitHub (Oct 27, 2023):

Yes, that pretty close.
Now I know why I was not finding it with my search keywords.

@DanielHabenicht commented on GitHub (Oct 27, 2023): Yes, that pretty close. Now I know why I was not finding it with my search keywords.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20740