Ctrl+Break behaves in cmd not as expected #7027

Open
opened 2026-01-31 00:53:18 +00:00 by claunia · 0 comments
Owner

Originally created by @schlamar on GitHub (Mar 20, 2020).

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.720]
Windows Terminal version (if applicable): Version: 0.10.761.0

Usually a Ctrl+C behaves different than Ctrl+Break in a cmd console.

But in Windows Terminal Ctrl+Break behaves like Ctrl+C.

For example you can reproduce this with Python by running in cmd

py -c "import time; time.sleep(60)"

Expected behavior

Ctrl+C --> KeyboardInterrupt
Ctrl+Break --> Program quits without KeyobardInterrupt

This is the default behavior in standalone cmd.exe.

Actual behavior

Ctrl+C --> KeyboardInterrupt
Ctrl+Break --> KeyboardInterrupt

Originally created by @schlamar on GitHub (Mar 20, 2020). # Environment ```none Windows build number: Microsoft Windows [Version 10.0.18363.720] Windows Terminal version (if applicable): Version: 0.10.761.0 ``` Usually a Ctrl+C behaves different than Ctrl+Break in a cmd console. But in Windows Terminal Ctrl+Break behaves like Ctrl+C. For example you can reproduce this with Python by running in cmd py -c "import time; time.sleep(60)" # Expected behavior Ctrl+C --> KeyboardInterrupt Ctrl+Break --> Program quits **without** KeyobardInterrupt This is the default behavior in standalone cmd.exe. # Actual behavior Ctrl+C --> KeyboardInterrupt Ctrl+Break --> KeyboardInterrupt
claunia added the Resolution-Duplicate label 2026-01-31 00:53:18 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7027