Issue: In Windows 10 Insider build 15002, when running Bash.exe, CTRL + chords are not being correctly handled by the Windows Console.
Effect: Users will be unable to terminate Linux apps using CTRL + C, or background running tasks using CTRL + Z, etc. When CTRL + C is hit in Bash, a ‘c’ is displayed in the bash console.
Work-Around(s): Until fixed:
Run Linux tools that require CTRL + C to terminate in a separate Bash console session; these individual bash consoles can then be closed when needed without disrupting your interactive bash consoles
Map an alternate key to Ctrl+C. For example, to map Ctrl+K to Ctrl+C run: stty intr \^k. This mapping is per terminal and will have to be done every time bash is launched. Users can include this in their .bashrc if preferred
Scope: This issue only affects Bash sessions and does not prevent CTRL + C, etc. in other console apps or shells (i.e. Cmd or PowerShell).
Issue: In Windows 10 Insider build 15002, when running Bash.exe, CTRL + chords are not being correctly handled by the Windows Console.
Effect: Users will be unable to terminate Linux apps using CTRL + C, or background running tasks using CTRL + Z, etc. When CTRL + C is hit in Bash, a ‘c’ is displayed in the bash console.
Work-Around(s): Until fixed:
stty intr \^k
. This mapping is per terminal and will have to be done every time bash is launched. Users can include this in their .bashrc if preferredScope: This issue only affects Bash sessions and does not prevent CTRL + C, etc. in other console apps or shells (i.e. Cmd or PowerShell).
For more information on this release, including the many other fixes it DOES include, be sure to read the build 15002 Release Notes.
We apologize for this annoying issue. A fix has been checked-in and will be released ASAP into an up-coming Insiders build.