You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Windows build number: Microsoft Windows [Version 10.0.18363.720]
Windows Terminal version 0.10.781.0
Any other software?
Steps to reproduce
start a terminal with a cmd.exe (not powershell) session
move the terminal window to the center of the screen
at the cmd prompt run start thisdoesnotexist
Expected behavior
a dialog is shown in front of the terminal window
Actual behavior
the dialog is shown behind the window.
there is no visible feedback that this has happened (there is an audio error queue but without sound you do not hear this)
this makes it appear as though the cmd session has hung.
contrast this to what happens when running cmd.exe in its "legacy" window (ie not in terminal)
The text was updated successfully, but these errors were encountered:
ghost
added
Needs-Triage
It's a new issue that the core contributor team needs to triage at the next triage meeting
Needs-Tag-Fix
Doesn't match tag requirements
labels
Mar 31, 2020
Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
ghost
added
Resolution-Duplicate
There's another issue on the tracker that's pretty much the same thing.
and removed
Needs-Triage
It's a new issue that the core contributor team needs to triage at the next triage meeting
Needs-Tag-Fix
Doesn't match tag requirements
labels
Mar 31, 2020
Environment
Steps to reproduce
start a terminal with a cmd.exe (not powershell) session
move the terminal window to the center of the screen
at the cmd prompt run
start thisdoesnotexist
Expected behavior
a dialog is shown in front of the terminal window

Actual behavior
the dialog is shown behind the window.
there is no visible feedback that this has happened (there is an audio error queue but without sound you do not hear this)
this makes it appear as though the cmd session has hung.
contrast this to what happens when running cmd.exe in its "legacy" window (ie not in terminal)
The text was updated successfully, but these errors were encountered: