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

PowerShell Core + RoboCopy: Ctrl-C does not interrupt execution #17798

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

Originally created by @doxxx on GitHub (Jun 24, 2022).

Windows Terminal version

1.13.11431.0

Windows build number

10.0.19044.1766

Other Software

PowerShell Core 7.2.5

Steps to reproduce

  1. Open PowerShell Core in Windows Terminal
  2. Run RoboCopy command to copy files from one directory to another
  3. Press Ctrl-C to interrupt

Expected Behavior

Robocopy execution is interrupted and control returns to the prompt.

Actual Behavior

When using PowerShell Core inside Windows Terminal, Ctrl-C does not interrupt Robocopy. Robocopy continues running and when it finishes, all the Ctrl-C presses are replayed at the prompt as they had been pressed after Robocopy had completed.

Ctrl-C to interrupt works in CMD running in Windows Terminal and in PowerShell Core using standard console window.

Originally created by @doxxx on GitHub (Jun 24, 2022). ### Windows Terminal version 1.13.11431.0 ### Windows build number 10.0.19044.1766 ### Other Software PowerShell Core 7.2.5 ### Steps to reproduce 1. Open PowerShell Core in Windows Terminal 2. Run RoboCopy command to copy files from one directory to another 3. Press Ctrl-C to interrupt ### Expected Behavior Robocopy execution is interrupted and control returns to the prompt. ### Actual Behavior When using PowerShell Core inside Windows Terminal, Ctrl-C does not interrupt Robocopy. Robocopy continues running and when it finishes, all the Ctrl-C presses are replayed at the prompt as they had been pressed after Robocopy had completed. Ctrl-C to interrupt works in CMD running in Windows Terminal and in PowerShell Core using standard console window.
claunia added the Needs-TriageIssue-BugNeeds-Tag-FixNeeds-Attention labels 2026-01-31 05:53:43 +00:00
claunia commented 2026-01-31 05:53:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 10, 2022):

How did you install PowerShell core/? I vaguely remember some issue about the global tools installer and control+c...

@zadjii-msft commented on GitHub (Aug 10, 2022): How did you install PowerShell core/? I vaguely remember some issue about the global tools installer and control+c...
claunia commented 2026-01-31 05:53:45 +00:00
Author
Owner
Copy Link

@doxxx commented on GitHub (Aug 11, 2022):

Either winget or the MSI installer. I'm 100% certain that I did not use dotnet tool install to install it, since this occurred while I was setting up a new laptop and PowerShell Core was one of the first things I installed even before the dotnet SDK.

@doxxx commented on GitHub (Aug 11, 2022): Either `winget` or the MSI installer. I'm 100% certain that I did not use `dotnet tool install` to install it, since this occurred while I was setting up a new laptop and PowerShell Core was one of the first things I installed even before the dotnet SDK.
claunia commented 2026-01-31 05:53:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 12, 2022):

Hmm, this isn't #6258 - That thread is more just a delay between pressing and receiving, and this is more robocopy DGAF and just doesn't read the console input at all. Hmm...

@zadjii-msft commented on GitHub (Aug 12, 2022): Hmm, this isn't #6258 - That thread is more just a delay between pressing and receiving, and this is more _robocopy DGAF_ and just doesn't read the console input at all. Hmm...
claunia commented 2026-01-31 05:53:46 +00:00
Author
Owner
Copy Link

@doxxx commented on GitHub (Aug 12, 2022):

It does work in CMD though...

@doxxx commented on GitHub (Aug 12, 2022): It does work in CMD though...
claunia commented 2026-01-31 05:53:46 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 12, 2022):

It does work in CMD though...

TO CLARIFY: Does this work in CMD tabs in the Terminal, or CMD in the vintage console (conhost.exe)?

@zadjii-msft commented on GitHub (Aug 12, 2022): > It does work in CMD though... TO CLARIFY: Does this work in CMD tabs in the Terminal, or CMD in the vintage console (conhost.exe)?
claunia commented 2026-01-31 05:53:46 +00:00
Author
Owner
Copy Link

@doxxx commented on GitHub (Aug 12, 2022):

I just retested this with Windows Terminal 1.14.1962.0 and PowerShell Core 7.2.5 and I can no longer reproduce the problem.

@doxxx commented on GitHub (Aug 12, 2022): I just retested this with Windows Terminal 1.14.1962.0 and PowerShell Core 7.2.5 and I can no longer reproduce the problem.
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-Attention Needs-Tag-Fix 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#17798
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?