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

Terminal can't create pseudoconsoles when condrv isn't loaded [Error 0xd000003a] #6658

New Issue
Open
opened 2026-01-31 00:44:04 +00:00 by claunia · 33 comments
claunia commented 2026-01-31 00:44:04 +00:00
Owner
Copy Link

Originally created by @dkav on GitHub (Feb 29, 2020).

Environment

Windows build number:  0.9.433.0

Windows Terminal version (if applicable):  0.9.433.0

Running within VirtualBox VM.

Steps to reproduce

Start Windows Terminal after reboot.

Expected behavior

Powershell starts.

Actual behavior

Powershell does not start. Following messaged displayed - Error 0xd000003a when launching 'powershell.exe'. Starting Powershell directly, which opens without a problem, and then opening Powershell in Windows Terminal fixes the problem.

The following is my PATH:

C:\Windows\system32
C:\Windows
C:\Windows\System32\Wbem
C:\Windows\System32\WindowsPowerShell\v1.0\
C:\Windows\System32\OpenSSH\
C:\Users\Darren\AppData\Local\Microsoft\WindowsApps
C:\Python27\ArcGIS10.8
C:\Program Files\ArcGIS\Pro\bin\Python\Scripts

Similar issue with Command and similar resolution.

Originally created by @dkav on GitHub (Feb 29, 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. --> # Environment ```none Windows build number: 0.9.433.0 Windows Terminal version (if applicable): 0.9.433.0 Running within VirtualBox VM. ``` # Steps to reproduce Start Windows Terminal after reboot. # Expected behavior Powershell starts. # Actual behavior Powershell does not start. Following messaged displayed - _Error 0xd000003a when launching 'powershell.exe'_. Starting Powershell directly, which opens without a problem, and then opening Powershell in Windows Terminal fixes the problem. The following is my PATH: ``` C:\Windows\system32 C:\Windows C:\Windows\System32\Wbem C:\Windows\System32\WindowsPowerShell\v1.0\ C:\Windows\System32\OpenSSH\ C:\Users\Darren\AppData\Local\Microsoft\WindowsApps C:\Python27\ArcGIS10.8 C:\Program Files\ArcGIS\Pro\bin\Python\Scripts ``` Similar issue with Command and similar resolution.
claunia commented 2026-01-31 00:44:05 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 2, 2020):

If you launch cmd, does powershell start working? I have a theory, but this will help me narrow it down.

@DHowett-MSFT commented on GitHub (Mar 2, 2020): If you launch cmd, does powershell start working? I have a theory, but this will help me narrow it down.
claunia commented 2026-01-31 00:44:05 +00:00
Author
Owner
Copy Link

@dkav commented on GitHub (Mar 2, 2020):

Yes, launching the stand alone Command Prompt enables Powershell to start within Windows Terminal.

@dkav commented on GitHub (Mar 2, 2020): Yes, launching the stand alone Command Prompt enables Powershell to start within Windows Terminal.
claunia commented 2026-01-31 00:44:05 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 2, 2020):

Okay, I bet condrv (our kernel driver) isn't being loaded. This is extremely rare, and only happens when no other console applications have been spawned on startup.

@DHowett-MSFT commented on GitHub (Mar 2, 2020): Okay, I bet condrv (our kernel driver) isn't being loaded. This is extremely rare, and only happens when no other console applications have been spawned on startup.
claunia commented 2026-01-31 00:44:05 +00:00
Author
Owner
Copy Link

@dkav commented on GitHub (Mar 2, 2020):

I have tried to keep the VM as spare as possible so I guess that would fit in with your hypothesis.

@dkav commented on GitHub (Mar 2, 2020): I have tried to keep the VM as spare as possible so I guess that would fit in with your hypothesis.
claunia commented 2026-01-31 00:44:06 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 6, 2020):

I've got an idea how to fix this, but the workaround is simple (launch a commandline app, or be on a non-stripped-out Windows); triaging into 1.x (not backlog), p2

@DHowett-MSFT commented on GitHub (Mar 6, 2020): I've got an idea how to fix this, but the workaround is simple (launch a commandline app, or be on a non-stripped-out Windows); triaging into 1.x (not backlog), p2
claunia commented 2026-01-31 00:44:06 +00:00
Author
Owner
Copy Link

