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

The MoAppHang thread #18002

New Issue
Closed
opened 2026-01-31 06:00:53 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 06:00:53 +00:00
Owner
Copy Link

Originally created by @robgom on GitHub (Jul 22, 2022).

Windows Terminal version

1.13.2205.23001

Windows build number

10.0.19043.1766

Other Software

No response

Steps to reproduce

  1. Open few cards in WindowsTerminal, including: cmd, powershell, ipython executed from cmd
  2. Interact with those daily, but leave everything running

Expected Behavior

WindowsTerminal executes smoothly.

Actual Behavior

WindowsTerminal crashes. It's been crashing for months now. At various intervals. I couldn't determine any action to cause this. Today I switched off remote desktop and when logged in in few minutes, terminal was gone.
The only trace was in Event Viewer:

Event Name: MoAppHang
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.WindowsTerminal_1.13.11431.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.13.2205.23001
P4: 628bd6e7
P5: 0c21
P6: 2097152
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7AF0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B2F.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B4D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7BBC.tmp.txt
\\?\C:\Users\RGomulk\AppData\Local\Temp\WER7FA5.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa\minidump.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa\memory.hdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa\minidump.3f88.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa\minidump.5990.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa\minidump.3478.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa\minidump.46b0.mdmp

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_0c6eae25-ca99-44ed-ac03-564ef4cf04aa

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6ff345e4-bc39-4cf6-8a62-596843d57bd6
Report Status: 268435456
Hashed bucket: 86e421f1a50f55fde4a62f6775b8f8e5
Cab Guid: 0

Before which I got:

Fault bucket , type 0
Event Name: MoAppHang
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.WindowsTerminal_1.13.11431.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.13.2205.23001
P4: 628bd6e7
P5: 0c21
P6: 2097152
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7AF0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B2F.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B4D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7BBC.tmp.txt
\\?\C:\Users\RGomulk\AppData\Local\Temp\WER7FA5.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa\minidump.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa\memory.hdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa\minidump.3f88.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa\minidump.5990.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa\minidump.3478.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa\minidump.46b0.mdmp

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6ff345e4-bc39-4cf6-8a62-596843d57bd6
Report Status: 4
Hashed bucket: 
Cab Guid: 0

and

The program WindowsTerminal.exe version 1.13.2205.23001 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
 Process ID: 2ff4
 Start Time: 01d8910361242def
 Termination Time: 4294967295
 Application Path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.13.11431.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
 Report Id: 6ff345e4-bc39-4cf6-8a62-596843d57bd6
 Faulting package full name: Microsoft.WindowsTerminal_1.13.11431.0_x64__8wekyb3d8bbwe
 Faulting package-relative application ID: App
 Hang type: Quiesce

I have both windows terminal and windows terminal preview installed. I'm not sure which exhibited the behaviour, but if remember correctly, both were crashing similarly.

