Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
sba923 opened this issue Jul 27, 2020 · 3 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@sba923
Copy link

sba923 commented 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

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jul 27, 2020
@zadjii-msft
Copy link
Member

Yep, sure is!

/dup #3915 #6726 #6743

@ghost
Copy link

ghost commented 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 ghost closed this as completed Jul 27, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jul 27, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants