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

Windows Terminal hangs with DesktopWindowXamlSource #9541

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

Originally created by @maksimushka32 on GitHub (Jul 10, 2020).

Windows Terminal doesn't start after reboot. It was working on current machine, but suddenly stop working and now it run only a zero size window with "DesktopWindowXamlSource" caption, that hangs immediately after start. I can close it only from task manager.
image (2)

It was working fine but after another windows update it just doesn't start. I've rebooted my PC several times, deleted profile.json, try to install Preview terminal version - nothing of this doesn't helps to me.

I'm located in secure local network and don't have administrator rights on my PC.

Link on feddback hub: https://aka.ms/AA8xqz6

Environment

Windows 10 2004
Microsoft Windows NT 10.0.19041.0
Windows Terminal version 1.0.1211.0

Steps to reproduce

Run Windows Terminal from desktop icon.

Expected behavior

It start and work

Actual behavior

It start and nothing happen. Just empty window with caption "DesktopWindowXamlSource", that i can't close.

Originally created by @maksimushka32 on GitHub (Jul 10, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> Windows Terminal doesn't start after reboot. It was working on current machine, but suddenly stop working and now it run only a zero size window with "DesktopWindowXamlSource" caption, that hangs immediately after start. I can close it only from task manager. ![image (2)](https://user-images.githubusercontent.com/54031964/87126584-1ebf7180-c295-11ea-9c50-b0ae6b01b0cb.png) It was working fine but after another windows update it just doesn't start. I've rebooted my PC several times, deleted profile.json, try to install Preview terminal version - nothing of this doesn't helps to me. I'm located in secure local network and don't have administrator rights on my PC. Link on feddback hub: https://aka.ms/AA8xqz6 # Environment ``` Windows 10 2004 Microsoft Windows NT 10.0.19041.0 Windows Terminal version 1.0.1211.0 ``` # Steps to reproduce Run Windows Terminal from desktop icon. <!-- A description of how to trigger this bug. --> # Expected behavior It start and work <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior It start and nothing happen. Just empty window with caption "DesktopWindowXamlSource", that i can't close. <!-- What's actually happening? -->
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Author-Feedback labels 2026-01-31 01:57:05 +00:00
claunia commented 2026-01-31 01:57:06 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 14, 2020):

Hey, I'm so sorry we took a long time to get to this bug. Does it still happen with 1.1 or 1.2?

@DHowett commented on GitHub (Aug 14, 2020): Hey, I'm so sorry we took a long time to get to this bug. Does it still happen with 1.1 or 1.2?
claunia commented 2026-01-31 01:57:06 +00:00
Author
Owner
Copy Link

@maksimushka32 commented on GitHub (Aug 14, 2020):

Hi!
I've check just now and can tell you that issue still persist. On both 1.1 and 1.2
image

@maksimushka32 commented on GitHub (Aug 14, 2020): Hi! I've check just now and can tell you that issue still persist. On both 1.1 and 1.2 ![image](https://user-images.githubusercontent.com/54031964/90221088-2c2ac700-de12-11ea-9ac2-415c72f05af8.png)
claunia commented 2026-01-31 01:57:06 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 19, 2020):

Okay this is a long shot, but I'm not really sure where to go with this one currently.

  • Could you try adding "showTabsInTitlebar": false, to your settings.json, and see if the Terminal will boot then? This file will be in %localappdata%\Packages\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe\LocalState\settings.json
  • Can you open the PowerToys Settings app? You can find that by right-clicking on the powertoys icon in the taskbar after installing PowerToys.
    image
    • This one's a real spitball. I know that the PT Settings app is another XAML Islands app, so I'm hoping we can check if the issue is local to the Terminal or not.
