Windows Terminal asks to close unprompted, does so even after telling it no, leaves processes hanging #12885

Closed
opened 2026-01-31 03:28:01 +00:00 by claunia · 4 comments
Owner

Originally created by @Daiz on GitHub (Mar 6, 2021).

Environment

Windows build number: 10.0.19041.0
Windows Terminal version (if applicable): 1.6.10571.0

Steps to reproduce

Unsure. Occasionally, seemingly some time after waking Windows 10 up from sleep, the Terminal on its own will prompt for "do you want to close all tabs?" and even after being told no, it still closes itself. This can also leave certain things hanging, for example I was running a webpack dev server in one of my terminals, which is still alive and now I have to kill it via Task Manager to get rid of it.

Expected behavior

1 Windows Terminal shouldn't randomly prompt me to close it without reason.
2. Even if it has a reason for wanting to close itself (updating?) it should respect the fact that I said "no".
3. When closing, active running processes should get killed accordingly.

Actual behavior

  1. Windows Terminal seemingly randomly prompts user to close all tabs.
  2. Closes itself even if told no.
  3. Can leave running processes hanging in limbo.
Originally created by @Daiz on GitHub (Mar 6, 2021). # Environment ```none Windows build number: 10.0.19041.0 Windows Terminal version (if applicable): 1.6.10571.0 ``` # Steps to reproduce Unsure. Occasionally, seemingly some time after waking Windows 10 up from sleep, the Terminal on its own will prompt for "do you want to close all tabs?" and even after being told no, it still closes itself. This can also leave certain things hanging, for example I was running a webpack dev server in one of my terminals, which is still alive and now I have to kill it via Task Manager to get rid of it. # Expected behavior 1 Windows Terminal shouldn't randomly prompt me to close it without reason. 2. Even if it has a reason for wanting to close itself (updating?) it should respect the fact that I said "no". 3. When closing, active running processes should get killed accordingly. # Actual behavior 1. Windows Terminal seemingly randomly prompts user to close all tabs. 2. Closes itself even if told no. 3. Can leave running processes hanging in limbo.
claunia added the Resolution-Duplicate label 2026-01-31 03:28:01 +00:00
Author
Owner

@j4james commented on GitHub (Mar 6, 2021):

Do you perhaps have the App Updates option in the Microsoft Store set to update automatically? That would possibly explain what happened. The problem of the app terminating because of an update is being tracked in issue #3915.

@j4james commented on GitHub (Mar 6, 2021): Do you perhaps have the _App Updates_ option in the Microsoft Store set to update automatically? That would possibly explain what happened. The problem of the app terminating because of an update is being tracked in issue #3915.
Author
Owner

@Daiz commented on GitHub (Mar 7, 2021):

That seems to have been the case, so the shutting down is most likely tied to the same issue. The only thing I can't say for sure is whether the hanging processes are tightly tied to the updating issue, but it does seem to only happen when WT forcefully closes itself.

I have turned automatic updates off in the Store for now, but this is obviously not a very ideal workaround.

@Daiz commented on GitHub (Mar 7, 2021): That seems to have been the case, so the shutting down is most likely tied to the same issue. The only thing I can't say for sure is whether the hanging processes are tightly tied to the updating issue, but it does seem to only happen when WT forcefully closes itself. I have turned automatic updates off in the Store for now, but this is obviously not a very ideal workaround.
Author
Owner

@zadjii-msft commented on GitHub (Mar 8, 2021):

Yea, we see a lot of these a few days after an update is pushed. We're working on pursuing an internal fix.

/dup #3915
/dup #6726

@zadjii-msft commented on GitHub (Mar 8, 2021): Yea, we see a lot of these a few days after an update is pushed. We're working on pursuing an internal fix. /dup #3915 /dup #6726
Author
Owner

@ghost commented on GitHub (Mar 8, 2021):

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 (Mar 8, 2021): 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.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#12885