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

Ctrl+C some programs closes Terminal instead of stopping current process when running PowerShell Core #5538

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

Originally created by @daniefer on GitHub (Dec 12, 2019).

When attempting to stop some programs the terminal will close instead of stopping the current process. npm, ping, and cmd are the only programs I have found so far that do this. Windows Terminal used to not do this and it only started happening after an update about 15-30 days ago. I can provide more info if needed, I just don't know what else to provide.

What I have tried so far

  1. Uninstalling and Reinstalling
  2. Trying running commands in PowerShell Core without Windows Terminal

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Microsoft Windows NT 10.0.18362.0

Windows Terminal version (if applicable):
Windows Terminal (Preview)
Version: 0.7.3382.0

PowerShell Core version
6.2.3

npm version:
6.12.0

node version:
v12.13.0

cmd version:
Microsoft Windows [Version 10.0.18362.476]

Steps to reproduce

  1. Open a terminal
  2. Run cmd
    • this is not the only command that does this. npm run <script> or npm run also do it. These are just the two cases I have run across so far
  3. Enter Ctrl + C
  4. The terminal closes instead of stopping the current running process

Expected behavior

The current running process is killed

Actual behavior

The terminal closes

Originally created by @daniefer on GitHub (Dec 12, 2019). When attempting to stop some programs the terminal will close instead of stopping the current process. `npm`, `ping`, and `cmd` are the only programs I have found so far that do this. Windows Terminal used to not do this and it only started happening after an update about 15-30 days ago. I can provide more info if needed, I just don't know what else to provide. ## What I have tried so far 1. Uninstalling and Reinstalling 1. Trying running commands in PowerShell Core without Windows Terminal # Environment ```none Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] Microsoft Windows NT 10.0.18362.0 Windows Terminal version (if applicable): Windows Terminal (Preview) Version: 0.7.3382.0 PowerShell Core version 6.2.3 npm version: 6.12.0 node version: v12.13.0 cmd version: Microsoft Windows [Version 10.0.18362.476] ``` # Steps to reproduce 1. Open a terminal 1. Run `cmd` * this is not the only command that does this. `npm run <script>` or `npm run` also do it. These are just the two cases I have run across so far 1. Enter `Ctrl + C` 1. The terminal closes instead of stopping the current running process # Expected behavior The current running process is killed # Actual behavior The terminal closes
claunia added the Resolution-Duplicate label 2026-01-31 00:15:43 +00:00
claunia commented 2026-01-31 00:15:44 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Dec 12, 2019):

Did you install powershell core as a dotnet global tool? If so, #3869.

@DHowett-MSFT commented on GitHub (Dec 12, 2019): Did you install powershell core as a dotnet global tool? If so, #3869.
claunia commented 2026-01-31 00:15:44 +00:00
Author
Owner
Copy Link

@daniefer commented on GitHub (Dec 12, 2019):

Wholly cow! You are a god send! Thank you and sorry for the duplicate issue.

@daniefer commented on GitHub (Dec 12, 2019): Wholly cow! You are a god send! Thank you and sorry for the duplicate issue.
claunia commented 2026-01-31 00:15:44 +00:00
Author
Owner
Copy Link

@daniefer commented on GitHub (Dec 12, 2019):

For those looking for a resolution, use the MSI installer

@daniefer commented on GitHub (Dec 12, 2019): For those looking for a resolution, use the MSI installer
claunia commented 2026-01-31 00:15:45 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Dec 12, 2019):

Thanks for confirming! Closing as an actual /dup of #3869.

@DHowett-MSFT commented on GitHub (Dec 12, 2019): Thanks for confirming! Closing as an actual /dup of #3869.
claunia commented 2026-01-31 00:15:45 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Dec 12, 2019):

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 commented on GitHub (Dec 12, 2019): 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!
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 Resolution-Duplicate
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#5538
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?