Windows Terminal randomly closes. #14348

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

Huh. There's unfortunately no cabs in the feedback link, which makes me think the Terminal didn't actually crash during the feedback hub recording.

Maybe it just got updated, and force-closed by the Store? Does this still repro for you on 1.8.1521.0?

@zadjii-msft commented on GitHub (Jul 6, 2021): Huh. There's unfortunately no cabs in the feedback link, which makes me think the Terminal didn't actually crash during the feedback hub recording. Maybe it just got updated, and force-closed by the Store? Does this still repro for you on 1.8.1521.0?

claunia commented

@jhakeinson commented on GitHub (Jul 6, 2021):

Thanks for responding @zadjii-msft.

I'm sure that the Terminal is not in the middle of updating when this issue happened. And it happened multiple times randomly (mostly when I'm using my WSL Ubuntu distro). I already tried the following but with no luck:

Uninstall and reinstall Windows Terminal
Uninstall and reinstall my WSL distro.
I set the "Profile termination behavior" options of my Ubuntu profile to "Never automatically terminate".

I'm not really sure how to reproduce this issue because it happens randomly. I'm not sure what triggers it.

@jhakeinson commented on GitHub (Jul 6, 2021): Thanks for responding @zadjii-msft. I'm sure that the Terminal is not in the middle of updating when this issue happened. And it happened multiple times randomly (mostly when I'm using my WSL Ubuntu distro). I already tried the following but with no luck: - Uninstall and reinstall Windows Terminal - Uninstall and reinstall my WSL distro. - I set the "Profile termination behavior" options of my Ubuntu profile to "Never automatically terminate". I'm not really sure how to reproduce this issue because it happens randomly. I'm not sure what triggers it.

claunia commented

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

Weird. Well, without a consistent repro, or a stack trace, or something, I'm not sure what we can do with this. If you've got windbg installed, you could maybe collect a dump with "post-mortem debugging". Otherwise I'm not sure how to get something actionable here 😕

@zadjii-msft commented on GitHub (Jul 6, 2021): Weird. Well, without a consistent repro, or a stack trace, or something, I'm not sure what we can do with this. If you've got windbg installed, you could maybe collect a dump with ["post-mortem debugging"](https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/enabling-postmortem-debugging). Otherwise I'm not sure how to get something actionable here 😕

claunia commented

@jhakeinson commented on GitHub (Jul 6, 2021):

Thanks. I will try to repro the issue later with windbg or other debug tools that I can find and send the details here.

@jhakeinson commented on GitHub (Jul 6, 2021): Thanks. I will try to repro the issue later with windbg or other debug tools that I can find and send the details here.

claunia commented

@jhakeinson commented on GitHub (Jul 9, 2021):

@zadjii-msft Sorry for the late follow-up for the additional details on this issue.

I tried reproducing the bug and I used Feedback Hub to record everything. Please check this Feedback Hub link:

https://aka.ms/AAd1c6q

Thank you.

@jhakeinson commented on GitHub (Jul 9, 2021): @zadjii-msft Sorry for the late follow-up for the additional details on this issue. I tried reproducing the bug and I used Feedback Hub to record everything. Please check this Feedback Hub link: https://aka.ms/AAd1c6q Thank you.

claunia commented

@FurmanSK commented on GitHub (Oct 31, 2021):

I've had this happen twice now. I believe I'm using the one from MS store. The programs are still running though and I'm not sure if there's a way to get back to their output without using task manager to close them and restart them. Any more updates on this?

@FurmanSK commented on GitHub (Oct 31, 2021): I've had this happen twice now. I believe I'm using the one from MS store. The programs are still running though and I'm not sure if there's a way to get back to their output without using task manager to close them and restart them. Any more updates on this?

claunia commented

@zadjii-msft commented on GitHub (Nov 2, 2021):

@FurmanSK You're probably looking for #9914.

I've looked high and low for the crash reported by OP here, and unfortunately, I think it's just lost to the backend. I'm not sure it ever got plumbed all the way through, for whatever reason. If this is still happening, could you try following the steps in this post to set up automatic crash dumps? If that works, then you should be able to automatically get a .dmp of the terminal when it crashes. Then, can you zip that dump up and send it to us, so we can investigate? Thanks!

@zadjii-msft commented on GitHub (Nov 2, 2021): @FurmanSK You're probably looking for #9914. I've looked high and low for the crash reported by OP here, and unfortunately, I think it's just lost to the backend. I'm not sure it ever got plumbed all the way through, for whatever reason. If this is still happening, could you try following the steps in [this post](https://www.meziantou.net/tip-automatically-create-a-crash-dump-file-on-error.htm) to set up automatic crash dumps? If that works, then you should be able to automatically get a `.dmp` of the terminal when it crashes. Then, can you zip that dump up and send it to us, so we can investigate? Thanks!

claunia commented

@ghost commented on GitHub (Nov 6, 2021):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Nov 6, 2021): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.

