Update has closed running instance of Terminal 🤬 #16673

Closed
opened 2026-01-31 05:19:15 +00:00 by claunia · 4 comments
Owner

Originally created by @mailinglists35 on GitHub (Feb 6, 2022).

Windows Terminal version

1.13.10336.0

Windows build number

10.0.19044.1466

Other Software

No response

Steps to reproduce

use Windows Terminal Preview

wake up the next day

Terminal preview is no longer in taskbar, all my tabs gone, work lost 🤬

Expected Behavior

wait until I voluntarily restart or close the terminal

Actual Behavior

Terminal preview is no longer in taskbar, all my tabs gone, work lost 🤬

Originally created by @mailinglists35 on GitHub (Feb 6, 2022). ### Windows Terminal version 1.13.10336.0 ### Windows build number 10.0.19044.1466 ### Other Software _No response_ ### Steps to reproduce use Windows Terminal Preview wake up the next day Terminal preview is no longer in taskbar, all my tabs gone, work lost 🤬 ### Expected Behavior wait until I voluntarily restart or close the terminal ### Actual Behavior Terminal preview is no longer in taskbar, all my tabs gone, work lost 🤬
claunia added the Resolution-Duplicate label 2026-01-31 05:19:15 +00:00
Author
Owner

@j4james commented on GitHub (Feb 6, 2022):

As I understand it, it's the app store that shuts down the terminal whenever there is an update. For more info, and suggestions on how you can workaround this, see issue #3915 and #6726.

@j4james commented on GitHub (Feb 6, 2022): As I understand it, it's the app store that shuts down the terminal whenever there is an update. For more info, and suggestions on how you can workaround this, see issue #3915 and #6726.
Author
Owner

@mailinglists35 commented on GitHub (Feb 6, 2022):

tovine opened this issue on Dec 11, 2019

so I guess I was just lucky to never occur on me until now.

i'm facepalming when I think that since issue first reported you have never managed to take the issue to ms store team and make the store simply add an exception for the terminal and instead you leave it for the user to find ways to work around it.

@mailinglists35 commented on GitHub (Feb 6, 2022): >tovine opened this issue on Dec 11, 2019 so I guess I was just lucky to never occur on me until now. i'm facepalming when I think that since issue first reported you have never managed to take the issue to ms store team and make the store simply add an exception for the terminal and instead you leave it for the user to find ways to work around it.
Author
Owner

@zadjii-msft commented on GitHub (Feb 7, 2022):

Yea, this is tracked elsewhere.

/dup #3915
/dup #6726

@zadjii-msft commented on GitHub (Feb 7, 2022): Yea, this is tracked elsewhere. /dup #3915 /dup #6726
Author
Owner

@ghost commented on GitHub (Feb 7, 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 (Feb 7, 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.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#16673