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

Setting Terminal to default terminal app causes blank screen when running bat file #20098

New Issue
Closed
opened 2026-01-31 07:03:33 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 07:03:33 +00:00
Owner
Copy Link

Originally created by @ToxicSmurf on GitHub (Jun 15, 2023).

Windows Terminal version

1.18.1462.0

Windows build number

10.0.19045.0

Other Software

No response

Steps to reproduce

Settings > Default terminal application > Windows Terminal Preview
Run (any) .bat file

Expected Behavior

.bat file to run

Actual Behavior

error

error 2

Originally created by @ToxicSmurf on GitHub (Jun 15, 2023). ### Windows Terminal version 1.18.1462.0 ### Windows build number 10.0.19045.0 ### Other Software _No response_ ### Steps to reproduce Settings > Default terminal application > Windows Terminal Preview Run (any) .bat file ### Expected Behavior .bat file to run ### Actual Behavior ![error](https://github.com/microsoft/terminal/assets/97206988/664a7aad-4317-4a0c-b681-82efc59e9fe3) ![error 2](https://github.com/microsoft/terminal/assets/97206988/098bb10e-5309-481f-9d3c-af1a5bf8f3f7)
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 07:03:33 +00:00
claunia commented 2026-01-31 07:03:34 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jun 15, 2023):

I think it's unlikely that any .bat file would run into this issue. After all, your screenshot shows an application error in pwsh.exe and .bat files are for cmd.exe. Could you provide us with a .bat file that reproduces the issue? If it involves calling into pwsh.exe, I'd also need the corresponding .ps1 script if possible.

@lhecker commented on GitHub (Jun 15, 2023): I think it's unlikely that any .bat file would run into this issue. After all, your screenshot shows an application error in pwsh.exe and .bat files are for cmd.exe. Could you provide us with a .bat file that reproduces the issue? If it involves calling into pwsh.exe, I'd also need the corresponding .ps1 script if possible.
claunia commented 2026-01-31 07:03:34 +00:00
Author
Owner
Copy Link

@ToxicSmurf commented on GitHub (Jun 16, 2023):

https://gist.github.com/ToxicSmurf/85923e79b8c2a9849bf6c525be504eec

@ToxicSmurf commented on GitHub (Jun 16, 2023): https://gist.github.com/ToxicSmurf/85923e79b8c2a9849bf6c525be504eec
claunia commented 2026-01-31 07:03:34 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jun 16, 2023):

Ah, a fellow MPV user. 😏

That gist has two updater.bat files. You meant the MPV one, right? And it's the scripts from https://sourceforge.net/projects/mpv-player-windows/files/? I also use those, and I just tried running my local MPV's updater.bat and it worked fine. Did you modify your pwsh.exe in any way? Like, let's say, marking it as an adminstrator-only application via the properties page? Or is the mpv directory perhaps inaccessible for the script? Does the issue reproduce if you choose the "Windows Console Host" as the default terminal application in Windows Terminal's settings?

Given that 0xe0434352 is a .NET exception code that occurs in pwsh, I believe it's at least somewhat unlikely that this is a Windows Terminal bug.

But what's especially confusing for me is that your error message has "pwsh.exe" in the title, but the updater.bat file clearly spawns powershell.exe which is an entirely different application. This is all really confusing... 🤔

@lhecker commented on GitHub (Jun 16, 2023): Ah, a fellow MPV user. 😏 That gist has two updater.bat files. You meant the MPV one, right? And it's the scripts from https://sourceforge.net/projects/mpv-player-windows/files/? I also use those, and I just tried running my local MPV's updater.bat and it worked fine. Did you modify your pwsh.exe in any way? Like, let's say, marking it as an adminstrator-only application via the properties page? Or is the mpv directory perhaps inaccessible for the script? Does the issue reproduce if you choose the "Windows Console Host" as the default terminal application in Windows Terminal's settings? Given that 0xe0434352 is a .NET exception code that occurs in pwsh, I believe it's at least somewhat unlikely that this is a Windows Terminal bug. But what's especially confusing for me is that your error message has "pwsh.exe" in the title, but the `updater.bat` file clearly spawns `powershell.exe` which is an entirely different application. This is all really confusing... 🤔
claunia commented 2026-01-31 07:03:34 +00:00
Author
Owner
Copy Link

@ToxicSmurf commented on GitHub (Jun 17, 2023):

I added the second updater.bat file because the error was occurring when I tried to run it as well. You're right, though; it wasn't a Windows Terminal bug. My bad 😭 I had my ComSpec environment variable pointed to pwsh.exe for some reason. Reverting that fixed the issue. Sorry!

@ToxicSmurf commented on GitHub (Jun 17, 2023): I added the second `updater.bat` file because the error was occurring when I tried to run it as well. You're right, though; it wasn't a Windows Terminal bug. My bad 😭 I had my `ComSpec` environment variable pointed to `pwsh.exe` for some reason. Reverting that fixed the issue. Sorry!
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#20098
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?