claunia commented

@pif17 commented on GitHub (Nov 22, 2024):

3 years later, it's still a problem.
No error message, No error number, No stack trace, nothing to help user to have real informations to understand the problem.

@pif17 commented on GitHub (Nov 22, 2024): 3 years later, it's still a problem. No error message, No error number, No stack trace, nothing to help user to have real informations to understand the problem.

claunia commented

@zadjii-msft commented on GitHub (Nov 22, 2024):

@pif17 Almost certainly, you got hit by #18119. We recently pushed an update. The Store probably killed the Terminal to install that update. We tried to ask the store to not do that, but alas, we didn't specify all the magic incantation to get the Store to not do that.

@zadjii-msft commented on GitHub (Nov 22, 2024): @pif17 Almost certainly, you got hit by #18119. We recently pushed an update. The Store probably killed the Terminal to install that update. We tried to ask the store to not do that, but alas, we didn't specify **all** the magic incantation to get the Store to not do that.

claunia commented

@pif17 commented on GitHub (Nov 25, 2024):

Thanks for your answer, you may have the good reason.
As simple user, loosing works without explanation is very frustrating.
As advanced user, discovering that is done because you don't have the hand on update and someone far away take you for a child, is very, let's says, disappointing.
As developer, it gives you a taste of unfinished work without plan to back to the original state after crash.
To finish, as embedded and OS developper, we just ask why don't Ms do something reliable with 2 versions of DLL or EXE loaded in memory, one updated, an other to keep software that use it alive. Waiting for a reload to update.
Your program is nice, it gives more eyes candies that command.com but make it just reliable please, don't let user think they don't do valuable work with uncontrollable update that kills days of work.
In a perfect world, every opened terminals must be conditions to stop every updates, including windows update, because someone do valuable work on his computer.

@pif17 commented on GitHub (Nov 25, 2024): Thanks for your answer, you may have the good reason. As simple user, loosing works without explanation is very frustrating. As advanced user, discovering that is done because you don't have the hand on update and someone far away take you for a child, is very, let's says, disappointing. As developer, it gives you a taste of unfinished work without plan to back to the original state after crash. To finish, as embedded and OS developper, we just ask why don't Ms do something reliable with 2 versions of DLL or EXE loaded in memory, one updated, an other to keep software that use it alive. Waiting for a reload to update. Your program is nice, it gives more eyes candies that command.com but make it just reliable please, don't let user think they don't do valuable work with uncontrollable update that kills days of work. In a perfect world, every opened terminals must be conditions to stop every updates, including windows update, because someone do valuable work on his computer.

claunia commented

@zdm commented on GitHub (Jan 12, 2025):

Same problem for me, all opened terminal windows suddenly closing.
This is very annoying, especially if some jobs were started there.

@zdm commented on GitHub (Jan 12, 2025): Same problem for me, all opened terminal windows suddenly closing. This is very annoying, especially if some jobs were started there.

claunia commented

@7F11 commented on GitHub (Feb 21, 2025):

+1.
In the past two weeks Windows Terminal started to crash randomly. MTBF is about two days.
No keypress is necessary, the idle terminal windows just disappear suddenly.

Update: a few seconds before the crash the pointer turns into sand-glass.

@7F11 commented on GitHub (Feb 21, 2025): +1. In the past two weeks Windows Terminal started to crash randomly. MTBF is about two days. No keypress is necessary, the idle terminal windows just disappear suddenly. Update: a few seconds before the crash the pointer turns into sand-glass.

claunia commented

@vient commented on GitHub (Mar 11, 2025):

Happened and is still happening for me, last time was 5 minutes ago. Store shows that I have v1.21.10351.0 installed and that it is current version - not sure why not v1.22 which seems to be last stable version on github. Maybe v1.21 does not have a fix for mentioned #18119?

Edit: OK, it seems that the fix for that issue is only available in the latest v1.23.10353.0, at least considering I'm using win11 24H2 (#18252)

@vient commented on GitHub (Mar 11, 2025): Happened and is still happening for me, last time was 5 minutes ago. Store shows that I have v1.21.10351.0 installed and that it is current version - not sure why not v1.22 which seems to be last stable version on github. Maybe v1.21 does not have a fix for mentioned #18119? Edit: OK, it seems that the fix for that issue is only available in the latest [v1.23.10353.0](https://github.com/microsoft/terminal/releases/tag/v1.23.10353.0), at least considering I'm using win11 24H2 (#18252)

claunia commented