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

"Start-Process -NoNewWindow cmd.exe" will break the screen and will not accept input. #18980

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

Originally created by @ardotsis on GitHub (Nov 29, 2022).

Windows Terminal version

1.15.2875.0

Windows build number

10.0.22623.0

Other Software

No response

Steps to reproduce

  1. Start PowerShell on WindowsTerminal.
  2. Type Start-Process -NoNewWindow cmd.exe (powershell.exe had the same effect.)

Expected Behavior

No response

Actual Behavior

Two processes are launched in one window. The screen is corrupted and does not accept user input properly.
I would suggest that some sort of restriction be placed on the commands.
(This bug report has been translated. Sorry if anything is unclear.)

Originally created by @ardotsis on GitHub (Nov 29, 2022). ### Windows Terminal version 1.15.2875.0 ### Windows build number 10.0.22623.0 ### Other Software _No response_ ### Steps to reproduce 1. Start PowerShell on WindowsTerminal. 2. Type `Start-Process -NoNewWindow cmd.exe` (`powershell.exe` had the same effect.) ### Expected Behavior _No response_ ### Actual Behavior Two processes are launched in one window. The screen is corrupted and does not accept user input properly. I would suggest that some sort of restriction be placed on the commands. (This bug report has been translated. Sorry if anything is unclear.)
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 06:30:15 +00:00
claunia commented 2026-01-31 06:30:16 +00:00
Author
Owner
Copy Link

@237dmitry commented on GitHub (Nov 29, 2022):

I think this is PowerShell issue. The same behavior in different terminals on Windows and on Linux.

@237dmitry commented on GitHub (Nov 29, 2022): I think this is PowerShell issue. The same behavior in different terminals on Windows and on Linux.
claunia commented 2026-01-31 06:30:17 +00:00
Author
Owner
Copy Link

@237dmitry commented on GitHub (Nov 29, 2022):

This works if you add -Wait switch (identical cmd.exe without Start-Process)

Start-Process cmd.exe -NoNewWindow -Wait

@237dmitry commented on GitHub (Nov 29, 2022): This works if you add `-Wait` switch (identical `cmd.exe` without `Start-Process`) `Start-Process cmd.exe -NoNewWindow -Wait`
claunia commented 2026-01-31 06:30:17 +00:00
Author
Owner
Copy Link

@ardotsis commented on GitHub (Nov 29, 2022):

Thanks for your response! It is indeed a problem on the PowerShell side.
After typing Start-Process cmd.exe -NoNewWindow -Wait, pressing Ctrl + C continues the same behavior. But it is not a WindowsTerminal issue, so I will close this Issue after a while.

@ardotsis commented on GitHub (Nov 29, 2022): Thanks for your response! It is indeed a problem on the PowerShell side. After typing `Start-Process cmd.exe -NoNewWindow -Wait`, pressing `Ctrl + C` continues the same behavior. But it is not a WindowsTerminal issue, so I will close this Issue after a while.
claunia commented 2026-01-31 06:30:17 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 30, 2022):

Thanks for following up!

@DHowett commented on GitHub (Nov 30, 2022): Thanks for following up!
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-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#18980
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?