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

suddenly refuses to start #14067

New Issue
Closed
opened 2026-01-31 03:59:57 +00:00 by claunia · 22 comments
claunia commented 2026-01-31 03:59:57 +00:00
Owner
Copy Link

Originally created by @black-snow on GitHub (May 31, 2021).

Windows Terminal version (or Windows build number)

1.8.1444.0

Other Software

No response

Steps to reproduce

Idk. Worked fine for ages. Now after a week-end and a reboot due to a windows update and apparently also a Windows Terminal update done automatically (installed via store) it refuses to start.

Expected Behavior

Windows Terminal starts up.

Actual Behavior

Application is active in task bar for about 2 seconds then just crashes without showing even a window.

Name der fehlerhaften Anwendung: WindowsTerminal.exe, Version: 1.8.2105.24004, Zeitstempel: 0x60ac2e94
Name des fehlerhaften Moduls: ucrtbase.dll, Version: 10.0.19041.789, Zeitstempel: 0x2bd748bf
Ausnahmecode: 0xc0000409
Fehleroffset: 0x000000000007286e
ID des fehlerhaften Prozesses: 0x2aa4
Startzeit der fehlerhaften Anwendung: 0x01d755f363c37cd6
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\System32\ucrtbase.dll
Berichtskennung: e744ecdd-b0f3-43d0-af28-00fa2abbbea6
Vollständiger Name des fehlerhaften Pakets: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App

grafik

/edit: dupe of https://github.com/microsoft/terminal/issues/8358
/edit: dupe of https://github.com/microsoft/terminal/issues/10211 (apparently)

Originally created by @black-snow on GitHub (May 31, 2021). ### Windows Terminal version (or Windows build number) 1.8.1444.0 ### Other Software _No response_ ### Steps to reproduce Idk. Worked fine for ages. Now after a week-end and a reboot due to a windows update and apparently also a Windows Terminal update done automatically (installed via store) it refuses to start. ### Expected Behavior Windows Terminal starts up. ### Actual Behavior Application is active in task bar for about 2 seconds then just crashes without showing even a window. ``` Name der fehlerhaften Anwendung: WindowsTerminal.exe, Version: 1.8.2105.24004, Zeitstempel: 0x60ac2e94 Name des fehlerhaften Moduls: ucrtbase.dll, Version: 10.0.19041.789, Zeitstempel: 0x2bd748bf Ausnahmecode: 0xc0000409 Fehleroffset: 0x000000000007286e ID des fehlerhaften Prozesses: 0x2aa4 Startzeit der fehlerhaften Anwendung: 0x01d755f363c37cd6 Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Pfad des fehlerhaften Moduls: C:\WINDOWS\System32\ucrtbase.dll Berichtskennung: e744ecdd-b0f3-43d0-af28-00fa2abbbea6 Vollständiger Name des fehlerhaften Pakets: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App ``` ![grafik](https://user-images.githubusercontent.com/579733/120162857-1d729c80-c1f9-11eb-9a16-ce7efac77b90.png) /edit: dupe of https://github.com/microsoft/terminal/issues/8358 /edit: dupe of https://github.com/microsoft/terminal/issues/10211 (apparently)
claunia added the Resolution-Duplicate label 2026-01-31 03:59:57 +00:00
claunia commented 2026-01-31 03:59:58 +00:00
Author
Owner
Copy Link

@black-snow commented on GitHub (May 31, 2021):

P.S.: wsl from power shell works fine

@black-snow commented on GitHub (May 31, 2021): P.S.: `wsl` from power shell works fine
claunia commented 2026-01-31 03:59:58 +00:00
Author
Owner
Copy Link

@swahilli commented on GitHub (May 31, 2021):

I have the same issue. It was working fine on Friday, then, following a silent upgrade, it's not doing anything.

@swahilli commented on GitHub (May 31, 2021): I have the same issue. It was working fine on Friday, then, following a silent upgrade, it's not doing anything.
claunia commented 2026-01-31 03:59:58 +00:00
Author
Owner
Copy Link

@Rafagd commented on GitHub (May 31, 2021):

+1

It was working on Thursday, opened it on Friday for a job interview and it instantly crashed on me.
It has not worked since.

ps.: wsl, cmd and powershell are working fine, the problem seems to be the terminal application itself.

@Rafagd commented on GitHub (May 31, 2021): +1 It was working on Thursday, opened it on Friday for a job interview and it instantly crashed on me. It has not worked since. ps.: wsl, cmd and powershell are working fine, the problem seems to be the terminal application itself.
claunia commented 2026-01-31 03:59:59 +00:00
Author
Owner
Copy Link

