starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Terminal closes after wake from sleep or hibernate (even with updated Windows) #23013

New Issue
Closed
opened 2026-01-31 08:29:54 +00:00 by claunia · 11 comments
claunia commented 2026-01-31 08:29:54 +00:00
Owner
Copy Link

Originally created by @Taylor-C-Reese on GitHub (Mar 13, 2025).

Windows Terminal version

1.21.10351.0

Windows build number

24H2 Build 26100.3476

Other Software

Windows 11 sleep or hibernate

Steps to reproduce

  1. Open Windows Terminal
  2. Leave the computer for several hours
  3. Wake the computer up

All Windows Terminals are gone. The programs that they were running are no longer running.

I typically run several Windows Terminals, some running PowerShell, some WSL. I use some of them to launch GUI apps, such as vscode and a custom Python GUI app. Repeatedly, after wake from several hours, they have all been closed. It seems to be a clean close in the sense that the apps seem to have closed down cleanly.

Expected Behavior

Terminals keep running

Actual Behavior

Terminals gone. WSL debug console shows it was shut down. vscode is closed. Python GUI app no longer running.

Note that this does not always happen. I don't know exactly what causes it, but it seems to only happen after very long sleep.

Note that this does not seem to be a WSL issue. I've set WSL to not terminate, even after long use. And my non-WSL Terminals, and their apps, are also gone.

This seems to be a regression of an older bug that has been reported many times, and is reported as having been fixed in certain patches - but I'm running those patches and still getting the bug:

Originally created by @Taylor-C-Reese on GitHub (Mar 13, 2025). ### Windows Terminal version 1.21.10351.0 ### Windows build number 24H2 Build 26100.3476 ### Other Software Windows 11 sleep or hibernate ### Steps to reproduce 1. Open Windows Terminal 2. Leave the computer for several hours 3. Wake the computer up All Windows Terminals are gone. The programs that they were running are no longer running. I typically run several Windows Terminals, some running PowerShell, some WSL. I use some of them to launch GUI apps, such as vscode and a custom Python GUI app. Repeatedly, after wake from several hours, they have all been closed. It seems to be a clean close in the sense that the apps seem to have closed down cleanly. ### Expected Behavior Terminals keep running ### Actual Behavior Terminals gone. WSL debug console shows it was shut down. vscode is closed. Python GUI app no longer running. Note that this does not _always_ happen. I don't know exactly what causes it, but it seems to only happen after very long sleep. Note that this does _not_ seem to be a WSL issue. I've set WSL to not terminate, even after long use. And my non-WSL Terminals, and their apps, are also gone. This seems to be a regression of an older bug that has been reported many times, and is reported as having been fixed in certain patches - but I'm running those patches and still getting the bug: * https://github.com/microsoft/terminal/issues/12513 (Concludes "If you are experiencing this issue after installing KB5023778, please file a new issue and follow the issue reporting steps." * https://github.com/microsoft/terminal/issues/3276 - Very similar issue * https://github.com/microsoft/terminal/issues/16888 - may be related
claunia added the Needs-TriageIssue-BugNeeds-AttentionSeverity-Crash labels 2026-01-31 08:29:55 +00:00
claunia commented 2026-01-31 08:29:56 +00:00
Author
Owner
Copy Link

@similar-issues-ai[bot] commented on GitHub (Mar 13, 2025):

We've found some similar issues:

  • #12513 , similarity score: 83%
  • #14377 , similarity score: 82%
  • #7183 , similarity score: 82%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

@similar-issues-ai[bot] commented on GitHub (Mar 13, 2025): We've found some similar issues: - #12513 , similarity score: 83% - #14377 , similarity score: 82% - #7183 , similarity score: 82% If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue. > Note: You can give me feedback by 👍 or 👎 this comment.
claunia commented 2026-01-31 08:29:56 +00:00
Author
Owner
Copy Link

@Taylor-C-Reese commented on GitHub (Mar 13, 2025):

I should add that I am using modified sleep/hibernate settings in Windows (not the default settings)

@Taylor-C-Reese commented on GitHub (Mar 13, 2025): I should add that I am using modified sleep/hibernate settings in Windows (not the default settings)
claunia commented 2026-01-31 08:29:57 +00:00
Author
Owner
Copy Link

@Taylor-C-Reese commented on GitHub (Mar 13, 2025):

The bot found several others with this issue, beyond the ones I've reported. Clearly, a lot of people are experiencing this. The challenge seems that the bug is hard to reproduce deterministically - those are the hardest bugs to fix. Still, given the amount of people reporting this, I'm hopeful that someone from MSFT will take it seriously.

@Taylor-C-Reese commented on GitHub (Mar 13, 2025): The bot found several others with this issue, beyond the ones I've reported. Clearly, a lot of people are experiencing this. The challenge seems that the bug is hard to reproduce deterministically - those are the hardest bugs to fix. Still, given the amount of people reporting this, I'm hopeful that someone from MSFT will take it seriously.
claunia commented 2026-01-31 08:29:57 +00:00
Author
Owner
Copy Link

