starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 16:05:21 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Restarting Microsoft Edge to install Update killed all Open Windows Teminals #14713

New Issue
Closed
opened 2026-01-31 04:17:32 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 04:17:32 +00:00
Owner
Copy Link

Originally created by @satya-marigold on GitHub (Jul 28, 2021).

Windows Terminal version (or Windows build number)

1.9.1942.0

Other Software

No response

Steps to reproduce

Have a running windows Terminal Session. I was using a WSL 2 terminal. Then restart edge when it prompts for the update

Expected Behavior

Windows Terminals remain open

Actual Behavior

All the terminals shutdown

Originally created by @satya-marigold on GitHub (Jul 28, 2021). ### Windows Terminal version (or Windows build number) 1.9.1942.0 ### Other Software _No response_ ### Steps to reproduce Have a running windows Terminal Session. I was using a WSL 2 terminal. Then restart edge when it prompts for the update ### Expected Behavior Windows Terminals remain open ### Actual Behavior All the terminals shutdown
claunia added the Resolution-ExternalResolution-Duplicate labels 2026-01-31 04:17:32 +00:00
claunia commented 2026-01-31 04:17:33 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 28, 2021):

Huh, that's certainly weird. Are you sure you were on 1.9.1942.0 before you updated Edge? It might be possible that the OS took that opportunity to check for updates to the Terminal and update that as well. We often get reports of "the terminal just crashed randomly" a little while after a Terminal update is shipped, when the OS decides to force-update the app.

Can you look through the Event Viewer to see if there are any logged events for the Terminal?

@zadjii-msft commented on GitHub (Jul 28, 2021): Huh, that's certainly weird. Are you sure you were on 1.9.1942.0 before you updated Edge? It might be possible that the OS took that opportunity to check for updates to the Terminal and update that as well. We often get reports of "the terminal just crashed randomly" a little while after a Terminal update is shipped, when the OS decides to force-update the app. Can you look through the Event Viewer to see if there are any logged events for the Terminal?
claunia commented 2026-01-31 04:17:34 +00:00
Author
Owner
Copy Link

@satya-marigold commented on GitHub (Jul 28, 2021):

Apologies, but is there a tip for filtering through event viewer for identifying Windows Terminal Logs? I haven't used it before

@satya-marigold commented on GitHub (Jul 28, 2021): Apologies, but is there a tip for filtering through event viewer for identifying Windows Terminal Logs? I haven't used it before
claunia commented 2026-01-31 04:17:34 +00:00
Author
Owner
Copy Link

@satya-marigold commented on GitHub (Jul 28, 2021):

I looked through the errors and I could find a WindowsUpdateClient error that lists > Installation Failure: Windows failed to install the following update with error 0x80073D02: 9N0DX20HK701-Microsoft.WindowsTerminal.

It is a bit troubling that restarting Edge for installing an update triggers an attempt to update the terminal as well.

Edit: I also realized that while windows terminal shut down, the tmux instance running inside WSL2 didn't shut down so my script finished execution and I could just attach to the tmux shell again.

@satya-marigold commented on GitHub (Jul 28, 2021): I looked through the errors and I could find a WindowsUpdateClient error that lists > Installation Failure: Windows failed to install the following update with error 0x80073D02: 9N0DX20HK701-Microsoft.WindowsTerminal. It is a bit troubling that restarting Edge for installing an update triggers an attempt to update the terminal as well. Edit: I also realized that while windows terminal shut down, the tmux instance running inside WSL2 didn't shut down so my script finished execution and I could just attach to the tmux shell again.
claunia commented 2026-01-31 04:17:34 +00:00
Author
Owner
Copy Link

@shuffle2 commented on GitHub (Jul 29, 2021):

Unfortunately this behavior forced me to disable the Store auto-updating apps globally. It's not acceptable to get all content of terminal sessions blown away unexpectedly, ever.

@shuffle2 commented on GitHub (Jul 29, 2021): Unfortunately this behavior forced me to disable the Store auto-updating apps globally. It's not acceptable to get all content of terminal sessions blown away unexpectedly, ever.
claunia commented 2026-01-31 04:17:34 +00:00
Author
Owner
Copy Link

@zakius commented on GitHub (Jul 30, 2021):

when the OS decides to force-update the app

is there any way to prevent that? cause that's pretty destructive behavior that may cause data loss

well, I guess if I sideload store should leave me alone?

@zakius commented on GitHub (Jul 30, 2021): > when the OS decides to force-update the app is there any way to prevent that? cause that's pretty destructive behavior that may cause data loss well, I guess if I sideload store should leave me alone?
claunia commented 2026-01-31 04:17:34 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 5, 2021):

After looking through other threads, we're all pretty sure that this is just a variation on:

@zadjii-msft commented on GitHub (Aug 5, 2021): After looking through other threads, we're all pretty sure that this is just a variation on: * /dup #6726 * /dup #3915 * /dup https://github.com/microsoft/WindowsAppSDK/issues/300
claunia commented 2026-01-31 04:17:35 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 5, 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 (Aug 5, 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!
claunia commented 2026-01-31 04:17:35 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 5, 2021):

Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!

@ghost commented on GitHub (Aug 5, 2021): Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. 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 Resolution-Duplicate Resolution-External
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#14713
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?