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

Terminal hangs after second invalid invocation of "start powershel" #4680

New Issue
Closed
opened 2026-01-30 23:54:01 +00:00 by claunia · 4 comments
claunia commented 2026-01-30 23:54:01 +00:00
Owner
Copy Link

Originally created by @grkramer on GitHub (Oct 26, 2019).

Environment

Windows build number: 10.0.18363.0
Windows Terminal version (if applicable): 0.6.2951.0

Any other software?
No

Steps to reproduce

  1. Launch Terminal
  2. Open a new cmd tab
  3. Type 'start powershel' and then press enter. The misspelling of PowerShell is part of the repro
  4. A dialog box pops up indicating that 'powershel' cannot be started. Dismiss the dialog box
  5. Type 'start powershel' and then press enter again.

Expected behavior

The same dialog box appears indicating the error and I can dismiss the dialog and continue using the cmd tab.

Actual behavior

The cmd tab hangs and there is no dialog box. Ctrl-C does not recover and the only option I've found to exit this state is to close the tab.

Originally created by @grkramer on GitHub (Oct 26, 2019). # Environment Windows build number: 10.0.18363.0 Windows Terminal version (if applicable): 0.6.2951.0 Any other software? No # Steps to reproduce 1. Launch Terminal 2. Open a new cmd tab 3. Type 'start powershel' and then press enter. The misspelling of PowerShell is part of the repro 4. A dialog box pops up indicating that 'powershel' cannot be started. Dismiss the dialog box 5. Type 'start powershel' and then press enter again. # Expected behavior The same dialog box appears indicating the error and I can dismiss the dialog and continue using the cmd tab. # Actual behavior The cmd tab hangs and there is no dialog box. Ctrl-C does not recover and the only option I've found to exit this state is to close the tab.
claunia commented 2026-01-30 23:54:02 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 28, 2019):

@grkramer Are you sure the dialog isn't just appearing below the Terminal window (in the z-order)?
image

For me, with the acrylic like this, you can see the faint image of the dialog appearing below the terminal. You should be able to alt-tab to the dialog and dismiss it.

@zadjii-msft commented on GitHub (Oct 28, 2019): @grkramer Are you sure the dialog isn't just appearing _below_ the Terminal window (in the z-order)? ![image](https://user-images.githubusercontent.com/18356694/67689321-29391580-f969-11e9-99bd-14dc720d2e5f.png) For me, with the acrylic like this, you can see the faint image of the dialog appearing below the terminal. You should be able to alt-tab to the dialog and dismiss it.
claunia commented 2026-01-30 23:54:02 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 1, 2019):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Nov 1, 2019): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-30 23:54:02 +00:00
Author
Owner
Copy Link

@jantari commented on GitHub (Nov 3, 2019):

I can confirm that the second messagebox appears below the terminal.

Terminal version: 0.6.2951.0
Windows version: 10.0.19013.1

That's inconvenient but what bothers me way more is that focus is not returned to the terminal after dismissing this messagebox:

  1. Open a CMD tab in WT
  2. type start powershel as per OPs example
  3. dismiss the dialog box with ENTER or ESCAPE, if neccessary after alt-tabbing to it
  4. press UP-ARROW to get the last command back and correct it or try typing
  5. nothing will happen as focus is not returned to the terminal window. If you have acrylic enabled this is also evident by the acrylic effect missing
@jantari commented on GitHub (Nov 3, 2019): I can confirm that the second messagebox appears below the terminal. Terminal version: 0.6.2951.0 Windows version: 10.0.19013.1 That's inconvenient but what bothers me way more is that focus is not returned to the terminal after dismissing this messagebox: 1. Open a CMD tab in WT 2. type `start powershel` as per OPs example 3. dismiss the dialog box with ENTER or ESCAPE, if neccessary after alt-tabbing to it 4. press UP-ARROW to get the last command back and correct it or try typing 5. nothing will happen as focus is not returned to the terminal window. If you have acrylic enabled this is also evident by the acrylic effect missing
claunia commented 2026-01-30 23:54:02 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 7, 2019):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Nov 7, 2019): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
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 Needs-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity
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#4680
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?