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 not working when pinging #8280

New Issue
Closed
opened 2026-01-31 01:25:19 +00:00 by claunia · 10 comments
claunia commented 2026-01-31 01:25:19 +00:00
Owner
Copy Link

Originally created by @arefg on GitHub (May 19, 2020).

Ctrl+c not working when using ping

When pinging an IP, I can't cancel the ping using Ctrl+c and if I use "ping -t" there is no way of getting out of the ping except closing the entire tab on Windows Terminal.

Platform ServicePack Version VersionString

Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0

Windows Terminal Version: 0.11.1333.0

Originally created by @arefg on GitHub (May 19, 2020). Ctrl+c not working when using ping When pinging an IP, I can't cancel the ping using Ctrl+c and if I use "ping -t" there is no way of getting out of the ping except closing the entire tab on Windows Terminal. [Environment]::OSVersion Platform ServicePack Version VersionString -------- ----------- ------- ------------- Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0 Windows Terminal Version: 0.11.1333.0
claunia added the Resolution-ExternalNeeds-Tag-FixNeeds-Attention labels 2026-01-31 01:25:19 +00:00
claunia commented 2026-01-31 01:25:20 +00:00
Author
Owner
Copy Link

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

How did you start ping? Command Prompt? Windows PowerShell? WSL?

@DHowett commented on GitHub (May 19, 2020): How did you start ping? Command Prompt? Windows PowerShell? WSL?
claunia commented 2026-01-31 01:25:20 +00:00
Author
Owner
Copy Link

@arefg commented on GitHub (May 19, 2020):

Thank you for responding so quickly. I've checked it in cmd, PowerShell 7, PowerShell 5.1, and WSL. It seems that the problem is not specific to any of these shells, because the problem exists in one of my PowerShell 7 tabs but at the same time the other PowerShell 7 tab and other shells are fine. I've seen this behaviour over and over in the last month or so.

@arefg commented on GitHub (May 19, 2020): Thank you for responding so quickly. I've checked it in cmd, PowerShell 7, PowerShell 5.1, and WSL. It seems that the problem is not specific to any of these shells, because the problem exists in one of my PowerShell 7 tabs but at the same time the other PowerShell 7 tab and other shells are fine. I've seen this behaviour over and over in the last month or so.
claunia commented 2026-01-31 01:25:20 +00:00
Author
Owner
Copy Link

@hexnut commented on GitHub (May 20, 2020):

I was able to reproduce this bug, but only when when connected via RDP. The ping command does not respond to a ctrl-c in Powershell via an RDP session but works fine when testing locally.

@hexnut commented on GitHub (May 20, 2020): I was able to reproduce this bug, but only when when connected via RDP. The ping command does not respond to a ctrl-c in Powershell via an RDP session but works fine when testing locally.
claunia commented 2026-01-31 01:25:20 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 22, 2020):

So, wow, this is crazy. I was only able to reproduce this after I've launched ssh once in the session.

If I press ^C while it's prompting for a password, ^C remains broken for the rest of the session forever.

Does that corroborate your findings?

@DHowett commented on GitHub (May 22, 2020): So, wow, this is crazy. I was only able to reproduce this after I've launched `ssh` once in the session. If I press ^C while it's prompting for a password, ^C remains broken for the rest of the session forever. Does that corroborate your findings?
claunia commented 2026-01-31 01:25:20 +00:00
Author
Owner
Copy Link

@Hallucine commented on GitHub (May 22, 2020):

So, wow, this is crazy. I was only able to reproduce this after I've launched ssh once in the session.

If I press ^C while it's prompting for a password, ^C remains broken for the rest of the session forever.

Does that corroborate your findings?

I can reproduce this fairly reliably using ssh and ssh-agent after pressing ^C at a password prompt. When it does stop working I found that terminating the ssh-agent process fixes it.

@Hallucine commented on GitHub (May 22, 2020): > So, wow, this is crazy. I was only able to reproduce this after I've launched `ssh` once in the session. > > If I press ^C while it's prompting for a password, ^C remains broken for the rest of the session forever. > > Does that corroborate your findings? I can reproduce this fairly reliably using `ssh` and `ssh-agent` after pressing ^C at a password prompt. When it does stop working I found that terminating the ssh-agent process fixes it.
claunia commented 2026-01-31 01:25:21 +00:00
Author
Owner
Copy Link

@oising commented on GitHub (May 22, 2020):

My guess is the masked input code for passwords is messing with ENABLE_PROCESSED_INPUT and crippling the break handler and it's not getting restored for some reason.

@oising commented on GitHub (May 22, 2020): My guess is the masked input code for passwords is messing with ENABLE_PROCESSED_INPUT and crippling the break handler and it's not getting restored for some reason.
claunia commented 2026-01-31 01:25:21 +00:00
Author
Owner
Copy Link

@arefg commented on GitHub (May 25, 2020):

@DHowett @Hallucine Exactly, I think this is what happens in my case either, pressing ctrl+c at a password prompt when using ssh produces this problem. I'm not sure if this is even related to Windows Terminal, because this exact behavior happens when using ssh in PowerShell 7 and PowerShell 5.1 without using Windows Terminal.

@arefg commented on GitHub (May 25, 2020): @DHowett @Hallucine Exactly, I think this is what happens in my case either, pressing ctrl+c at a password prompt when using ssh produces this problem. I'm not sure if this is even related to Windows Terminal, because this exact behavior happens when using ssh in PowerShell 7 and PowerShell 5.1 without using Windows Terminal.
claunia commented 2026-01-31 01:25:21 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 29, 2020):

Based on all this, it seems like it's probably an OpenSSH issue. Thanks everyone for letting me know.
Might be worth filing on the upstream Microsoft OpenSSH fork. Better if it comes from a community member than from me! 😄

@DHowett commented on GitHub (May 29, 2020): Based on all this, it seems like it's probably an OpenSSH issue. Thanks everyone for letting me know. Might be worth filing on [the upstream Microsoft OpenSSH fork](https://github.com/powershell/win32-openssh). Better if it comes from a community member than from me! :smile:
claunia commented 2026-01-31 01:25:21 +00:00
Author
Owner
Copy Link

@xobs commented on GitHub (Feb 24, 2022):

This was reported to the Microsoft OpenSSH fork at https://github.com/PowerShell/Win32-OpenSSH/issues/1699

@xobs commented on GitHub (Feb 24, 2022): This was reported to the Microsoft OpenSSH fork at https://github.com/PowerShell/Win32-OpenSSH/issues/1699
claunia commented 2026-01-31 01:25:21 +00:00
Author
Owner
Copy Link

@gunthre commented on GitHub (Jun 16, 2022):

Sorry for reviving an old thread, but I just came across this and found a fix that might help others. Go into Properties (for an existing Powershell instance or a Powershell shortcut), Options tab, Edit Options. Uncheck "Enable Ctrl key shortcuts."

@gunthre commented on GitHub (Jun 16, 2022): Sorry for reviving an old thread, but I just came across this and found a fix that might help others. Go into Properties (for an existing Powershell instance or a Powershell shortcut), Options tab, Edit Options. Uncheck "Enable Ctrl key shortcuts."
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#8280
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?