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

A transparent terminal window and cmd.exe window are opened when running a .bat file #23542

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

Originally created by @GFCYqw on GitHub (Aug 25, 2025).

Windows Terminal version

1.22.12111.0

Windows build number

10.0.26100.0

Other Software

No response

Steps to reproduce

Open any .bat (or some .exe) files

Expected Behavior

Only a windows terminal window is opened and all commands are run in this window.

Actual Behavior

A transparent terminal window was opened first, then all command were run in cmd.exe in another window.

https://github.com/user-attachments/assets/e9d7d907-11f3-4a41-b3f9-8741842b972b

Originally created by @GFCYqw on GitHub (Aug 25, 2025). ### Windows Terminal version 1.22.12111.0 ### Windows build number 10.0.26100.0 ### Other Software _No response_ ### Steps to reproduce Open any .bat (or some .exe) files ### Expected Behavior Only a windows terminal window is opened and all commands are run in this window. ### Actual Behavior A transparent terminal window was opened first, then all command were run in cmd.exe in another window. https://github.com/user-attachments/assets/e9d7d907-11f3-4a41-b3f9-8741842b972b
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 08:45:22 +00:00
claunia commented 2026-01-31 08:45:23 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 25, 2025):

That's not good! Can you use the Feedback Hub's "Advanced Diagnostics" section, in the "Apps > Windows Terminal" category, to collect some diagnostics for us? If you start recording:

Image

then reproduce your issue, it will generate a report you can upload here.

@DHowett commented on GitHub (Aug 25, 2025): That's not good! Can you use the Feedback Hub's "Advanced Diagnostics" section, in the "Apps > Windows Terminal" category, to collect some diagnostics for us? If you start recording: <img width="1260" height="291" alt="Image" src="https://github.com/user-attachments/assets/3c10cbdf-056b-4ce8-b5a1-9d1529e6e6e7" /> then reproduce your issue, it will generate a report you can upload here.
claunia commented 2026-01-31 08:45:23 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 25, 2025):

this is the "defterm window with no tabs" thing

@zadjii-msft commented on GitHub (Aug 25, 2025): this is the "defterm window with no tabs" thing
claunia commented 2026-01-31 08:45:24 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 25, 2025):

Indeed it is. Be nice to get some tracing on it :)

@DHowett commented on GitHub (Aug 25, 2025): Indeed it is. Be nice to get some tracing on it :)
claunia commented 2026-01-31 08:45:24 +00:00
Author
Owner
Copy Link

@GFCYqw commented on GitHub (Aug 31, 2025):

Thx guys for help ^_^
Here is the record, and I rezipped it due to the file size limit.
Please let me know if you need any further information. I'll be happy to assist.

diagnostics.zip

@GFCYqw commented on GitHub (Aug 31, 2025): Thx guys for help ^_^ Here is the record, and I rezipped it due to the file size limit. Please let me know if you need any further information. I'll be happy to assist. [diagnostics.zip](https://github.com/user-attachments/files/22062370/diagnostics.zip)
claunia commented 2026-01-31 08:45:25 +00:00
Author
Owner
Copy Link

@sanioooook commented on GitHub (Sep 7, 2025):

I have a same problem

Windows Terminal version
1.23.12371.0

Windows build number
26100.4946 (Windows 11 Pro)

in event viewer i see this

Faulting application name: WindowsTerminal.exe, version: 1.23.2508.25001, time stamp: 0x68ace21c
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.26100.5074, time stamp: 0x2c3bce81
Exception code: 0xc000027b
Fault offset: 0x00000000008fd0c3
Faulting process id: 0x43EC
Faulting application start time: 0x1DC24B7E92F4453
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.23.12371.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report Id: 61d0d99f-1656-42e3-ad11-abe4bacbeceb
Faulting package full name: Microsoft.WindowsTerminal_1.23.12371.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
@sanioooook commented on GitHub (Sep 7, 2025): I have a same problem **Windows Terminal version** 1.23.12371.0 **Windows build number** 26100.4946 (Windows 11 Pro) in event viewer i see this ``` Faulting application name: WindowsTerminal.exe, version: 1.23.2508.25001, time stamp: 0x68ace21c Faulting module name: Windows.UI.Xaml.dll, version: 10.0.26100.5074, time stamp: 0x2c3bce81 Exception code: 0xc000027b Fault offset: 0x00000000008fd0c3 Faulting process id: 0x43EC Faulting application start time: 0x1DC24B7E92F4453 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.23.12371.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll Report Id: 61d0d99f-1656-42e3-ad11-abe4bacbeceb Faulting package full name: Microsoft.WindowsTerminal_1.23.12371.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ```
claunia commented 2026-01-31 08:45:25 +00:00
Author
Owner
Copy Link

