Updating via Microsoft Store app silently kills Windows Terminal and all shells running therein #9871

Closed
opened 2026-01-31 02:06:16 +00:00 by claunia · 3 comments
Owner

Originally created by @sba923 on GitHub (Jul 27, 2020).

Environment

Windows build number: 10.0.19041.388
Windows Terminal version (if applicable): 1.1.2021.0 (version after update)

Steps to reproduce

  • Start Windows Terminal, with at least one tab (in my case, was running PowerShell 7.1 preview 5)
  • Launch the "Microsoft Store" app
  • Hit "Get Updates"
  • let the updates run, including Windows Terminal's (might require hitting "Update all")

Expected behavior

The update to Windows Terminal should be delayed until all tabs have been closed

Actual behavior

Windows Terminal is forcibly closed, causing all shells therein (in my case, PowerShell was even running a script) to be killed

Originally created by @sba923 on GitHub (Jul 27, 2020). # Environment ``` Windows build number: 10.0.19041.388 Windows Terminal version (if applicable): 1.1.2021.0 (version after update) ``` # Steps to reproduce - Start Windows Terminal, with at least one tab (in my case, was running PowerShell 7.1 preview 5) - Launch the "Microsoft Store" app - Hit "Get Updates" - let the updates run, including Windows Terminal's (might require hitting "Update all") # Expected behavior The update to Windows Terminal should be delayed until all tabs have been closed # Actual behavior Windows Terminal is forcibly closed, causing all shells therein (in my case, PowerShell was even running a script) to be killed
claunia added the Resolution-Duplicate label 2026-01-31 02:06:16 +00:00
Author
Owner
@Lo0oG commented on GitHub (Jul 27, 2020): Duplicate issue - #6743 - #6726 - #3915
Author
Owner

@zadjii-msft commented on GitHub (Jul 27, 2020):

Yep, sure is!

/dup #3915 #6726 #6743

@zadjii-msft commented on GitHub (Jul 27, 2020): Yep, sure is! /dup #3915 #6726 #6743
Author
Owner

@ghost commented on GitHub (Jul 27, 2020):

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 (Jul 27, 2020): 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#9871