starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Some client app closes randomly after idle (even with sleep disabled) #21409

New Issue
Open
opened 2026-01-31 07:43:51 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 07:43:51 +00:00
Owner
Copy Link

Originally created by @colin-heberling on GitHub (Mar 18, 2024).

Windows Terminal version

1.19.10573.0

Windows build number

10.0.19045.4046

Other Software

No response

Steps to reproduce

Don't know yet, sometimes it happens once every couple weeks, other times 2-3 times a week.

Expected Behavior

Terminal doesn't close or terminate unless I tell it to.

Actual Behavior

I have Terminal installed on 2 different desktop computers, one with Windows 10, the other with Windows 11.

  1. Sleep is disabled on both,
  2. power settings set to performance,
  3. advanced app settings set to 'always' for background permissions
  4. in advanced control panel settings for power options, made sure sleep and hibernate are set to never, 'put hard disk to sleep' set to never
  5. changed Terminal advanced profile options so that terminate behavior is set to 'never close automatically'

The error happens intermittently, and does not happen at the same time on both computers, suggesting that it is not related to Windows Store updates.

After applying change 5 listed above, Terminal doesn't close, but all sessions are still terminated with following error message:

[process exited with code 3221225786 (0xc000013a)] You can now close this terminal with Ctrl+D, or press Enter to restart.

Previous session processes are no longer running in background either.

Originally created by @colin-heberling on GitHub (Mar 18, 2024). ### Windows Terminal version 1.19.10573.0 ### Windows build number 10.0.19045.4046 ### Other Software _No response_ ### Steps to reproduce Don't know yet, sometimes it happens once every couple weeks, other times 2-3 times a week. ### Expected Behavior Terminal doesn't close or terminate unless I tell it to. ### Actual Behavior I have Terminal installed on 2 different desktop computers, one with Windows 10, the other with Windows 11. 1. Sleep is disabled on both, 2. power settings set to performance, 3. advanced app settings set to 'always' for background permissions 4. in advanced control panel settings for power options, made sure sleep and hibernate are set to never, 'put hard disk to sleep' set to never 5. changed Terminal advanced profile options so that terminate behavior is set to 'never close automatically' The error happens intermittently, and does not happen at the same time on both computers, suggesting that it is not related to Windows Store updates. After applying change 5 listed above, Terminal doesn't close, but all sessions are still terminated with following error message: `[process exited with code 3221225786 (0xc000013a)] You can now close this terminal with Ctrl+D, or press Enter to restart.` Previous session processes are no longer running in background either.
claunia added the Needs-TriageIssue-BugNeeds-Author-FeedbackNo-Recent-Activity labels 2026-01-31 07:43:51 +00:00
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-Author-Feedback Needs-Triage No-Recent-Activity
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#21409
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?