@DIzFer commented on GitHub (Mar 14, 2020):

I can also observe this exact behaviour on my system, which both has as little software installed as possible and on a virtual machine.

@DIzFer commented on GitHub (Mar 14, 2020): I can also observe this exact behaviour on my system, which both has as little software installed as possible and on a virtual machine.
claunia commented 2026-01-31 00:44:06 +00:00
Author
Owner
Copy Link

@revnode commented on GitHub (Mar 21, 2020):

Seeing this on my laptop that's running Windows 10 ARM.

@revnode commented on GitHub (Mar 21, 2020): Seeing this on my laptop that's running Windows 10 ARM.
claunia commented 2026-01-31 00:44:07 +00:00
Author
Owner
Copy Link

@cbrnr commented on GitHub (Jun 8, 2020):

Same on my machine (not a VM, standard installation) - this happens very often and I can't start any of my profiles (Bash, Powershell, CMD).

@cbrnr commented on GitHub (Jun 8, 2020): Same on my machine (*not* a VM, standard installation) - this happens very often and I can't start any of my profiles (Bash, Powershell, CMD).
claunia commented 2026-01-31 00:44:07 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 19, 2020):

I am having an almost identical issue on my main machine. I am using Windows 10 2004 x64. When I launch Windows Terminal after a reboot I am faced with this. However if I then launch CMD and reopen Windows Terminal the issue is fixed. I have CMD set as my default profile just FYI.

@ghost commented on GitHub (Jun 19, 2020): I am having an almost identical issue on my main machine. I am using Windows 10 2004 x64. When I launch Windows Terminal after a reboot I am faced with [this](https://i.imgur.com/wAprUEW.png). However if I then launch CMD and reopen Windows Terminal the issue is fixed. I have CMD set as my default profile just FYI.
claunia commented 2026-01-31 00:44:07 +00:00
Author
Owner
Copy Link

@rfalanga commented on GitHub (Sep 5, 2020):

@DHowett-MSFT the work around you gave on March 5th does work, but it is disconcerting. I had previously uninstalled FileZilla, which then required (so it said) me to reboot. As soon as my machine came back on the first thing I did was get into Windows Terminal, which launches a PowerShell 7.0.3 instance. Or tried, as I got that error. I thought that somehow uninstalling FileZilla had corrupted my machine. Until I came across this post. So, I thought brought up PowerShell, not Windows Terminal. That allowed me to bring up Windows Terminal.

Is this issue being worked on?

@rfalanga commented on GitHub (Sep 5, 2020): @DHowett-MSFT the work around you gave on March 5th does work, but it is disconcerting. I had previously uninstalled FileZilla, which then required (so it said) me to reboot. As soon as my machine came back on the first thing I did was get into Windows Terminal, which launches a PowerShell 7.0.3 instance. Or tried, as I got that error. I thought that somehow uninstalling FileZilla had corrupted my machine. Until I came across this post. So, I thought brought up PowerShell, not Windows Terminal. That allowed me to bring up Windows Terminal. Is this issue being worked on?
claunia commented 2026-01-31 00:44:07 +00:00
Author
Owner
Copy Link

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

"Sort of." The official mechanism by which we would load our driver is effectively a private API. I'm working on making sure we can actually ship that ;P

@DHowett commented on GitHub (Sep 5, 2020): "Sort of." The official mechanism by which we would load our driver is _effectively a private API_. I'm working on making sure we can actually ship that ;P
claunia commented 2026-01-31 00:44:08 +00:00
Author
Owner
Copy Link

@AnthonyK213 commented on GitHub (Sep 13, 2020):

Same (not a VM). The error would be reproduced every time I restart the pc, which is really annoying. The windows is fresh installed (ver 1909), and the windows terminal is also newly installed (ver 1.2.2381.0).

@AnthonyK213 commented on GitHub (Sep 13, 2020): Same (not a VM). The error would be reproduced every time I restart the pc, which is really annoying. The windows is fresh installed (ver 1909), and the windows terminal is also newly installed (ver 1.2.2381.0).
claunia commented 2026-01-31 00:44:08 +00:00
Author
Owner
Copy Link

@rowheel commented on GitHub (Oct 2, 2020):

Same. It's a Win10/KVM installation. Problem reproduces each time I boot up the guest OS. The workaround is to fire up a PowerShell console, and then close that. WT shall get functioning.

@rowheel commented on GitHub (Oct 2, 2020): Same. It's a Win10/KVM installation. Problem reproduces each time I boot up the guest OS. The workaround is to fire up a PowerShell console, and then close that. WT shall get functioning.
claunia commented 2026-01-31 00:44:08 +00:00
Author
Owner
Copy Link

@Kein commented on GitHub (Dec 31, 2020):

Same issue.
NOT A VM INSTALLATION

@Kein commented on GitHub (Dec 31, 2020): Same issue. **_NOT A VM INSTALLATION_**
claunia commented 2026-01-31 00:44:08 +00:00
Author
Owner
Copy Link

@justinkb commented on GitHub (Feb 10, 2021):

seeing this in a non-vm setting as well. windows 10 pro

@justinkb commented on GitHub (Feb 10, 2021): seeing this in a non-vm setting as well. windows 10 pro
claunia commented 2026-01-31 00:44:08 +00:00
Author
Owner
Copy Link

@submodify commented on GitHub (Feb 15, 2021):

Same issue here...
Windows 10 Pro Version 10.0.19042 Build 19042
Fresh install
not a VM

@submodify commented on GitHub (Feb 15, 2021): Same issue here... Windows 10 Pro Version 10.0.19042 Build 19042 Fresh install not a VM
claunia commented 2026-01-31 00:44:09 +00:00
Author
Owner
Copy Link

@LukasDoesDev commented on GitHub (Feb 26, 2021):

Same issue here, using a KVM

Windows 10 Pro Version 20H2 Build 19042.804

@LukasDoesDev commented on GitHub (Feb 26, 2021): Same issue here, using a KVM Windows 10 Pro Version 20H2 Build 19042.804
claunia commented 2026-01-31 00:44:09 +00:00
Author
Owner
Copy Link

@nullinger commented on GitHub (Mar 2, 2021):

Same issue. No VM. Windows 10 Pro Version 20H2.

Apart from that: Great software 👍 Thank you

@nullinger commented on GitHub (Mar 2, 2021): Same issue. No VM. Windows 10 Pro Version 20H2. Apart from that: Great software 👍 Thank you
claunia commented 2026-01-31 00:44:09 +00:00
Author
Owner
Copy Link

@jordankkk commented on GitHub (Apr 4, 2021):

same 20H2 without vm

@jordankkk commented on GitHub (Apr 4, 2021): same 20H2 without vm
claunia commented 2026-01-31 00:44:09 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Apr 5, 2021):

