System Error dialog cannot display with Command Prompt #20633

Open
opened 2026-01-31 07:19:42 +00:00 by claunia · 2 comments
Owner

Originally created by @TGSAN on GitHub (Oct 8, 2023).

Windows Terminal version

1.18.2681.0/1.19.2682.0

Windows build number

10.0.19045.3516/10.0.22631.2361

Other Software

No response

Steps to reproduce

  1. Launch Windows Terminal using "Open with Terminal" in explorer context menu.
  2. Switch to Command Prompt.
  3. Execute a dll missing or runtime error CLI program binary using Command Prompt.
  4. System Error dialog cannot display. (no error information display, but process exited)

Expected Behavior

Display a system error dialog. (if launch cmd.exe or Windows Terminal in Win+R direct, and execute a dll missing or runtime error CLI program binary, it can display system error dialog)

Actual Behavior

System Error dialog cannot display.

Originally created by @TGSAN on GitHub (Oct 8, 2023). ### Windows Terminal version 1.18.2681.0/1.19.2682.0 ### Windows build number 10.0.19045.3516/10.0.22631.2361 ### Other Software _No response_ ### Steps to reproduce 1. Launch Windows Terminal using "Open with Terminal" in explorer context menu. 2. Switch to Command Prompt. 3. Execute a dll missing or runtime error CLI program binary using Command Prompt. 4. System Error dialog cannot display. (no error information display, but process exited) ### Expected Behavior Display a system error dialog. (if launch cmd.exe or Windows Terminal in Win+R direct, and execute a dll missing or runtime error CLI program binary, it can display system error dialog) ### Actual Behavior System Error dialog cannot display.
claunia added the Issue-BugProduct-ConptyArea-Windowing labels 2026-01-31 07:19:42 +00:00
Author
Owner

@TGSAN commented on GitHub (Oct 8, 2023):

Using "Open with Terminal" context menu item to launch Windows Terminal:

(Bug)

https://github.com/microsoft/terminal/assets/7440847/4cf8a041-a1ff-47e9-afc3-6b5e00a10ff9

Using Win+R to launch Windows Terminal:

(No Bug)

https://github.com/microsoft/terminal/assets/7440847/ff1aa919-1ec4-459e-9fe8-f7722c9484a5

@TGSAN commented on GitHub (Oct 8, 2023): ### Using "Open with Terminal" context menu item to launch Windows Terminal: > (Bug) https://github.com/microsoft/terminal/assets/7440847/4cf8a041-a1ff-47e9-afc3-6b5e00a10ff9 ### Using Win+R to launch Windows Terminal: > (No Bug) https://github.com/microsoft/terminal/assets/7440847/ff1aa919-1ec4-459e-9fe8-f7722c9484a5
Author
Owner

@zadjii-msft commented on GitHub (Dec 4, 2023):

Huh. That's really weird, for sure. Why would opening the Terminal via the shell extension change the window parenting?

It's not a defterm issue, cause wt.exe is getting launched directly. I coulda swore there was another issue around here for something similar, a situation where the phwnd didn't get created/parented right

@zadjii-msft commented on GitHub (Dec 4, 2023): Huh. That's really weird, for sure. Why would opening the Terminal via the shell extension change the window parenting? It's not a defterm issue, cause `wt.exe` is getting launched directly. I coulda swore there was another issue around here for something similar, a situation where the phwnd didn't get created/parented right
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20633