starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

windows store update of terminal breaks running instance #18700

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

Originally created by @jtnord on GitHub (Oct 17, 2022).

Windows Terminal version

1.15.2875.0

Windows build number

10.0.22000.1098

Other Software

clink 1.3.46.d6fdd0

Steps to reproduce

Not fully steps to reproduce... (and would need to force an update somehow via windows store?)

Have a terminal window open with several cmd.exe sessions running (clink is injected into these although I do not believe it changes the outcome, however you would not obviously see it)

When Terminal is updated by windows store the terminal UI is gone, however the sessions running within it are not. (it also appears as though the terminal process is still present but without the UI)

this was noticed as clink will perform and update the console prompt in the background (e.g. git status and other things) and from these cmd.exe session that have no windows anymore clink will try and run some more commands (and these tasks which are run every minute or so fail with 0xc000...145)

Expected Behavior

Windows store upgrade should not break running sessions.

Actual Behavior

it appears as though the windows store update of terminal breaks running sessions.

Originally created by @jtnord on GitHub (Oct 17, 2022). ### Windows Terminal version 1.15.2875.0 ### Windows build number 10.0.22000.1098 ### Other Software [clink ](https://github.com/chrisant996/clink) 1.3.46.d6fdd0 ### Steps to reproduce Not fully steps to reproduce... (and would need to force an update somehow via windows store?) Have a terminal window open with several cmd.exe sessions running (clink is injected into these although I do not believe it changes the outcome, however you would not obviously see it) When Terminal is updated by windows store the terminal UI is gone, however the sessions running within it are not. (it also appears as though the terminal process is still present but without the UI) this was noticed as clink will perform and update the console prompt in the background (e.g. git status and other things) and from these cmd.exe session that have no windows anymore clink will try and run some more commands (and these tasks which are run every minute or so fail with 0xc000...145) ### Expected Behavior Windows store upgrade should not break running sessions. ### Actual Behavior it appears as though the windows store update of terminal breaks running sessions.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:21:44 +00:00
claunia commented 2026-01-31 06:21:45 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Oct 18, 2022):

Yeah, unfortunately it's a known issue that the store updating windows terminal ends up closing Windows Terminal itself. We're tracking that over in #3915. As for the ophaning, we're tracking that over in #9914.

We're still trying to work with the Store team to let us request not being killed for an update. Sorry, closing this as a /dup of #9914

@carlos-zamora commented on GitHub (Oct 18, 2022): Yeah, unfortunately it's a known issue that the store updating windows terminal ends up closing Windows Terminal itself. We're tracking that over in #3915. As for the ophaning, we're tracking that over in #9914. We're still trying to work with the Store team to let us request not being killed for an update. Sorry, closing this as a /dup of #9914
claunia commented 2026-01-31 06:21:45 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 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 (Oct 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#18700
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?