@binki commented on GitHub (Sep 13, 2025):

I couldn’t find parameters which would make the ZIP file small enough. So here’s a 7-zip of it in a zip archive split at 24M and then re-zipped just to keep GitHub happy (GitHub likes neither .7z nor .001, .002, .003, .004, nor .005):

diagnostics_2.zip.001.zip
diagnostics_2.zip.002.zip
diagnostics_2.zip.003.zip
diagnostics_2.zip.004.zip
diagnostics_2.zip.005.zip

I get this issue on occasion too. It normally goes away after a reboot, so it is hard to reproduce. I do not know how to trigger it. I have already reported a similar issue at #16612, but that has a slightly different behavior where the conhost terminal emulator will appear after some timeout. Currently, I just see the Terminal window sitting, as far as I can tell, forever without the fallback behavior ever occurring. Thus I am commenting and sharing diagnostics here.

@binki commented on GitHub (Sep 13, 2025): I couldn’t find parameters which would make the ZIP file small enough. So here’s a 7-zip of it in a zip archive split at 24M and then re-zipped just to keep GitHub happy (GitHub likes neither `.7z` nor `.001`, `.002`, `.003`, `.004`, nor `.005`): [diagnostics_2.zip.001.zip](https://github.com/user-attachments/files/22312062/diagnostics_2.zip.001.zip) [diagnostics_2.zip.002.zip](https://github.com/user-attachments/files/22312063/diagnostics_2.zip.002.zip) [diagnostics_2.zip.003.zip](https://github.com/user-attachments/files/22312061/diagnostics_2.zip.003.zip) [diagnostics_2.zip.004.zip](https://github.com/user-attachments/files/22312060/diagnostics_2.zip.004.zip) [diagnostics_2.zip.005.zip](https://github.com/user-attachments/files/22312059/diagnostics_2.zip.005.zip) I get this issue on occasion too. It normally goes away after a reboot, so it is hard to reproduce. I do not know how to trigger it. I have already reported a similar issue at #16612, but that has a slightly different behavior where the conhost terminal emulator will appear after some timeout. Currently, I just see the Terminal window sitting, as far as I can tell, forever without the fallback behavior ever occurring. Thus I am commenting and sharing diagnostics here.
claunia commented 2026-01-31 08:45:25 +00:00
Author
Owner
Copy Link

@binki commented on GitHub (Sep 13, 2025):

One interesting thing I noticed is that my existing open Terminal which had two tabs open to different CMD sessions and which didn’t appear to be affected stopped drawing too. I can’t open a new tab in it anymore and if I resize it to be larger the portions of the window that were newly added remain translucent. It isn’t marked as “(Not Responding)” but it might as well be. It’s as if all of the windows are for the same process and there is a global lock held somewhere important.

@binki commented on GitHub (Sep 13, 2025): One interesting thing I noticed is that my existing open Terminal which had two tabs open to different CMD sessions and which didn’t appear to be affected stopped drawing too. I can’t open a new tab in it anymore and if I resize it to be larger the portions of the window that were newly added remain translucent. It isn’t marked as “(Not Responding)” but it might as well be. It’s as if all of the windows are for the same process and there is a global lock held somewhere important.
claunia commented 2026-01-31 08:45:25 +00:00
Author
Owner
Copy Link

@binki commented on GitHub (Sep 13, 2025):

Indeed, there was a single WindowsTerminal.exe process. Since I needed to do things in terminals, I went ahead and killed it. After that, I was able to open new functional windows.

@binki commented on GitHub (Sep 13, 2025): Indeed, there was a single WindowsTerminal.exe process. Since I needed to do things in terminals, I went ahead and killed it. After that, I was able to open new functional windows.
claunia commented 2026-01-31 08:45:26 +00:00
Author
Owner
Copy Link

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

if allow start widows terminal when machine startup - problem is solved

@sanioooook commented on GitHub (Sep 30, 2025): if allow start widows terminal when machine startup - problem is solved
claunia commented 2026-01-31 08:45:26 +00:00
Author
Owner
Copy Link

@GFCYqw commented on GitHub (Oct 8, 2025):

if allow start widows terminal when machine startup - problem is solved

Thank you, I tried it, but the problem still exists.

@GFCYqw commented on GitHub (Oct 8, 2025): > if allow start widows terminal when machine startup - problem is solved Thank you, I tried it, but the problem still exists.
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 Issue-Bug Needs-Attention 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#23542
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?