@zadjii-msft commented on GitHub (Aug 19, 2020): Okay this is a long shot, but I'm not really sure where to go with this one currently. * Could you try adding `"showTabsInTitlebar": false,` to your `settings.json`, and see if the Terminal will boot then? This file will be in `%localappdata%\Packages\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe\LocalState\settings.json` * Can you open the [PowerToys ](https://github.com/microsoft/PowerToys)Settings app? You can find that by right-clicking on the powertoys icon in the taskbar after installing PowerToys. ![image](https://user-images.githubusercontent.com/18356694/90685836-fc275d80-e22f-11ea-8dc5-508e7e075cd3.png) - This one's a real spitball. I know that the PT Settings app is another XAML Islands app, so I'm hoping we can check if the issue is local to the Terminal or not.
claunia commented 2026-01-31 01:57:07 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 23, 2020):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Aug 23, 2020): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 01:57:07 +00:00
Author
Owner
Copy Link

@maksimushka32 commented on GitHub (Aug 24, 2020):

Hi!
Sorry for the delay
showTabsInTitlebar setting has no affect on behavior of the terminal. It still hangs.
As for PowerToys unfortunately i can't install it to this PC. I can install apps only from msixbundle file

@maksimushka32 commented on GitHub (Aug 24, 2020): Hi! Sorry for the delay showTabsInTitlebar setting has no affect on behavior of the terminal. It still hangs. As for PowerToys unfortunately i can't install it to this PC. I can install apps only from msixbundle file
claunia commented 2026-01-31 01:57:07 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 4, 2020):

If you run wsl.exe (outside of terminal!) does it ever work, or does it hang forever? How about wsl.exe -l?

@DHowett commented on GitHub (Sep 4, 2020): If you run `wsl.exe` (outside of terminal!) does it ever work, or does it hang forever? How about `wsl.exe -l`?
claunia commented 2026-01-31 01:57:07 +00:00
Author
Owner
Copy Link

@maksimushka32 commented on GitHub (Sep 4, 2020):

Yes. Problem with Windows Terminal only. Wsl runs nice as from it's own app and from powershell.
I've try to run Terminal even without settings.json and have same result.

@maksimushka32 commented on GitHub (Sep 4, 2020): Yes. Problem with Windows Terminal only. Wsl runs nice as from it's own app and from powershell. I've try to run Terminal even without settings.json and have same result.
claunia commented 2026-01-31 01:57:07 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 4, 2020):

Can you use Task Manager to “Create a dump file” for WindowsTerminal.exe? You can do it by right-clicking WindowsTerminal on the Details tab.

Then, upload the “.dmp” file to OneDrive or Google Drive and e-mail me a link. My address is on my GitHub profile.

Thanks!

@DHowett commented on GitHub (Sep 4, 2020): Can you use Task Manager to “Create a dump file” for WindowsTerminal.exe? You can do it by right-clicking WindowsTerminal on the Details tab. Then, upload the “.dmp” file to OneDrive or Google Drive and e-mail me a link. My address is on my GitHub profile. Thanks!
claunia commented 2026-01-31 01:57:07 +00:00
Author
Owner
Copy Link

@maksimushka32 commented on GitHub (Sep 4, 2020):

Please, check your e-mail for link

@maksimushka32 commented on GitHub (Sep 4, 2020): Please, check your e-mail for link
claunia commented 2026-01-31 01:57:08 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 4, 2020):

Interesting... it looks like we have a bunch of threads blocked in the Mcafee security driver. Are you getting any AV/security alerts from that software?

@DHowett commented on GitHub (Sep 4, 2020): Interesting... it looks like we have a bunch of threads blocked in the _Mcafee security driver_. Are you getting any AV/security alerts from that software?
claunia commented 2026-01-31 01:57:08 +00:00
Author
Owner
Copy Link

@maksimushka32 commented on GitHub (Sep 4, 2020):

I don't receive any, but maybe security officers does. I will check this at monday.

@maksimushka32 commented on GitHub (Sep 4, 2020): I don't receive any, but maybe security officers does. I will check this at monday.
claunia commented 2026-01-31 01:57:08 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 14, 2020):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Sep 14, 2020): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 01:57:08 +00:00
Author
Owner
Copy Link

@owainkenwayucl commented on GitHub (May 26, 2021):