@Taylor-C-Reese commented on GitHub (Mar 26, 2025):

Microsoft - is anyone monitoring this queue? It's been two weeks and it hasn't been responded to, let alone triaged.

@Taylor-C-Reese commented on GitHub (Mar 26, 2025): Microsoft - is anyone monitoring this queue? It's been two weeks and it hasn't been responded to, let alone triaged.
claunia commented 2026-01-31 08:29:57 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 26, 2025):

Apologies - team is super short staffed this month. We're pretty deeply behind on triage.

Does this happen on 1.23 Preview?

If you enable post-mortem dumps, is there a WindowsTerminal.exe dump that's created?

@zadjii-msft commented on GitHub (Mar 26, 2025): Apologies - team is super short staffed this month. We're pretty deeply behind on triage. Does this happen on 1.23 Preview? If you [enable post-mortem dumps](https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capture-automatically), is there a WindowsTerminal.exe dump that's created?
claunia commented 2026-01-31 08:29:58 +00:00
Author
Owner
Copy Link

@Taylor-C-Reese commented on GitHub (Mar 26, 2025):

Zadjii, no need to apologize - I just wanted to make sure this is not getting lost. The challenge here is that it's hard to reliably reproduce. The shutdown seems totally clean, not a crash, and it happens when not in use.

@Taylor-C-Reese commented on GitHub (Mar 26, 2025): Zadjii, no need to apologize - I just wanted to make sure this is not getting lost. The challenge here is that it's hard to reliably reproduce. The shutdown seems totally clean, not a crash, and it happens when not in use.
claunia commented 2026-01-31 08:29:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 26, 2025):

Well, the post-mortem dumps can just be enabled and waiting in the background. Whenever you eventually see it happen again, go see if it grabbed a dump.

@zadjii-msft commented on GitHub (Mar 26, 2025): Well, the post-mortem dumps can just be enabled and waiting in the background. Whenever you eventually see it happen again, go see if it grabbed a dump.
claunia commented 2026-01-31 08:29:58 +00:00
Author
Owner
Copy Link

@Taylor-C-Reese commented on GitHub (Mar 31, 2025):

This doesn't occur every 4 days - it happens intermittently. However, as many others are reporting it, I'd hope you fix it.

@Taylor-C-Reese commented on GitHub (Mar 31, 2025): This doesn't occur every 4 days - it happens intermittently. However, as many others are reporting it, I'd hope you fix it.
claunia commented 2026-01-31 08:29:58 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Mar 31, 2025):

Unfortunately, it's already often difficult to fix a crash when we have a dump (without a repro), but pretty much impossible to guess the correct fix when we have no dump at all.

As such, I think it'd still be best to enable dumps just in case it happens to you again.

@lhecker commented on GitHub (Mar 31, 2025): Unfortunately, it's already often difficult to fix a crash when we have a dump (without a repro), but pretty much impossible to guess the correct fix when we have no dump at all. As such, I think it'd still be best to enable dumps just in case it happens to you again.
claunia commented 2026-01-31 08:29:58 +00:00
Author
Owner
Copy Link

@thatsysadmin commented on GitHub (Apr 19, 2025):

@Taylor-C-Reese

Is this still an issue for you with 1.22.250314001 and you're running the Windows Store variant by any chance? I've been having the same issue but I can reproduce it every time. I tried the .zip packaged one and it seems fine.

EDIT: Seems like a memory pressure issue on Windows's part. If the machine is short on memory, MSIX package apps seem to be the first to go (this would explain the clean kill symptom), then get restored if possible after sleep. Are you short on memory when this happens by any chance?

@thatsysadmin commented on GitHub (Apr 19, 2025): @Taylor-C-Reese Is this still an issue for you with `1.22.250314001` and you're running the Windows Store variant by any chance? I've been having the same issue but I can reproduce it every time. I tried the .zip packaged one and it seems fine. EDIT: Seems like a memory pressure issue on Windows's part. If the machine is short on memory, MSIX package apps seem to be the first to go (this would explain the clean kill symptom), then get restored if possible after sleep. Are you short on memory when this happens by any chance?
claunia commented 2026-01-31 08:29:59 +00:00
Author
Owner
Copy Link

@Taylor-C-Reese commented on GitHub (Apr 22, 2025):

@thatsysadmin I'm running the regular install, no Windows Store. Lots of RAM. Strangely, ChatGPT said that people report this with fast boot enable, and I should disable it in the BIOS. I did so, and since then, it hasn't occurred, though I don't know if that's simply luck or it's really tied somehow to fast boot.

@Taylor-C-Reese commented on GitHub (Apr 22, 2025): @thatsysadmin I'm running the regular install, no Windows Store. Lots of RAM. Strangely, ChatGPT said that people report this with fast boot enable, and I should disable it in the BIOS. I did so, and since then, it hasn't occurred, though I don't know if that's simply luck or it's really tied somehow to fast boot.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Attention Needs-Triage Severity-Crash
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#23013
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?