@swahilli commented on GitHub (May 31, 2021):

I uninstalled and reinstalled from the app store and it's now working, but I obviously lost all my settings

@swahilli commented on GitHub (May 31, 2021): I uninstalled and reinstalled from the app store and it's now working, but I obviously lost all my settings
claunia commented 2026-01-31 03:59:59 +00:00
Author
Owner
Copy Link

@gfraiteur commented on GitHub (May 31, 2021):

Same here. Broken after silent update.

@gfraiteur commented on GitHub (May 31, 2021): Same here. Broken after silent update.
claunia commented 2026-01-31 03:59:59 +00:00
Author
Owner
Copy Link

@timanstey commented on GitHub (May 31, 2021):

Opening the App Settings for Windows Terminal Preview (Start -> Windows Terminal Preview -> on the jump list expand it and choose App Settings; or Settings -> Apps -> Windows Terminal Preview -> Advanced Options) then choosing the Repair option appears to fix this. Repair doesn't erase any settings (or didn't for me anyway).

@timanstey commented on GitHub (May 31, 2021): Opening the App Settings for Windows Terminal Preview (Start -> Windows Terminal Preview -> on the jump list expand it and choose App Settings; or Settings -> Apps -> Windows Terminal Preview -> Advanced Options) then choosing the Repair option appears to fix this. Repair doesn't erase any settings (or didn't for me anyway).
claunia commented 2026-01-31 03:59:59 +00:00
Author
Owner
Copy Link

@zarunet commented on GitHub (May 31, 2021):

Can confirm. Here's a short clip of what happens in the taskbar :

https://user-images.githubusercontent.com/43345608/120176096-2ff3d280-c207-11eb-8083-da5b68b906d0.mp4

Same crash report as @black-snow afterwards.

Unfortunately, @timanstey's suggestion did nothing for me :/

@zarunet commented on GitHub (May 31, 2021): Can confirm. Here's a short clip of what happens in the taskbar : https://user-images.githubusercontent.com/43345608/120176096-2ff3d280-c207-11eb-8083-da5b68b906d0.mp4 Same crash report as @black-snow afterwards. Unfortunately, @timanstey's suggestion did nothing for me :/
claunia commented 2026-01-31 03:59:59 +00:00
Author
Owner
Copy Link

@Rafagd commented on GitHub (May 31, 2021):

Opening the App Settings for Windows Terminal Preview (Start -> Windows Terminal Preview -> on the jump list expand it and choose App Settings; or Settings -> Apps -> Windows Terminal Preview -> Advanced Options) then choosing the Repair option appears to fix this. Repair doesn't erase any settings (or didn't for me anyway).

I tried uninstalling and reinstalling, and I just have tried both the Repair and the Reset options. No luck.

@Rafagd commented on GitHub (May 31, 2021): > > > Opening the App Settings for Windows Terminal Preview (Start -> Windows Terminal Preview -> on the jump list expand it and choose App Settings; or Settings -> Apps -> Windows Terminal Preview -> Advanced Options) then choosing the Repair option appears to fix this. Repair doesn't erase any settings (or didn't for me anyway). I tried uninstalling and reinstalling, and I just have tried both the Repair and the Reset options. No luck.
claunia commented 2026-01-31 04:00:00 +00:00
Author
Owner
Copy Link

@hagronnestad commented on GitHub (May 31, 2021):

Opening the App Settings for Windows Terminal Preview (Start -> Windows Terminal Preview -> on the jump list expand it and choose App Settings; or Settings -> Apps -> Windows Terminal Preview -> Advanced Options) then choosing the Repair option appears to fix this. Repair doesn't erase any settings (or didn't for me anyway).

This worked perfectly for me as well.

@hagronnestad commented on GitHub (May 31, 2021): > Opening the App Settings for Windows Terminal Preview (Start -> Windows Terminal Preview -> on the jump list expand it and choose App Settings; or Settings -> Apps -> Windows Terminal Preview -> Advanced Options) then choosing the Repair option appears to fix this. Repair doesn't erase any settings (or didn't for me anyway). This worked perfectly for me as well.
claunia commented 2026-01-31 04:00:00 +00:00
Author
Owner
Copy Link

@TheThing commented on GitHub (May 31, 2021):

Opening the App Settings for Windows Terminal Preview (Start -> Windows Terminal Preview -> on the jump list expand it and choose App Settings; or Settings -> Apps -> Windows Terminal Preview -> Advanced Options) then choosing the Repair option appears to fix this. Repair doesn't erase any settings (or didn't for me anyway).

