Terminal doesn't survive PC hibernation #4575

Closed
opened 2026-01-30 23:50:58 +00:00 by claunia · 9 comments
Owner

Originally created by @SimonWellborne on GitHub (Oct 21, 2019).

Environment

Microsoft Windows [Version 10.0.18990.1]
Windows Terminal (Preview) 0.5.2762.0

Steps to reproduce

  1. Open Windows Terminal
  2. Place PC into Hibernation
  3. Awake PC from Hibernation

Expected behavior

Expect Windows Terminal to remain open and maintain the state of the tabs in use prior to hibernation.

Actual behavior

I utilise between 1-2 Windows Terminal windows, each containing multiple tabs through the course of a normal day. I place the PC into hibernation, resuming either a few hours later or the next day and find all Windows Terminal windows closed.

All other applications maintain their state across the hibernation process.

Originally created by @SimonWellborne on GitHub (Oct 21, 2019). # Environment Microsoft Windows [Version 10.0.18990.1] Windows Terminal (Preview) 0.5.2762.0 # Steps to reproduce 1. Open Windows Terminal 2. Place PC into Hibernation 3. Awake PC from Hibernation # Expected behavior Expect Windows Terminal to remain open and maintain the state of the tabs in use prior to hibernation. # Actual behavior I utilise between 1-2 Windows Terminal windows, each containing multiple tabs through the course of a normal day. I place the PC into hibernation, resuming either a few hours later or the next day and find all Windows Terminal windows closed. All other applications maintain their state across the hibernation process.
Author
Owner

@HBelusca commented on GitHub (Oct 23, 2019):

All these tabs are "connected" to console applications opened on the local computer? (i.e. no remote ssh sessions are running inside them?)

@HBelusca commented on GitHub (Oct 23, 2019): All these tabs are "connected" to console applications opened on the local computer? (i.e. no remote ssh sessions are running inside them?)
Author
Owner

@DHowett-MSFT commented on GitHub (Oct 23, 2019):

/feedback

@DHowett-MSFT commented on GitHub (Oct 23, 2019): /feedback
Author
Owner

@ghost commented on GitHub (Oct 23, 2019):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?

Thanks!

image image

@ghost commented on GitHub (Oct 23, 2019): Hi there!<br><br>Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?<br><br>Thanks!<br><br>![image](https://user-images.githubusercontent.com/18221333/62478757-b69d0d00-b760-11e9-9626-1fa33c91e7c5.png) ![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
Author
Owner

@SimonWellborne commented on GitHub (Oct 24, 2019):

All these tabs are "connected" to console applications opened on the local computer? (i.e. no remote ssh sessions are running inside them?)

Forgot to mention that I predominantly use WSL (Ubuntu) tabs. When I open a new WSL tab its default directory is /mnt/c/Users/simon

I've tried leaving the WSL tab at either this directory, or in ~, but no difference.

@SimonWellborne commented on GitHub (Oct 24, 2019): > All these tabs are "connected" to console applications opened on the local computer? (i.e. no remote ssh sessions are running inside them?) Forgot to mention that I predominantly use WSL (Ubuntu) tabs. When I open a new WSL tab its default directory is /mnt/c/Users/simon I've tried leaving the WSL tab at either this directory, or in ~, but no difference.
Author
Owner

@SimonWellborne commented on GitHub (Oct 24, 2019):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?

Thanks!

image image

https://aka.ms/AA6e8dh

@SimonWellborne commented on GitHub (Oct 24, 2019): > Hi there! > > Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end? > > Thanks! > > ![image](https://user-images.githubusercontent.com/18221333/62478757-b69d0d00-b760-11e9-9626-1fa33c91e7c5.png) ![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png) https://aka.ms/AA6e8dh
Author
Owner

@Alonski commented on GitHub (Jan 12, 2021):

Chiming in that I see similar behavior.
I use Pwsh in Terminal. After hibernation Terminal is closed.
However, any processes that were running in Powershell stay running although I can't view them.
I end up having to kill the processes with Task Manager and respawn them.

Is there any info that I can provide to help?

@Alonski commented on GitHub (Jan 12, 2021): Chiming in that I see similar behavior. I use Pwsh in Terminal. After hibernation Terminal is closed. However, any processes that were running in Powershell stay running although I can't view them. I end up having to kill the processes with Task Manager and respawn them. Is there any info that I can provide to help?
Author
Owner

@zadjii-msft commented on GitHub (Aug 18, 2022):

Hey it's been like, 3 years since this was filed - is this still happening? It's possible that the store just took this opportunity to update the Terminal (and also just closed it), but if it happens on every hibernate, then that's not it.

If it is still happening, can you try following the steps in this post to set up automatic crash dumps? (For more info, see this link) 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 (Aug 18, 2022): Hey it's been like, 3 years since this was filed - is this still happening? It's possible that the store just took this opportunity to update the Terminal (and also just closed it), but if it happens on _every_ hibernate, then that's not it. If it is still happening, can 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? (For more info, see [this link](https://docs.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-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!
Author
Owner

@ghost commented on GitHub (Aug 22, 2022):

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 (Aug 22, 2022): 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**.
Author
Owner

@duaneking commented on GitHub (Feb 14, 2024):

I'm getting this issue. I had a terminal opened as admin with multiple DOS command tabs and a single wsl tab for ubuntu crash, it was open when I hibernated my computer last night and hibernating it this morning resulted in no open terminal so I was forced to restart i and reset up my development environments and activate my virtual environments again.

This is annoying and lowering productivity as I just had to spend the first 20 minute of the day debugging and reinitializing a system that was working perfectly the night before.

This should be reopened.

@duaneking commented on GitHub (Feb 14, 2024): I'm getting this issue. I had a terminal opened as admin with multiple DOS command tabs and a single wsl tab for ubuntu crash, it was open when I hibernated my computer last night and hibernating it this morning resulted in no open terminal so I was forced to restart i and reset up my development environments and activate my virtual environments again. This is annoying and lowering productivity as I just had to spend the first 20 minute of the day debugging and reinitializing a system that was working perfectly the night before. This should be reopened.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#4575