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 doen't stop a program in windows terminal powershell console. #9075

New Issue
Closed
opened 2026-01-31 01:45:17 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 01:45:17 +00:00
Owner
Copy Link

Originally created by @xchern on GitHub (Jun 17, 2020).

Environment

Windows build number:
Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.18362.0 Microsoft Windows NT 10.0.18362.0

Windows Terminal version (if applicable):
Version: 1.0.1401.0

Any other software?
Windows built-in ssh:
PS> ssh -V
OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5

Steps to reproduce

  1. open a powershell window.
  2. try to connect a ssh sever with ssh, press Ctrl+C to quit when it ask for password.
  3. run a endless program, for example ping bing.com /t, which will not quit by itself. Ctrl+C doesn't end the program.

Expected behavior

Ctrl+C should end the running program.

Actual behavior

Ctrl+C does not end the program.

Originally created by @xchern on GitHub (Jun 17, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Platform ServicePack Version VersionString -------- ----------- ------- ------------- Win32NT 10.0.18362.0 Microsoft Windows NT 10.0.18362.0 Windows Terminal version (if applicable): Version: 1.0.1401.0 Any other software? Windows built-in ssh: PS> ssh -V OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5 ``` # Steps to reproduce 1. open a powershell window. 2. try to connect a ssh sever with ssh, press Ctrl+C to quit when it ask for password. 3. run a endless program, for example `ping bing.com /t`, which will not quit by itself. Ctrl+C doesn't end the program. # Expected behavior Ctrl+C should end the running program. # Actual behavior Ctrl+C does not end the program.
claunia added the Resolution-ExternalNeeds-Tag-FixNeeds-Attention labels 2026-01-31 01:45:17 +00:00
claunia commented 2026-01-31 01:45:18 +00:00
Author
Owner
Copy Link

@xchern commented on GitHub (Jun 17, 2020):

After more test, I noticed this is probably a powershell bug. The same operation in cmd has no problem.

@xchern commented on GitHub (Jun 17, 2020): After more test, I noticed this is probably a powershell bug. The same operation in cmd has no problem.
claunia commented 2026-01-31 01:45:18 +00:00
Author
Owner
Copy Link

@finsterdexter commented on GitHub (Jun 17, 2020):

What version of Powershell were you using? Powershell Core v7? Something else?

I am seeing this issue in Terminal, as well, while running a long running task. The tab seems to crash with [process exited with code 3221225786] when I press Ctrl-C, and the program keeps running in background.

My env:
Windows 10 Pro 19041.329
same version of Terminal (1.0.1401.0)
This is happening in a Powershell Core tab, Powershell Core v7.0.2

If I run my task in a standalone Powershell Core window, I do not see this behavior, and Ctrl-C works as expected, i.e. shuts down the task gracefully. It only happens to me in Terminal. In my case, I'm running a docker-compose process using Docker Desktop v2.3.0.3

@finsterdexter commented on GitHub (Jun 17, 2020): What version of Powershell were you using? Powershell Core v7? Something else? I am seeing this issue in Terminal, as well, while running a long running task. The tab seems to crash with `[process exited with code 3221225786]` when I press Ctrl-C, and the program keeps running in background. My env: Windows 10 Pro 19041.329 same version of Terminal (1.0.1401.0) This is happening in a Powershell Core tab, Powershell Core v7.0.2 If I run my task in a standalone Powershell Core window, I do not see this behavior, and Ctrl-C works as expected, i.e. shuts down the task gracefully. It only happens to me in Terminal. In my case, I'm running a docker-compose process using Docker Desktop v2.3.0.3
claunia commented 2026-01-31 01:45:19 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 17, 2020):

I am seeing this issue in Terminal, as well, while running a long running task. The tab seems to crash with [process exited with code 3221225786] when I press Ctrl-C, and the program keeps running in background.

This is a totally different issue. You have either installed PowerShell Core via Scoop or as a dotnet global tool before v7.0 came out. More info here (dotnet) https://github.com/PowerShell/PowerShell/issues/11314 and (scoop) https://github.com/lukesampson/scoop/issues/3634.

I'm going to mark this comment and yours as "off-topic"; if you continue running into this issue after investigating the dotnet/scoop bug reports, please file a new issue.

@DHowett commented on GitHub (Jun 17, 2020): > I am seeing this issue in Terminal, as well, while running a long running task. The tab seems to crash with [process exited with code 3221225786] when I press Ctrl-C, and the program keeps running in background. This is a totally different issue. You have either installed PowerShell Core via Scoop or as a dotnet global tool before v7.0 came out. More info here (dotnet) https://github.com/PowerShell/PowerShell/issues/11314 and (scoop) https://github.com/lukesampson/scoop/issues/3634. I'm going to mark this comment and yours as "off-topic"; if you continue running into this issue after investigating the dotnet/scoop bug reports, please _file a new issue._
claunia commented 2026-01-31 01:45:19 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 17, 2020):

@xiaosong0911 Are you using any other software in the affected tabs? Sometimes when you run "ssh" in the same window, ssh disables Ctrl+C.

@DHowett commented on GitHub (Jun 17, 2020): @xiaosong0911 Are you using any other software in the affected tabs? Sometimes when you run "ssh" in the same window, ssh disables <kbd>Ctrl+C</kbd>.
claunia commented 2026-01-31 01:45:19 +00:00
Author
Owner
Copy Link

@xchern commented on GitHub (Jun 19, 2020):

@xiaosong0911 Are you using any other software in the affected tabs? Sometimes when you run "ssh" in the same window, ssh disables Ctrl+C.

I only used "ssh" and "ping" as described in the steps to reproduce. I have no idea how ssh can disable Ctrl+C.

BTW, I noticed this problem also occurs in the windows' built-in powershell window, so it is probably a bug of powershell or ssh rather than windows terminal.

@xchern commented on GitHub (Jun 19, 2020): > @xiaosong0911 Are you using any other software in the affected tabs? Sometimes when you run "ssh" in the same window, ssh disables Ctrl+C. I only used "ssh" and "ping" as described in the steps to reproduce. I have no idea how ssh can disable `Ctrl+C`. BTW, I noticed this problem also occurs in the windows' built-in powershell window, so it is probably a bug of powershell or ssh rather than windows terminal.
claunia commented 2026-01-31 01:45:19 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 19, 2020):

Yes, there is an API that globally disables Ctrl+C for the whole console window. SSH uses it, sometimes, and does not enable it again.

@DHowett commented on GitHub (Jun 19, 2020): Yes, there is an API that globally disables Ctrl+C for the whole console window. SSH uses it, sometimes, and does not enable it again.
claunia commented 2026-01-31 01:45:19 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 19, 2020):

Thanks!

@DHowett commented on GitHub (Jun 19, 2020): Thanks!
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-Attention Needs-Tag-Fix Resolution-External
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#9075
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?