Does the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\condrv\Start affect this? What if it were changed from 3 (manual) to 2 (autoload)?

@vefatica commented on GitHub (Apr 5, 2021): Does the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\condrv\Start affect this? What if it were changed from 3 (manual) to 2 (autoload)?
claunia commented 2026-01-31 00:44:09 +00:00
Author
Owner
Copy Link

@jordankkk commented on GitHub (Apr 6, 2021):

so far reinstall the problem is not appearing again

@jordankkk commented on GitHub (Apr 6, 2021): so far reinstall the problem is not appearing again
claunia commented 2026-01-31 00:44:10 +00:00
Author
Owner
Copy Link

@panorb commented on GitHub (Apr 23, 2021):

Does the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\condrv\Start affect this? What if it were changed from 3 (manual) to 2 (autoload)?

This change fixed the issue for me.

@panorb commented on GitHub (Apr 23, 2021): > Does the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\condrv\Start affect this? What if it were changed from 3 (manual) to 2 (autoload)? This change fixed the issue for me.
claunia commented 2026-01-31 00:44:10 +00:00
Author
Owner
Copy Link

@htcfreek commented on GitHub (May 24, 2021):

I had this issue too before a couple of minutes. Affected profiles: git bash, cmd, powershell
The solution for me was running cmd directly via start menu. The wt works again.

@htcfreek commented on GitHub (May 24, 2021): I had this issue too before a couple of minutes. Affected profiles: git bash, cmd, powershell The solution for me was running cmd directly via start menu. The wt works again.
claunia commented 2026-01-31 00:44:10 +00:00
Author
Owner
Copy Link

@the-j0k3r commented on GitHub (May 26, 2021):

Today out of the blue after it has been working perfectly for a long time.