Originally created by @robgom on GitHub (Jul 22, 2022). ### Windows Terminal version 1.13.2205.23001 ### Windows build number 10.0.19043.1766 ### Other Software _No response_ ### Steps to reproduce 1. Open few cards in WindowsTerminal, including: cmd, powershell, ipython executed from cmd 2. Interact with those daily, but leave everything running ### Expected Behavior WindowsTerminal executes smoothly. ### Actual Behavior WindowsTerminal crashes. It's been crashing for months now. At various intervals. I couldn't determine any action to cause this. Today I switched off remote desktop and when logged in in few minutes, terminal was gone. The only trace was in Event Viewer: ```Fault bucket 0, type 5 Event Name: MoAppHang Response: Not available Cab Id: 0 Problem signature: P1: Microsoft.WindowsTerminal_1.13.11431.0_x64__8wekyb3d8bbwe P2: praid:App P3: 1.13.2205.23001 P4: 628bd6e7 P5: 0c21 P6: 2097152 P7: P8: P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7AF0.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B2F.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B4D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7BBC.tmp.txt \\?\C:\Users\RGomulk\AppData\Local\Temp\WER7FA5.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa\minidump.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa\memory.hdmp \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa\minidump.3f88.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa\minidump.5990.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa\minidump.3478.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa\minidump.46b0.mdmp These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_0c6eae25-ca99-44ed-ac03-564ef4cf04aa Analysis symbol: Rechecking for solution: 0 Report Id: 6ff345e4-bc39-4cf6-8a62-596843d57bd6 Report Status: 268435456 Hashed bucket: 86e421f1a50f55fde4a62f6775b8f8e5 Cab Guid: 0 ``` Before which I got: ``` Fault bucket , type 0 Event Name: MoAppHang Response: Not available Cab Id: 0 Problem signature: P1: Microsoft.WindowsTerminal_1.13.11431.0_x64__8wekyb3d8bbwe P2: praid:App P3: 1.13.2205.23001 P4: 628bd6e7 P5: 0c21 P6: 2097152 P7: P8: P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7AF0.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B2F.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B4D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7BBC.tmp.txt \\?\C:\Users\RGomulk\AppData\Local\Temp\WER7FA5.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa\minidump.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa\memory.hdmp \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa\minidump.3f88.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa\minidump.5990.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa\minidump.3478.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa\minidump.46b0.mdmp These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_Microsoft.Window_4bcfb2ab6ceed78368cad6844db4f7cf44eba4_3ff56f4b_cab_0c6eae25-ca99-44ed-ac03-564ef4cf04aa Analysis symbol: Rechecking for solution: 0 Report Id: 6ff345e4-bc39-4cf6-8a62-596843d57bd6 Report Status: 4 Hashed bucket: Cab Guid: 0 ``` and ``` The program WindowsTerminal.exe version 1.13.2205.23001 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel. Process ID: 2ff4 Start Time: 01d8910361242def Termination Time: 4294967295 Application Path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.13.11431.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Report Id: 6ff345e4-bc39-4cf6-8a62-596843d57bd6 Faulting package full name: Microsoft.WindowsTerminal_1.13.11431.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App Hang type: Quiesce ``` I have both windows terminal and windows terminal preview installed. I'm not sure which exhibited the behaviour, but if remember correctly, both were crashing similarly.
claunia commented 2026-01-31 06:00:55 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 22, 2022):

Huh. This is bucket 86e421f1-a50f-55fd-e4a6-2f6775b8f8e5 which is the moapphang bucket. Usually that's only really hit on upgrade, but there's quite a few more hits than I'd expect...

MSFT:38947155 tracks a variant of this one. a9fa6747-7f80-2130-9fd8-3b2f7d420159 also has a pile of hits and dupes to it.

Y'know though, the crashes are for Terminal version 1.13.11431.0, but it looks like you've got Terminal 1.13.2205.23001 installed currently. I'd guess that this IS the upgrade moapphang!