I tried uninstalling and reinstalling, and I just have tried both the Repair and the Reset options. No luck.

This occured on both my machines. Uninstalling and installing fixed the problem for me though.

@TheThing commented on GitHub (May 31, 2021): > > > > Opening the App Settings for Windows Terminal Preview (Start -> Windows Terminal Preview -> on the jump list expand it and choose App Settings; or Settings -> Apps -> Windows Terminal Preview -> Advanced Options) then choosing the Repair option appears to fix this. Repair doesn't erase any settings (or didn't for me anyway). > > I tried uninstalling and reinstalling, and I just have tried both the Repair and the Reset options. No luck. This occured on both my machines. Uninstalling and installing fixed the problem for me though.
claunia commented 2026-01-31 04:00:00 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 31, 2021):

Huh. The ucrtbase.dll is definitely new. We've got a bunch of other crashes, but none coming from the CRT iirc. Best way to get to the bottom of this would be a feedback hub trace: /feedback

@zadjii-msft commented on GitHub (May 31, 2021): Huh. The `ucrtbase.dll` is definitely new. We've got a bunch of other crashes, but none coming from the CRT iirc. Best way to get to the bottom of this would be a feedback hub trace: /feedback
claunia commented 2026-01-31 04:00:01 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 31, 2021):

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 (May 31, 2021): 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)
claunia commented 2026-01-31 04:00:01 +00:00
Author
Owner
Copy Link

@Rafagd commented on GitHub (May 31, 2021):

Like this? https://aka.ms/AAcroqk

@Rafagd commented on GitHub (May 31, 2021): Like this? https://aka.ms/AAcroqk
claunia commented 2026-01-31 04:00:02 +00:00
Author
Owner
Copy Link

@black-snow commented on GitHub (May 31, 2021):

Now after lunch break it works again ... I have just installed the feedback hub and wanted to record when WT suddenly just worked again ...

/edit: anyone else having it (double-) mysteriously working again?

@black-snow commented on GitHub (May 31, 2021): Now after lunch break it works again ... I have just installed the feedback hub and wanted to record when WT suddenly just worked again ... /edit: anyone else having it (double-) mysteriously working again?
claunia commented 2026-01-31 04:00:02 +00:00
Author
Owner
Copy Link

@zarunet commented on GitHub (May 31, 2021):

Still broken for me :/ I sent a feedback from the hub ; did not get a link to share here, tho.

@zarunet commented on GitHub (May 31, 2021): Still broken for me :/ I sent a feedback from the hub ; did not get a link to share here, tho.
claunia commented 2026-01-31 04:00:02 +00:00
Author
Owner
Copy Link

@whereisaaron commented on GitHub (May 31, 2021):

Windows Update struck yesterday and since it installed Windows Terminal will no longer start. Well it appears to run for 2-5 seconds then exits again. Using 1.8.1444.0 from the Windows Store (I know, I know, foolish, but only thing close to a package manager for Windows 😄). Same ucrtbase.dll related crash others are reporting.

Faulting application name: WindowsTerminal.exe, version: 1.8.2105.24004, time stamp: 0x60ac2e94
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process ID: 0x6cd4
Faulting application start time: 0x01d75614900bd9f6
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report ID: 78473d8b-303a-4caf-b8c9-b77587623e04
Faulting package full name: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Using @timanstey's 'Repair' option (https://github.com/microsoft/terminal/issues/10294#issuecomment-851357596) has seemed to fix it though!

@whereisaaron commented on GitHub (May 31, 2021): Windows Update struck yesterday and since it installed Windows Terminal will no longer start. Well it appears to run for 2-5 seconds then exits again. Using 1.8.1444.0 from the Windows Store (I know, I know, foolish, but only thing close to a package manager for Windows 😄). Same `ucrtbase.dll` related crash others are reporting. ``` Faulting application name: WindowsTerminal.exe, version: 1.8.2105.24004, time stamp: 0x60ac2e94 Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf Exception code: 0xc0000409 Fault offset: 0x000000000007286e Faulting process ID: 0x6cd4 Faulting application start time: 0x01d75614900bd9f6 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Report ID: 78473d8b-303a-4caf-b8c9-b77587623e04 Faulting package full name: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ``` Using @timanstey's 'Repair' option (https://github.com/microsoft/terminal/issues/10294#issuecomment-851357596) has seemed to fix it though!
claunia commented 2026-01-31 04:00:03 +00:00
Author
Owner
Copy Link

@smiler commented on GitHub (May 31, 2021):

This is also being discussed in https://github.com/microsoft/terminal/issues/8358. Doing the repair dance seems as mentioned above seems fix the issue (I've had this on two systems so far).

@smiler commented on GitHub (May 31, 2021): This is also being discussed in https://github.com/microsoft/terminal/issues/8358. Doing the repair dance seems as mentioned above seems fix the issue (I've had this on two systems so far).
claunia commented 2026-01-31 04:00:03 +00:00
Author
Owner
Copy Link

@Eric2203 commented on GitHub (May 31, 2021):

Hi, I'm having the exact same error. Repairing does NOT help in my case. Uninstall/reinstall does not either. It was working a few days ago. I've not rebooted since then.

From the Event viewer:

Faulting application name: WindowsTerminal.exe, version: 1.8.2105.24004, time stamp: 0x60ac2e94 Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf Exception code: 0xc0000409 Fault offset: 0x000000000007286e Faulting process id: 0x6e2c Faulting application start time: 0x01d7566cb1e7e12d Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Report Id: b996e0eb-a6bc-40dd-a27e-f4e9a8463d49 Faulting package full name: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App

And:

`Fault bucket 1320776192965560009, type 5
Event Name: MoBEX
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.8.2105.24004
P4: 60ac2e94
P5: ucrtbase.dll
P6: 10.0.19041.789
P7: 2bd748bf
P8: 000000000007286e
P9: c0000409
P10: 0000000000000007

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE811.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREAF0.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREB30.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREB3D.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREB9C.tmp.txt

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Window_bb1488c3939d65a4e3fed65bb628a3e554bf88_19389ec9_075e3dda-3c75-4edf-9061-4048fca64605

Analysis symbol:
Rechecking for solution: 0
Report Id: b996e0eb-a6bc-40dd-a27e-f4e9a8463d49
Report Status: 268435456
Hashed bucket: 4ba5cd02f28599e4625456f3218146c9
Cab Guid: 0`

@Eric2203 commented on GitHub (May 31, 2021): Hi, I'm having the exact same error. Repairing does NOT help in my case. Uninstall/reinstall does not either. It was working a few days ago. I've not rebooted since then. From the Event viewer: `Faulting application name: WindowsTerminal.exe, version: 1.8.2105.24004, time stamp: 0x60ac2e94 Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf Exception code: 0xc0000409 Fault offset: 0x000000000007286e Faulting process id: 0x6e2c Faulting application start time: 0x01d7566cb1e7e12d Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Report Id: b996e0eb-a6bc-40dd-a27e-f4e9a8463d49 Faulting package full name: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App` And: `Fault bucket 1320776192965560009, type 5 Event Name: MoBEX Response: Not available Cab Id: 0 Problem signature: P1: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe P2: praid:App P3: 1.8.2105.24004 P4: 60ac2e94 P5: ucrtbase.dll P6: 10.0.19041.789 P7: 2bd748bf P8: 000000000007286e P9: c0000409 P10: 0000000000000007 Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE811.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREAF0.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREB30.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREB3D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREB9C.tmp.txt These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Window_bb1488c3939d65a4e3fed65bb628a3e554bf88_19389ec9_075e3dda-3c75-4edf-9061-4048fca64605 Analysis symbol: Rechecking for solution: 0 Report Id: b996e0eb-a6bc-40dd-a27e-f4e9a8463d49 Report Status: 268435456 Hashed bucket: 4ba5cd02f28599e4625456f3218146c9 Cab Guid: 0`
claunia commented 2026-01-31 04:00:04 +00:00
Author
Owner
Copy Link

@matthewstuartedwards commented on GitHub (Jun 1, 2021):

Also having the issue starting up, and repair did not work for me.

@matthewstuartedwards commented on GitHub (Jun 1, 2021): Also having the issue starting up, and repair did not work for me.
claunia commented 2026-01-31 04:00:04 +00:00
Author
Owner
Copy Link

@bsmely-w commented on GitHub (Jun 1, 2021):

+1

@bsmely-w commented on GitHub (Jun 1, 2021): +1
claunia commented 2026-01-31 04:00:04 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 1, 2021):

Nevermind, I'm crazy. The ucrtbase.dll crash is /dup #10211

@zadjii-msft commented on GitHub (Jun 1, 2021): Nevermind, I'm crazy. The `ucrtbase.dll` crash is /dup #10211
claunia commented 2026-01-31 04:00:05 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 1, 2021):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Jun 1, 2021): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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 Resolution-Duplicate
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#14067
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?