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

Terminal update from store closes terminal and detaches all consoles #18197

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

Originally created by @ukdocCT on GitHub (Aug 18, 2022).

Windows Terminal version

1.14.1962.0

Windows build number

10.0.19044.0

Other Software

No other software, issue is with terminal itself.

Steps to reproduce

Terminal has been installed on my laptop from the Microsoft store.
When an update flows through the store it appears to close off my running terminal, will several tabs open, and then installs.
The running consoles become detached.

When i start the terminal again the consoles are not reattached.

I then have to kill all the consoles i was running and relaunch them. This sometimes means code that i have been running in powershell or WSL needs to be rerun.

Expected Behavior

Prompt to close the terminal app for the install, or install in the background and switch to the new version on next launch of terminal (dont know if this is even possible with store delivered apps), or reattach to the consoles (i know that this one is likely to be near impossible as you will not be able identify the old consoles).

Actual Behavior

terminal closes and all running consoles are detached from the terminal meaning they have to be killed from taskmgr.

Originally created by @ukdocCT on GitHub (Aug 18, 2022). ### Windows Terminal version 1.14.1962.0 ### Windows build number 10.0.19044.0 ### Other Software No other software, issue is with terminal itself. ### Steps to reproduce Terminal has been installed on my laptop from the Microsoft store. When an update flows through the store it appears to close off my running terminal, will several tabs open, and then installs. The running consoles become detached. When i start the terminal again the consoles are not reattached. I then have to kill all the consoles i was running and relaunch them. This sometimes means code that i have been running in powershell or WSL needs to be rerun. ### Expected Behavior Prompt to close the terminal app for the install, or install in the background and switch to the new version on next launch of terminal (dont know if this is even possible with store delivered apps), or reattach to the consoles (i know that this one is likely to be near impossible as you will not be able identify the old consoles). ### Actual Behavior terminal closes and all running consoles are detached from the terminal meaning they have to be killed from taskmgr.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:06:33 +00:00
claunia commented 2026-01-31 06:06:34 +00:00
Author
Owner
Copy Link

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

What precisely were you running that got detached/? I'm under the impression that anything running in the foreground should still act as though the running console window was closed and shut down accordingly [1].

Largely, we're tracking this in #3915 and more specifical to the "orphaning" you're seeing here, #9914. I believe we have a fix for the orphaning that went out in https://github.com/microsoft/terminal/releases/tag/v1.15.2282.0 (though, that won't really work until 1.16 comes out).

I think I'm gonna leave this open for now, to try and get at whatever is being orphaned here, but I'll probably dupe this to #9914.

[1]: The caveat of course, is anything running in the BG of that console, isn't gonna get a detach message.

@zadjii-msft commented on GitHub (Aug 18, 2022): What _precisely_ were you running that got detached/? I'm under the impression that anything running in the foreground should still act as though the running console window was closed and shut down accordingly [1]. Largely, we're tracking this in #3915 and more specifical to the "orphaning" you're seeing here, #9914. I believe we have a fix for the orphaning that went out in https://github.com/microsoft/terminal/releases/tag/v1.15.2282.0 (though, that won't really work until 1.16 comes out). I think I'm gonna leave this open for now, to try and get at whatever is being orphaned here, but I'll probably dupe this to #9914. [1]: The caveat of course, is anything running in the BG of that console, isn't gonna get a detach message.
claunia commented 2026-01-31 06:06:35 +00:00
Author
Owner
Copy Link

@ukdocCT commented on GitHub (Aug 18, 2022):

The comments on #9914 is exactly the problem i am having with orphaned consoles.

I have read the comments on #9914 and #13614 and am not sure that having all the open consoles closed out rather than orphaned is any better than the current situation.

Although this is only one crash per user, and for home users perhaps not too important, for those of us that find terminal invaluable in their work situation, coming back to my laptop overnight and finding all my sessions unusable is more than inconvenient, it has broken several of our long running processes, so much so that i now have to run them in separate powershell or WSL sessions outside terminal. A situation i'm not happy with as i love using terminal, but i don't have a choice if i want to ensure that i can check my scripts the following day.

I have added a comment on #9914 so am happy for this one to be closed and i will track it on that issue.

@ukdocCT commented on GitHub (Aug 18, 2022): The comments on #9914 is exactly the problem i am having with orphaned consoles. I have read the comments on #9914 and #13614 and am not sure that having all the open consoles closed out rather than orphaned is any better than the current situation. Although this is only one crash per user, and for home users perhaps not too important, for those of us that find terminal invaluable in their work situation, coming back to my laptop overnight and finding all my sessions unusable is more than inconvenient, it has broken several of our long running processes, so much so that i now have to run them in separate powershell or WSL sessions outside terminal. A situation i'm not happy with as i love using terminal, but i don't have a choice if i want to ensure that i can check my scripts the following day. I have added a comment on #9914 so am happy for this one to be closed and i will track it on that issue.
claunia commented 2026-01-31 06:06:35 +00:00
Author
Owner
Copy Link

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

We're still really trying to work with the Store team here to let us request not being killed for an update. Alas, there's still a lot of work to do here. I think that's the resolution really everyone wants 😓

/dup #9914

@zadjii-msft commented on GitHub (Aug 18, 2022): We're still really trying to work with the Store team here to let us request not being killed for an update. Alas, there's still a lot of work to do here. I think that's the resolution really everyone wants 😓 /dup #9914
claunia commented 2026-01-31 06:06:35 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 18, 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 18, 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#18197
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?