I just had this for the first time ever and I don't have McAfee it took maybe five minutes and then it closed and resolved itself.

@owainkenwayucl commented on GitHub (May 26, 2021): I just had this for the first time ever and I don't have McAfee it took maybe five minutes and then it closed and resolved itself.
claunia commented 2026-01-31 01:57:08 +00:00
Author
Owner
Copy Link

@owainkenwayucl commented on GitHub (May 26, 2021):

Oh, more detail I guess.

I just updated to 21H1 - Windows 10.0.19043.1023
Windows Terminal 1.7.1033.0.

I was closing the WIndow after spending a couple of hours logged in via SSH to one of our HPC systems.

If it happens again I'll try creating a dump as described above.

@owainkenwayucl commented on GitHub (May 26, 2021): Oh, more detail I guess. I just updated to 21H1 - Windows 10.0.19043.1023 Windows Terminal 1.7.1033.0. I was closing the WIndow after spending a couple of hours logged in via SSH to one of our HPC systems. If it happens again I'll try creating a dump as described above.
claunia commented 2026-01-31 01:57:09 +00:00
Author
Owner
Copy Link

@owainkenwayucl commented on GitHub (May 26, 2021):

Oh, actually there's an error in event log:

Exception code 0xc0000602

In module KERNELBASE.dll.

@owainkenwayucl commented on GitHub (May 26, 2021): Oh, actually there's an error in event log: Exception code 0xc0000602 In module KERNELBASE.dll.
claunia commented 2026-01-31 01:57:09 +00:00
Author
Owner
Copy Link

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

Unfortunately, that doesn't give us enough to work with by itself. However, if it's happening consistently, the Feedback Hub might be able to get us some useful info:

/feedback

@zadjii-msft commented on GitHub (May 27, 2021): Unfortunately, that doesn't give us enough to work with by itself. However, if it's happening consistently, the Feedback Hub might be able to get us some useful info: /feedback
claunia commented 2026-01-31 01:57:09 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 27, 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 27, 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 01:57:09 +00:00
Author
Owner
Copy Link

@muRn commented on GitHub (May 28, 2021):

I'm having the same problem as well. Just prior to rebooting Windows Terminal worked fine, but after it just doesn't start. Something titled "DesktopWindowXamlSource" appears for couple seconds (without visible window) and closes itself automatically without any warnings/errors:
windows_terminal_issue

I've tried setting "showTabsInTitlebar": false in the settings.json - didn't help. I've tried running wsl.exe from cmd.exe - works fine. Default profile on Windows Terminal was PowerShell 7 and separately it works fine as well.

Are there any logs written somewhere when Windows Terminal starts? I don't think it's possible to make a memory dump - it's closing itself too fast.

