Skip to content

Can't reopen Windows Terminal #17360

Closed
@SpecterShell

Description

@SpecterShell

Windows Terminal version

1.20.11381.0

Windows build number

10.0.22631.0

Other Software

No response

Steps to reproduce

In Windows Terminal 1.20.11381.0 (delivered by Microsoft Store), when a window is being closed, it appears not to be properly "unregistered", so the process still thinks it is alive, and it is still present in the context menu like this:

image

This would bring issues when the "New instance behavior" is set to "Attach to most recently used window on this desktop". No window will pop up when you try to open a new console or run console applications after a window is closed, even if I'm in a different desktop.

  1. Set "New instance behavior" to "Attach to most recently used window on this desktop" and close the window.
  2. Open a new window in either way.

Expected Behavior

No response

Actual Behavior

The process didn't crash, but it just rejects to open a new window for me.

When opening a console application, the Windows Terminal window doesn't pop up either, and about 1 minute later the conhost window pop up.

Quake mode still works, and I can open a new window by pressing Ctrl+Shift+N there, but it doesn't fix the issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area-RemotingCommunication layer between windows. Often for windowing behavior, quake mode, etc.In-PRThis issue has a related PRIssue-BugIt either shouldn't be doing this or needs an investigation.Needs-AttentionThe core contributors need to come back around and look at this ASAP.Needs-Tag-FixDoesn't match tag requirementsProduct-TerminalThe new Windows Terminal.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions