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

[1.22] Terminal stops functioning after closing last window with "compatibility.allowHeadless" enabled and "windowingBehavior" set to "useExisting"/"useAnyExisting" #23192

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

Originally created by @nickamante on GitHub (Apr 23, 2025).

Originally assigned to: @carlos-zamora on GitHub.

Windows Terminal version

1.22.10730.0

Windows build number

10.0.26100 (Windows 11)
10.0.19045 (Windows 10)

Other Software

No response

Steps to reproduce

  • Enable Settings > Compatibility > Allow Windows Terminal to run in the background
  • Close all existing Terminal windows
  • Attempt to re-launch Terminal (directly via Start > Terminal or via Global Summon hotkey)
    • Terminal does not launch
  • Attempt to launch Command Prompt, Windows Powershell, Powershell 7 (x64)
    • Terminal does not launch; after ~30 seconds the non-terminal version of the app launches.

Expected Behavior

Terminal remains running in the background and launching new Terminal windows continues to work.

Actual Behavior

  • After closing the last window, WindowsTerminal.exe remains running in Task Manager.
  • If Appearance > Always display an icon in the notification area is enabled, left-clicking the icon or right-click Focus Terminal has no effect. Under Windows > the last window to be closed remains listed.
  • New terminal windows will not launch until the WindowsTerminal.exe process is killed in Task Manager.
  • Turning off Allow Windows Terminal to run in the background causes the WindowsTerminal.exe process to exit after the last window is closed and allows re-launch
Originally created by @nickamante on GitHub (Apr 23, 2025). Originally assigned to: @carlos-zamora on GitHub. ### Windows Terminal version 1.22.10730.0 ### Windows build number 10.0.26100 (Windows 11) 10.0.19045 (Windows 10) ### Other Software _No response_ ### Steps to reproduce * Enable `Settings > Compatibility > Allow Windows Terminal to run in the background` * Close all existing Terminal windows * Attempt to re-launch Terminal (directly via Start > Terminal or via Global Summon hotkey) * **Terminal does not launch** * Attempt to launch Command Prompt, Windows Powershell, Powershell 7 (x64) * **Terminal does not launch**; after ~30 seconds the non-terminal version of the app launches. ### Expected Behavior Terminal remains running in the background and launching new Terminal windows continues to work. ### Actual Behavior * After closing the last window, `WindowsTerminal.exe` remains running in Task Manager. * If `Appearance > Always display an icon in the notification area` is enabled, left-clicking the icon or right-click Focus Terminal has no effect. Under `Windows >` the last window to be closed remains listed. * New terminal windows will not launch until the `WindowsTerminal.exe` process is killed in Task Manager. * Turning off `Allow Windows Terminal to run in the background` causes the `WindowsTerminal.exe` process to exit after the last window is closed and allows re-launch
claunia added the Issue-BugNeeds-Tag-FixProduct-TerminalPriority-1Area-Windowing labels 2026-01-31 08:35:01 +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 Area-Windowing Issue-Bug Needs-Tag-Fix Priority-1 Product-Terminal
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#23192
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?