@muRn commented on GitHub (May 28, 2021): I'm having the same problem as well. Just prior to rebooting Windows Terminal worked fine, but after it just doesn't start. Something titled "DesktopWindowXamlSource" appears for couple seconds (without visible window) and closes itself automatically without any warnings/errors: ![windows_terminal_issue](https://user-images.githubusercontent.com/2263591/119957133-19007680-bfa2-11eb-994d-256389689c97.gif) I've tried setting `"showTabsInTitlebar": false` in the `settings.json` - didn't help. I've tried running wsl.exe from cmd.exe - works fine. Default profile on Windows Terminal was PowerShell 7 and separately it works fine as well. Are there any logs written somewhere when Windows Terminal starts? I don't think it's possible to make a memory dump - it's closing itself too fast.
claunia commented 2026-01-31 01:57:10 +00:00
Author
Owner
Copy Link

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

I'm having the same problem right now, this has never happened before on my end. Are there any possibilities to reset some caches or something similar? I don't want to need to use the old conhost again. :D

PS: Using Win 2004.

@LinqLover commented on GitHub (Jun 1, 2021): I'm having the same problem right now, this has never happened before on my end. Are there any possibilities to reset some caches or something similar? I don't want to need to use the old conhost again. :D PS: Using Win 2004.
claunia commented 2026-01-31 01:57:10 +00:00
Author
Owner
Copy Link

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

A reboot (coincidentally during an update to Windows 21H1) fixed this for me.

@brechtm commented on GitHub (Jun 1, 2021): A reboot (coincidentally during an update to Windows 21H1) fixed this for me.
claunia commented 2026-01-31 01:57:10 +00:00
Author
Owner
Copy Link

@soharang commented on GitHub (Aug 30, 2021):

In my case, uninstalling Ubuntu that I installed from Microsoft Store solved problem. After uninstalling Ubuntu, windows terminal started to launch properly. Both Ubuntu 18.04 LTS and 20.04 LTS causes this problem.
But it does not mean a lot to me if I cannot keep both "Windows terminal" and "Ubuntu WSL".

@soharang commented on GitHub (Aug 30, 2021): In my case, uninstalling Ubuntu that I installed from Microsoft Store solved problem. After uninstalling Ubuntu, windows terminal started to launch properly. Both Ubuntu 18.04 LTS and 20.04 LTS causes this problem. But it does not mean a lot to me if I cannot keep both "Windows terminal" and "Ubuntu WSL".
claunia commented 2026-01-31 01:57:10 +00:00
Author
Owner
Copy Link

@chenfw2017 commented on GitHub (Jul 1, 2022):

I'm having the same problem right now. My Environment:
OS: win10 21H2 19044.1806
Terminal ver: 1.13.11431.0
:(

@chenfw2017 commented on GitHub (Jul 1, 2022): I'm having the same problem right now. My Environment: OS: win10 21H2 19044.1806 Terminal ver: 1.13.11431.0 :(
claunia commented 2026-01-31 01:57:10 +00:00
Author
Owner
Copy Link

@Agamenox commented on GitHub (Dec 31, 2022):

I got this problem when use terminal in administrator mode...

@Agamenox commented on GitHub (Dec 31, 2022): I got this problem when use terminal in administrator mode...
claunia commented 2026-01-31 01:57:11 +00:00
Author
Owner
Copy Link

@mannfuri commented on GitHub (May 23, 2023):

clear then JSON file, FIX this.
in my case is

C:\Users\user\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json
@mannfuri commented on GitHub (May 23, 2023): clear then JSON file, FIX this. in my case is ``` C:\Users\user\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json ```
claunia commented 2026-01-31 01:57:11 +00:00
Author
Owner
Copy Link

@dariusaurius commented on GitHub (Jan 31, 2024):

clear then JSON file, FIX this. in my case is

C:\Users\user\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json

Removing the folder Microsoft.WindowsTerminal_8wekyb3d8bbwe fixed it for me

@dariusaurius commented on GitHub (Jan 31, 2024): > clear then JSON file, FIX this. in my case is > > ``` > C:\Users\user\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json > ``` Removing the folder `Microsoft.WindowsTerminal_8wekyb3d8bbwe` fixed it for me
claunia commented 2026-01-31 01:57:11 +00:00
Author
Owner
Copy Link

@Gladrat commented on GitHub (May 4, 2025):

I've had this issue on Terminal for a couple of months, and nothing has worked to solve it.
Today I updated my PowerToys app and the DesktopWindowXamlSource window instantly disappeared...

No other manipulation done today.
I somewhat suspect FancyZones, but I don’t have any evidence to support it.

@Gladrat commented on GitHub (May 4, 2025): I've had this issue on Terminal for a couple of months, and nothing has worked to solve it. Today I updated my PowerToys app and the DesktopWindowXamlSource window instantly disappeared... No other manipulation done today. I somewhat suspect FancyZones, but I don’t have any evidence to support it.
claunia commented 2026-01-31 01:57:11 +00:00
Author
Owner
Copy Link

@nickgpltech commented on GitHub (May 20, 2025):

it's one of these settings.
I updated powertoys and same issue persistent.
disabled this, and the ghost window went away.

This seems like more of a powertoys\fancyzones issue than a terminal issue.

Image

@nickgpltech commented on GitHub (May 20, 2025): it's one of these settings. I updated powertoys and same issue persistent. disabled this, and the ghost window went away. This seems like more of a powertoys\fancyzones issue than a terminal issue. ![Image](https://github.com/user-attachments/assets/eb6d745e-d41f-465c-9bcc-72b622b2fc1c)
claunia commented 2026-01-31 01:57:12 +00:00
Author
Owner
Copy Link

@majkinetor commented on GitHub (Sep 2, 2025):

Yeah, i have this hangin on all the time above WT, and as @nickgpltech told, closing powertoys fixes it.

@majkinetor commented on GitHub (Sep 2, 2025): Yeah, i have this hangin on all the time above WT, and as @nickgpltech told, closing powertoys fixes it.
claunia commented 2026-01-31 01:57:12 +00:00
Author
Owner
Copy Link

@Hassan4Dev commented on GitHub (Sep 30, 2025):

Yep, had the same. Specifically, it's the FancyZones tool, and more specifically, it's the "Move newly created windows to their last known zone". Toggling that on / off reliably reproduces this issue.

Edit, you can fix this by adding: DesktopWindowXamlSource under Excluded apps in the FancyZones settings, as such:

Image
@Hassan4Dev commented on GitHub (Sep 30, 2025): Yep, had the same. Specifically, it's the FancyZones tool, and more specifically, it's the "Move newly created windows to their last known zone". Toggling that on / off reliably reproduces this issue. Edit, you can fix this by adding: DesktopWindowXamlSource under Excluded apps in the FancyZones settings, as such: <img width="1073" height="181" alt="Image" src="https://github.com/user-attachments/assets/e772ae1d-4332-4d03-b495-7e9d7d124f1a" />
claunia commented 2026-01-31 01:57:12 +00:00
Author
Owner
Copy Link

@Ad-closeNN commented on GitHub (Nov 8, 2025):

Hello guys. Today I met this problem.
TL;DR: Disable Compatibility > Allow Windows Terminal to run in the background if you have enable it
I tried to disable FancyZones and uninstall Powertoys but it did't work.
Luckily I found the button then I disabled it. Finally there was no that ghost DesktopWindowXamlSource
I don't know if this solution will work for everyone. But if you enable this function I think you should try this. Thank you for watching.

img
Original link of pic: https://geekrewind.com/wp-content/uploads/2025/02/Allow-Window-Terminal-to-run-in-the-background.webp

Original screenshot in Simplified Chinese

Image

The About Page of Windows Terminal.
Version 1.23.12811.0
Image

@Ad-closeNN commented on GitHub (Nov 8, 2025): Hello guys. Today I met this problem. **TL;DR: Disable `Compatibility > Allow Windows Terminal to run in the background` if you have enable it** I tried to disable `FancyZones` and uninstall Powertoys but it did't work. Luckily I found the button then I disabled it. Finally there was no that ghost **DesktopWindowXamlSource** I don't know if this solution will work for everyone. But if you enable this function I think you should try this. Thank you for watching. ![img](https://geekrewind.com/wp-content/uploads/2025/02/Allow-Window-Terminal-to-run-in-the-background.webp) Original link of pic: [https://geekrewind.com/wp-content/uploads/2025/02/Allow-Window-Terminal-to-run-in-the-background.webp](https://geekrewind.com/wp-content/uploads/2025/02/Allow-Window-Terminal-to-run-in-the-background.webp) <details><summary>Original screenshot in Simplified Chinese</summary> <p> <img width="1113" height="626" alt="Image" src="https://github.com/user-attachments/assets/88ee3998-24d7-48ac-9f6f-08b74f930949" /> </p> </details> The About Page of Windows Terminal. Version 1.23.12811.0 <img width="224" height="108" alt="Image" src="https://github.com/user-attachments/assets/73c547c0-8741-4167-96e8-a1d2a9acc4fc" />
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 Needs-Author-Feedback Needs-Tag-Fix Needs-Triage
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#9541
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?