(fwiw the dump here had basically nothing useful in it - all our threads looked like they were in perfectly good, unblocked states, and the rest of the threads didn't have symbols)

@zadjii-msft commented on GitHub (Jul 22, 2022): Huh. This is bucket 86e421f1-a50f-55fd-e4a6-2f6775b8f8e5 which is the moapphang bucket. Usually that's only really hit on upgrade, but there's quite a few more hits than I'd expect... MSFT:38947155 tracks a variant of this one. a9fa6747-7f80-2130-9fd8-3b2f7d420159 also has a pile of hits and dupes to it. Y'know though, the crashes are for Terminal version `1.13.11431.0`, but it looks like you've got Terminal `1.13.2205.23001` installed currently. I'd guess that this _IS_ the upgrade moapphang! (fwiw the dump here had basically nothing useful in it - all our threads looked like they were in perfectly good, unblocked states, and the rest of the threads didn't have symbols)
claunia commented 2026-01-31 06:00:56 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 22, 2022):

MoAppHangs seem to be caused by us continuing to do something even after the system asks us to suspend. I wonder if we're seeing a spike of these on 1.13+, because we've got the window state restoration, and we're waiting for the monarch to collect up all the window state. We've apparently got 5s to be ready to be suspended, so I could totally see the RPC calls taking longer than that, or just hanging around.

Thats at least a theory.

EDIT: Other theories:

HANG_QUIESCE is used to signify that a packaged Win32 process didn't exit in a timely manner during a servicing operation (uninstall, update, etc). During servicing, processes are sent Ctrl + C and WM_CLOSE messages, afterwards they have 30 seconds to exit.

If the process IsConsoleApp is True, the Ctrl + C will be sent. If WindowNum > 0, then WM_CLOSE will be sent. Otherwise, there is no way of sending Ctrl + C or window messages, so the app will not be notified. Create a window to receive WM_CLOSE or convert to a console application to receive Ctrl + C.

Elevated Processes Always Hang Quiesce

MSFT:27096508 is tracking the issue. It is present in all versions of Windows that support packaged Win32, and stems from the fact that SiHost (which sends the messages) does not run as elevated.

So we're gonna ALWAYS get a hang quiesce:

  • if the terminal is elevated
  • If there are multiple tabs and the user has the "are you sure you want to close" dialog open.
@zadjii-msft commented on GitHub (Jul 22, 2022): MoAppHangs seem to be caused by us continuing to do something even after the system asks us to suspend. I wonder if we're seeing a spike of these on 1.13+, because we've got the window state restoration, and we're waiting for the monarch to collect up all the window state. We've apparently got 5s to be ready to be suspended, so I could totally see the RPC calls taking longer than that, or just hanging around. Thats at least a theory. EDIT: Other theories: > HANG_QUIESCE is used to signify that a packaged Win32 process didn't exit in a timely manner during a servicing operation (uninstall, update, etc). During servicing, processes are sent Ctrl + C and WM_CLOSE messages, afterwards they have 30 seconds to exit. > > If the process IsConsoleApp is True, the Ctrl + C will be sent. If WindowNum > 0, then WM_CLOSE will be sent. Otherwise, there is no way of sending Ctrl + C or window messages, so the app will not be notified. Create a window to receive WM_CLOSE or convert to a console application to receive Ctrl + C. > > ### Elevated Processes Always Hang Quiesce > MSFT:27096508 is tracking the issue. It is present in all versions of Windows that support packaged Win32, and stems from the fact that SiHost (which sends the messages) does not run as elevated. So we're gonna ALWAYS get a hang quiesce: * if the terminal is elevated * If there are multiple tabs and the user has the "are you sure you want to close" dialog open.
claunia commented 2026-01-31 06:00:56 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 22, 2022):

NOTE TO SELF - DO THIS vvvv

https://docs.microsoft.com/en-us/windows/win32/rstmgr/guidelines-for-applications

This is literally 50% of our crashes. Amazing that we only have a raw count of crashes equal to the number of updates we get, but let get these out of the metrics entirely.

@zadjii-msft commented on GitHub (Jul 22, 2022): NOTE TO SELF - DO THIS vvvv https://docs.microsoft.com/en-us/windows/win32/rstmgr/guidelines-for-applications This is literally 50% of our crashes. Amazing that we only have a raw count of crashes equal to the number of updates we get, but let get these out of the metrics entirely.
claunia commented 2026-01-31 06:00:56 +00:00
Author
Owner
Copy Link

@RossWang commented on GitHub (Jul 27, 2022):

I bet this is because of an automatic update. My job on Windows Terminal that required several days to run got interrupted by the update yesterday. It's so frustrating.

Powershell, however, seems not to update when running.

@RossWang commented on GitHub (Jul 27, 2022): I bet this is because of an automatic update. My job on Windows Terminal that required several days to run got interrupted by the update yesterday. It's so frustrating. Powershell, however, seems not to update when running.
claunia commented 2026-01-31 06:00:56 +00:00
Author
Owner
Copy Link

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

:tada:This issue was addressed in #13614, which has now been successfully released as Windows Terminal Preview v1.15.228.🎉

Handy links:

@ghost commented on GitHub (Aug 18, 2022): :tada:This issue was addressed in #13614, which has now been successfully released as `Windows Terminal Preview v1.15.228`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.15.228) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
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 Priority-1 Product-Terminal Resolution-Fix-Committed 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#18002
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?