[error 0xd000003a when launching powershell.exe -NoLogo']`

Windows 10 pro 1909 18363.1556

Windows Terminal version (if applicable):  1.7.1033.0

NOT A VM

I believe this happened because it was the first app opened after Windows finished loading, workaround was to start cmd before hand,

@the-j0k3r commented on GitHub (May 26, 2021): Today out of the blue after it has been working perfectly for a long time. `[error 0xd000003a when launching `powershell.exe -NoLogo']` ``` Windows 10 pro 1909 18363.1556 Windows Terminal version (if applicable): 1.7.1033.0 ``` # NOT A VM I believe this happened because it was the first app opened after Windows finished loading, workaround was to start cmd before hand,
claunia commented 2026-01-31 00:44:10 +00:00
Author
Owner
Copy Link

@the-j0k3r commented on GitHub (Jun 3, 2021):

After my initial report as above, there are new changes.

Terminal was updated to Version: 1.8.1444.0 a day or so later from said report, and for a while the issue was gone.

Windows upgraded from 1909 - build 18363.1556 to 2004 19041.985 last terminal was launching just fine for a while after this.

Today I opened WT and low and behold here comes the issue back into focus rearing its head.

The only changes to system were that I cleanup via the new settings menu all old installations and temp files.

If I open Windows store checking for new version of apps, afterwards the issue is gone. Though there are no new WT updates.

With no official developers feedback into with what specific information developers would benefit from in all bugs reports reports, its hard to know what further information would benefit said developers in fixing the issue, since having to perform some workaround in order to have a successful error free WT launch and operation is already a strain on day to day usage.

TLDR

Can someone official to project please add some entry to both readme/issue templates that details how to gather logs or other desired information that would help developers pin the issues reported down. With exception of telemetry which users may have disabled or cannot submit manually when creating issues.

/end

and again

NOT A VM

regards.

@the-j0k3r commented on GitHub (Jun 3, 2021): After my initial report as above, there are new changes. Terminal was updated to `Version: 1.8.1444.0` a day or so later from said report, and for a while the issue was gone. Windows upgraded from `1909 - build 18363.1556` to `2004 19041.985` last terminal was launching just fine for a while after this. Today I opened WT and low and behold here comes the issue back into focus rearing its head. The only changes to system were that I cleanup via the new settings menu all old installations and temp files. If I open Windows store checking for new version of apps, afterwards the issue is gone. Though there are no new WT updates. With no official developers feedback into with what specific information developers would benefit from in all bugs reports reports, its hard to know what further information would benefit said developers in fixing the issue, since having to perform some workaround in order to have a successful error free WT launch and operation is already a strain on day to day usage. TLDR Can someone official to project please add some entry to both readme/issue templates that details how to gather logs or other desired information that would help developers pin the issues reported down. With exception of telemetry which users may have disabled or cannot submit manually when creating issues. /end and again # NOT A VM regards.
claunia commented 2026-01-31 00:44:10 +00:00
Author
Owner
Copy Link

@TheBinitGhimire commented on GitHub (Jun 26, 2021):

Hi there,

I just installed the 21H1 version of Windows 10, and I was facing this issue in Windows Terminal latest release v1.8.1444.0 after restarting my computer.

I quickly came across this issue, and I tried to follow this suggestion from @vefatica:

Does the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\condrv\Start affect this? What if it were changed from 3 (manual) to 2 (autoload)?

After changing the value from 3 to 2 in hexadecimal, the issue was resolved.

I guess this change could help in resolving this issue for everyone who is facing this problem. I hope you would try it, and let me know what happens.

Thanks,
@TheBinitGhimire

@TheBinitGhimire commented on GitHub (Jun 26, 2021): Hi there, I just installed the 21H1 version of Windows 10, and I was facing this issue in Windows Terminal latest release [v1.8.1444.0](https://github.com/microsoft/terminal/releases/tag/v1.8.1444.0) after restarting my computer. I quickly came across this issue, and I tried to follow this suggestion from @vefatica: > Does the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\condrv\Start affect this? What if it were changed from 3 (manual) to 2 (autoload)? After changing the value from 3 to 2 in hexadecimal, the issue was resolved. I guess this change could help in resolving this issue for everyone who is facing this problem. I hope you would try it, and let me know what happens. Thanks, @TheBinitGhimire
claunia commented 2026-01-31 00:44:11 +00:00
Author
Owner
Copy Link

@gwonhong commented on GitHub (Aug 6, 2021):

I just read the suggestion above from @TheBinitGhimire, changing the value 3 to 2, the issue was resolved even without rebooting. Thanks a lot!

@gwonhong commented on GitHub (Aug 6, 2021): I just read the suggestion above from @TheBinitGhimire, changing the value 3 to 2, the issue was resolved even without rebooting. Thanks a lot!
claunia commented 2026-01-31 00:44:11 +00:00
Author
Owner
Copy Link

@fn5 commented on GitHub (Oct 12, 2021):

Had this issue within a Hyper-V VM, guest running 11 21H2 22000.194
Changing the registry key as per post above from @TheBinitGhimire resolved the issue.

@fn5 commented on GitHub (Oct 12, 2021): Had this issue within a Hyper-V VM, guest running 11 21H2 22000.194 Changing the registry key as per post above from @TheBinitGhimire resolved the issue.
claunia commented 2026-01-31 00:44:11 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 28, 2023):

Note

Walkthrough

  • We should add a dedicated error message handler for this
  • It would basically be the same as: fc90045cc3/src/cascadia/TerminalConnection/ConptyConnection.cpp (L431-L438)
    • Text like "This might be due to ConDrv not being started yet. Please refer to <link> for more information"
  • It should theoretically include an aka.ms link to the docs site which explains this (though, we can add the docs and set up the link. That's not something external folks can do)
  • Bonus points: the error message could wrap the URL in an OSC 8 hyperlink
@zadjii-msft commented on GitHub (Apr 28, 2023): > **Note** > ## Walkthrough * We should add a dedicated error message handler for this * It would basically be the same as: https://github.com/microsoft/terminal/blob/fc90045cc37c4862f0d447f7ceb5fe1a20eea3fd/src/cascadia/TerminalConnection/ConptyConnection.cpp#L431-L438 * Text like "This might be due to ConDrv not being started yet. Please refer to \<link> for more information" * It should theoretically include an aka.ms link to the docs site which explains this (though, we can add the docs and set up the link. That's not something external folks can do) * Bonus points: the error message could wrap the URL in an [OSC 8 hyperlink](https://gist.github.com/egmontkob/eb114294efbcd5adb1944c9f3cb5feda)
claunia commented 2026-01-31 00:44:11 +00:00
Author
Owner
Copy Link

@Ayush-mishra-0-0 commented on GitHub (Sep 27, 2023):

Can i work on this issue?

@Ayush-mishra-0-0 commented on GitHub (Sep 27, 2023): Can i work on this issue?
claunia commented 2026-01-31 00:44:11 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 27, 2023):

Sure!

@zadjii-msft commented on GitHub (Sep 27, 2023): Sure!
claunia commented 2026-01-31 00:44:11 +00:00
Author
Owner
Copy Link

@jennarbates commented on GitHub (Apr 20, 2024):

Can I work on this issue?

@jennarbates commented on GitHub (Apr 20, 2024): Can I work on this issue?
claunia commented 2026-01-31 00:44:12 +00:00
Author
Owner
Copy Link

@mattieb commented on GitHub (May 18, 2025):

Does the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\condrv\Start affect this? What if it were changed from 3 (manual) to 2 (autoload)?

So it looks like this is helping some folks, and it helped me too!

You also don't have to use the Registry Editor to set it. Grab an elevated PowerShell and

Get-Service condrv | Set-Service -StartupType Automatic

I don't know enough about Windows to sort out how to make this manual service start when needed by Terminal, but "Automatic" seems like a pretty reasonable way to run condrv to me. Maybe I'm missing something?

@mattieb commented on GitHub (May 18, 2025): > Does the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\condrv\Start affect this? What if it were changed from 3 (manual) to 2 (autoload)? So it looks like this is helping some folks, and it helped me too! You also don't have to use the Registry Editor to set it. Grab an elevated PowerShell and ```powershell Get-Service condrv | Set-Service -StartupType Automatic ``` I don't know enough about Windows to sort out how to make this manual service start when needed by Terminal, but "Automatic" seems like a pretty reasonable way to run condrv to me. Maybe I'm missing something?
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-Server good first issue Help Wanted Issue-Bug Priority-2 Product-Conpty
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#6658
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?