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 in gitbash on windows terminal kills ssh remote sessions #16716

New Issue
Closed
opened 2026-01-31 05:20:32 +00:00 by claunia · 44 comments
claunia commented 2026-01-31 05:20:32 +00:00
Owner
Copy Link

Originally created by @avasant21 on GitHub (Feb 8, 2022).

Windows Terminal version

1.11.3471.0

Windows build number

10.0.19043.0

Other Software

Gitbash - mintty 3.5.2

Steps to reproduce

  1. Added the gitbash as default profile in Windows Terminal
  2. Logged into ssh remote systems
  3. Pressing ctlr+c(keyboard interrupt) kills the remote sessions and brings the prompt back to git bash

This behavior is not observed when directly running on Gitbash terminal

Expected Behavior

ctlr+c should just interrupt the current process not the sessions

Actual Behavior

Pressing ctlr+c(keyboard interrupt) kills the remote sessions and brings the prompt back to git bash

Originally created by @avasant21 on GitHub (Feb 8, 2022). ### Windows Terminal version 1.11.3471.0 ### Windows build number 10.0.19043.0 ### Other Software Gitbash - mintty 3.5.2 ### Steps to reproduce 1. Added the gitbash as default profile in Windows Terminal 2. Logged into ssh remote systems 3. Pressing ctlr+c(keyboard interrupt) kills the remote sessions and brings the prompt back to git bash This behavior is not observed when directly running on Gitbash terminal ### Expected Behavior ctlr+c should just interrupt the current process not the sessions ### Actual Behavior Pressing ctlr+c(keyboard interrupt) kills the remote sessions and brings the prompt back to git bash
claunia commented 2026-01-31 05:20:33 +00:00
Author
Owner
Copy Link

@fredrik-corneliusson commented on GitHub (Feb 10, 2022):

Bug is also discussed in git for windows:
https://github.com/git-for-windows/git/issues/3657#issuecomment-1024020071

@fredrik-corneliusson commented on GitHub (Feb 10, 2022): Bug is also discussed in git for windows: https://github.com/git-for-windows/git/issues/3657#issuecomment-1024020071
claunia commented 2026-01-31 05:20:34 +00:00
Author
Owner
Copy Link

@akulbe commented on GitHub (Feb 17, 2022):

Okay, I thought this issue was with my keyboard. This is happening here multiple times per day, and it's making me crazy. 🤪

@akulbe commented on GitHub (Feb 17, 2022): Okay, I thought this issue was with my keyboard. This is happening here multiple times per day, and it's making me crazy. 🤪
claunia commented 2026-01-31 05:20:34 +00:00
Author
Owner
Copy Link

@poonsakn commented on GitHub (Apr 8, 2022):

This also happen to me when using puTTY via plink command.

Windows Terminal
Version: 1.11.3471.0
@poonsakn commented on GitHub (Apr 8, 2022): This also happen to me when using puTTY via plink command. ``` Windows Terminal Version: 1.11.3471.0 ```
claunia commented 2026-01-31 05:20:34 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 8, 2022):

huh, so this is like the opposite of #8034

@zadjii-msft commented on GitHub (Apr 8, 2022): huh, so this is like the _opposite_ of #8034
claunia commented 2026-01-31 05:20:34 +00:00
Author
Owner
Copy Link

@macdjord commented on GitHub (Apr 11, 2022):

I've been seeing this every since I updated from git version 2.35.1.windows.2 to git version 2.36.0.rc0.windows.1.

Also, I've noticed something odd: after accidentally killing an SSH session in this way, the terminal stops echoing characters when I type them.

@macdjord commented on GitHub (Apr 11, 2022): I've been seeing this every since I updated from `git version 2.35.1.windows.2` to `git version 2.36.0.rc0.windows.1`. Also, I've noticed something odd: after accidentally killing an SSH session in this way, the terminal stops echoing characters when I type them.
claunia commented 2026-01-31 05:20:35 +00:00
Author
Owner
Copy Link

@aschaepper commented on GitHub (Apr 12, 2022):

Got the same behavior but also with the older Git Version:
git version 2.35.1.windows.2
It only hapens in the git shell, other shells like powershell work.

Also the keyboard buttons home and end seem to behave weird, but only on some kind of target machines (ARM/Yoctolinux/Busybox in my case) on Ubuntu 20 home and end works. but Ctrl-c also closes the connection.

Running windows Terminal 1.12.10733.0 from the store on:
Windows 11:
21H2
OSBuild: 22000.593
Windows Feature Experience Pack 1000.22000.593.0

Reinstalled Windows Terminal, Reset the settings nothing worked so far.

@aschaepper commented on GitHub (Apr 12, 2022): Got the same behavior but also with the older Git Version: git version 2.35.1.windows.2 It only hapens in the git shell, other shells like powershell work. Also the keyboard buttons home and end seem to behave weird, but only on some kind of target machines (ARM/Yoctolinux/Busybox in my case) on Ubuntu 20 home and end works. but Ctrl-c also closes the connection. Running windows Terminal 1.12.10733.0 from the store on: Windows 11: 21H2 OSBuild: 22000.593 Windows Feature Experience Pack 1000.22000.593.0 Reinstalled Windows Terminal, Reset the settings nothing worked so far.
claunia commented 2026-01-31 05:20:35 +00:00
Author
Owner
Copy Link

@WereCatf commented on GitHub (Apr 14, 2022):

I noticed this bug a while ago already and haven't found a fix for it. So far I've stuck to 2.34.1, because I really need SSH and ctrl+c to work.

Would be nice to know, if the issue is caused by Windows Terminal or Gitbash, though.

@WereCatf commented on GitHub (Apr 14, 2022): I noticed this bug a while ago already and haven't found a fix for it. So far I've stuck to 2.34.1, because I really need SSH and ctrl+c to work. Would be nice to know, if the issue is caused by Windows Terminal or Gitbash, though.
claunia commented 2026-01-31 05:20:35 +00:00
Author
Owner
Copy Link

@kennyhyun commented on GitHub (Apr 16, 2022):

ssh in Command Prompt (on Windows Terminal) has no such issue

@kennyhyun commented on GitHub (Apr 16, 2022): ssh in Command Prompt (on Windows Terminal) has no such issue
claunia commented 2026-01-31 05:20:35 +00:00
Author
Owner
Copy Link

@joaommartins commented on GitHub (Apr 26, 2022):

Seems to be fixed in git version 2.36.0.windows.1, running on Windows Terminal build 1.12.10982.0.

@joaommartins commented on GitHub (Apr 26, 2022): Seems to be fixed in git version 2.36.0.windows.1, running on Windows Terminal build 1.12.10982.0.
claunia commented 2026-01-31 05:20:35 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 26, 2022):

@joaommartins that's great to hear! I had a sneaking suspicion this was a git bash issue, but I was having a hard time tracking this down.

Can any other folks confirm/? Hopefully we can just close this one out ☺️

@zadjii-msft commented on GitHub (Apr 26, 2022): @joaommartins that's great to hear! I had a sneaking suspicion this was a git bash issue, but I was having a hard time tracking this down. Can any other folks confirm/? Hopefully we can just close this one out ☺️
claunia commented 2026-01-31 05:20:35 +00:00
Author
Owner
Copy Link

@WereCatf commented on GitHub (Apr 26, 2022):

I can confirm, works fine with 2.36.0 again.

@WereCatf commented on GitHub (Apr 26, 2022): I can confirm, works fine with 2.36.0 again.
claunia commented 2026-01-31 05:20:36 +00:00
Author
Owner
Copy Link

@Throbac-Labs commented on GitHub (Apr 30, 2022):

im runnning git version 2.36.0.windows.1 and still seeing this issue. Should i attempt a rollback? or uninstall and re-install git?

@Throbac-Labs commented on GitHub (Apr 30, 2022): im runnning git version 2.36.0.windows.1 and still seeing this issue. Should i attempt a rollback? or uninstall and re-install git?
claunia commented 2026-01-31 05:20:36 +00:00
Author
Owner
Copy Link

@ijin82 commented on GitHub (May 9, 2022):

Same for me. That's awfull.

@ijin82 commented on GitHub (May 9, 2022): Same for me. That's awfull.
claunia commented 2026-01-31 05:20:36 +00:00
Author
Owner
Copy Link

@jeefs commented on GitHub (May 18, 2022):

marked

@jeefs commented on GitHub (May 18, 2022): marked
claunia commented 2026-01-31 05:20:36 +00:00
Author
Owner
Copy Link

@MiguelBamberino commented on GitHub (Jul 11, 2022):

I am on 2.36.1.windows.1 and still getting issue,

@MiguelBamberino commented on GitHub (Jul 11, 2022): I am on 2.36.1.windows.1 and still getting issue,
claunia commented 2026-01-31 05:20:36 +00:00
Author
Owner
Copy Link

@ijin82 commented on GitHub (Jul 12, 2022):

I am on 2.36.1.windows.1 and still getting issue,

just upgraded (chocolatey) to microsoft-windows-terminal 1.14.1861.0 + git 2.37.0
works fine (resolved)

@ijin82 commented on GitHub (Jul 12, 2022): > I am on 2.36.1.windows.1 and still getting issue, just upgraded (chocolatey) to **microsoft-windows-terminal 1.14.1861.0** + **git 2.37.0** **w**orks fine (resolved)
claunia commented 2026-01-31 05:20:37 +00:00
Author
Owner
Copy Link

@OrlinAlvarado commented on GitHub (Jul 13, 2022):

I'm having the same issue, but only when using Git Bash. In the PowerShell and CMD, it works correctly.

Any idea?

@OrlinAlvarado commented on GitHub (Jul 13, 2022): I'm having the same issue, but only when using Git Bash. In the PowerShell and CMD, it works correctly. Any idea?
claunia commented 2026-01-31 05:20:37 +00:00
Author
Owner
Copy Link

@boly38 commented on GitHub (Jul 13, 2022):

@OrlinAlvarado not sure that everyone noticed the workaround quoted in git-for-windows/git/issues/3657 and that worked for me

export MSYS=enable_pcon

@boly38 commented on GitHub (Jul 13, 2022): @OrlinAlvarado not sure that everyone noticed the **workaround** quoted in git-for-windows/git/issues/3657 and that worked for me >export MSYS=enable_pcon
claunia commented 2026-01-31 05:20:37 +00:00
Author
Owner
Copy Link

@OrlinAlvarado commented on GitHub (Jul 13, 2022):

@OrlinAlvarado not sure that everyone noticed the workaround quoted in git-for-windows/git/issues/3657 and that worked for me

export MSYS=enable_pcon

Hi, @boly38 I added what you suggested, but CTRL+C, exit my ssh session.

@OrlinAlvarado commented on GitHub (Jul 13, 2022): > @OrlinAlvarado not sure that everyone noticed the **workaround** quoted in [git-for-windows/git/issues/3657](https://github.com/git-for-windows/git/issues/3657) and that worked for me > > > export MSYS=enable_pcon Hi, @boly38 I added what you suggested, but CTRL+C, exit my ssh session.
claunia commented 2026-01-31 05:20:37 +00:00
Author
Owner
Copy Link

@Shenmin-Z commented on GitHub (Jul 21, 2022):

@rdoering it's not in the store, but if you are asking when will an official Git for Windows be available with this fix: It is now. https://github.com/git-for-windows/git/releases/tag/v2.36.0.windows.1

@OrlinAlvarado 2.36.0 works.

@Shenmin-Z commented on GitHub (Jul 21, 2022): > @rdoering it's not in the store, but if you are asking when will an official Git for Windows be available with this fix: It is now. https://github.com/git-for-windows/git/releases/tag/v2.36.0.windows.1 @OrlinAlvarado 2.36.0 works.
claunia commented 2026-01-31 05:20:37 +00:00
Author
Owner
Copy Link

@rdoering commented on GitHub (Jul 23, 2022):

@Shenmin-Z thanks

@rdoering commented on GitHub (Jul 23, 2022): @Shenmin-Z thanks
claunia commented 2026-01-31 05:20:38 +00:00
Author
Owner
Copy Link

@0xaead commented on GitHub (Aug 14, 2022):

I rolled back till https://github.com/git-for-windows/git/releases/tag/v2.32.0.windows.1 to solve this issue. What a long and winding road.

@0xaead commented on GitHub (Aug 14, 2022): I rolled back till https://github.com/git-for-windows/git/releases/tag/v2.32.0.windows.1 to solve this issue. What a long and winding road.
claunia commented 2026-01-31 05:20:38 +00:00
Author
Owner
Copy Link

@83leej commented on GitHub (Aug 25, 2022):

reverted back to 2.30.0 to get this to work again

@83leej commented on GitHub (Aug 25, 2022): reverted back to 2.30.0 to get this to work again
claunia commented 2026-01-31 05:20:38 +00:00
Author
Owner
Copy Link

@OrlinAlvarado commented on GitHub (Aug 25, 2022):

I decided to use a different terminal for windows.
https://conemu.github.io/

@OrlinAlvarado commented on GitHub (Aug 25, 2022): I decided to use a different terminal for windows. https://conemu.github.io/
claunia commented 2026-01-31 05:20:38 +00:00
Author
Owner
Copy Link

@aschaepper commented on GitHub (Oct 30, 2022):

Perfect, works with new Version of Git! 2.38

@aschaepper commented on GitHub (Oct 30, 2022): Perfect, works with new Version of Git! 2.38
claunia commented 2026-01-31 05:20:38 +00:00
Author
Owner
Copy Link

@Eugene-Melbourne commented on GitHub (Nov 6, 2022):

It really depends on the SSH connection. For example

The latest one (gitbash v2.38.1) is working fine with SSH connections to AWS EC2 instances.

But it does not work with Vagrant (Oracle VM).
To work with Vagrant (Oracle VM) the working options would be

@Eugene-Melbourne commented on GitHub (Nov 6, 2022): It really depends on the SSH connection. For example The latest one (gitbash v2.38.1) is working fine with SSH connections to AWS EC2 instances. But it does not work with Vagrant (Oracle VM). To work with Vagrant (Oracle VM) the working options would be - [`gitbash v2.32.0.windows`](https://github.com/git-for-windows/git/releases/tag/v2.32.0.windows.1) - [`gitbash v2.34.1.windows`](https://github.com/git-for-windows/git/releases/tag/v2.34.1.windows.1) - Windows PowerShell
claunia commented 2026-01-31 05:20:39 +00:00
Author
Owner
Copy Link

@matthiasbannach commented on GitHub (Nov 11, 2022):

For me it happen when I have X-Forwarding enabled (e.g. -Y or -X) or the equivalent setting in .ssh/config.

Without it - no problems.

@matthiasbannach commented on GitHub (Nov 11, 2022): For me it happen when I have X-Forwarding enabled (e.g. -Y or -X) or the equivalent setting in .ssh/config. Without it - no problems.
claunia commented 2026-01-31 05:20:39 +00:00
Author
Owner
Copy Link

@zehawki commented on GitHub (Dec 2, 2022):

This issue made Windows terminal quite useless for me, and I always thought this was a Win Term issue. This thread made me realise that the culprit could be git bash. Problem seems to have gone away for SSH to AWS EC2 (my usecase) with gitbash v2.38.1.

@zehawki commented on GitHub (Dec 2, 2022): This issue made Windows terminal quite useless for me, and I always thought this was a Win Term issue. This thread made me realise that the culprit could be git bash. Problem seems to have gone away for SSH to AWS EC2 (my usecase) with gitbash v2.38.1.
claunia commented 2026-01-31 05:20:39 +00:00
Author
Owner
Copy Link

@sanviler commented on GitHub (Dec 29, 2022):

still happening in version 2.39.0.windows.1 using vagrant

@sanviler commented on GitHub (Dec 29, 2022): still happening in version 2.39.0.windows.1 using vagrant
claunia commented 2026-01-31 05:20:39 +00:00
Author
Owner
Copy Link

@robert-lill-tie commented on GitHub (Jan 10, 2023):

Had the same issue with 2.35.0, updated to 2.39.0(2), now it's working fine.

@robert-lill-tie commented on GitHub (Jan 10, 2023): Had the same issue with 2.35.0, updated to 2.39.0(2), now it's working fine.
claunia commented 2026-01-31 05:20:39 +00:00
Author
Owner
Copy Link

@karmendra commented on GitHub (Jan 13, 2023):

I had new installation of windows 10 and updated it. Installed git version 2.39.0.windows.2 and it is not working as expected Ctrl+C exits me out of the ssh session and returns to git-bash prompt. vagrant is running the guest machine on virtualbox in my case.

@karmendra commented on GitHub (Jan 13, 2023): I had new installation of windows 10 and updated it. Installed `git version 2.39.0.windows.2` and it is not working as expected Ctrl+C exits me out of the ssh session and returns to git-bash prompt. vagrant is running the guest machine on virtualbox in my case.
claunia commented 2026-01-31 05:20:39 +00:00
Author
Owner
Copy Link

@rai-streamline commented on GitHub (Feb 3, 2023):

2.39.1 still happening

@rai-streamline commented on GitHub (Feb 3, 2023): 2.39.1 still happening
claunia commented 2026-01-31 05:20:40 +00:00
Author
Owner
Copy Link

@yuvaramachandran-gurusamy commented on GitHub (Feb 3, 2023):

This issue still observed in Git-2.39.0.

@yuvaramachandran-gurusamy commented on GitHub (Feb 3, 2023): This issue still observed in Git-2.39.0.
claunia commented 2026-01-31 05:20:40 +00:00
Author
Owner
Copy Link

@milkpirate commented on GitHub (Feb 26, 2023):

Dito, really annoying! 😭

@milkpirate commented on GitHub (Feb 26, 2023): Dito, really annoying! 😭
claunia commented 2026-01-31 05:20:40 +00:00
Author
Owner
Copy Link

@blakeduffey commented on GitHub (Apr 28, 2023):

This still seem to be an issue on git 2.40.0, OpenSSH_9.2.p1

This also happens with these versions of git/OpenSSH using a vanilla powershell window. after connecting via ssh, issuing a CTRL-C (which is muscle memory to end interrupt the remote task) results in

client_loop: send disconnect: Broken pipe

@blakeduffey commented on GitHub (Apr 28, 2023): This still seem to be an issue on git 2.40.0, OpenSSH_9.2.p1 This also happens with these versions of git/OpenSSH using a vanilla powershell window. after connecting via ssh, issuing a CTRL-C (which is muscle memory to end interrupt the remote task) results in **client_loop: send disconnect: Broken pipe**
claunia commented 2026-01-31 05:20:40 +00:00
Author
Owner
Copy Link

@xiaolitongxue666 commented on GitHub (May 11, 2023):

git --version
git version 2.39.2.windows.1
still have this problem

@xiaolitongxue666 commented on GitHub (May 11, 2023): git --version git version 2.39.2.windows.1 still have this problem
claunia commented 2026-01-31 05:20:40 +00:00
Author
Owner
Copy Link

@blakeduffey commented on GitHub (May 11, 2023):

OpenSSH_for_Windows_9.2p1, LibreSSL 3.7.2 does NOT have this problem

The ssh client bundled with git does

To work around it I installed OpenSSH Beta Microsoft.OpenSSH.Beta 9.2.2.0 and updated the path to prefer that version.

@blakeduffey commented on GitHub (May 11, 2023): OpenSSH_for_Windows_9.2p1, LibreSSL 3.7.2 does NOT have this problem The ssh client bundled with git does To work around it I installed OpenSSH Beta Microsoft.OpenSSH.Beta 9.2.2.0 and updated the path to prefer that version.
claunia commented 2026-01-31 05:20:41 +00:00
Author
Owner
Copy Link

@karmendra commented on GitHub (May 11, 2023):

@blakeduffey Please share more details like, where did you download the OpenSSH Beta Microsoft.OpenSSH.Beta 9.2.2.0 for windows 10 host and what file you updated the path to prefer that version. Thanks.

@karmendra commented on GitHub (May 11, 2023): @blakeduffey Please share more details like, where did you download the OpenSSH Beta Microsoft.OpenSSH.Beta 9.2.2.0 for windows 10 host and what file you updated the path to prefer that version. Thanks.
claunia commented 2026-01-31 05:20:41 +00:00
Author
Owner
Copy Link

@blakeduffey commented on GitHub (May 12, 2023):

The OpenSSH Beta 9.2.2.0 is available via winget (which just pulls it off github)

winget install Microsoft.OpenSSH.Beta

Since this default install requires admin (it installs the server component as well) - I use this instead:

msiexec /a https://github.com/PowerShell/Win32-OpenSSH/releases/download/v9.2.2.0p1-Beta/OpenSSH-Win64-v9.2.2.0.msi /qb TARGETDIR="$env:LOCALAPPDATA\Programs\OpenSSH"

This will extract the zip into a user profile directory in $env:LOCALAPPDATA

I generally add that path to the USERS path

[Environment]::SetEnvironmentVariable("PATH", $Env:PATH + ";$env:LOCALAPPDATA\Programs\OpenSSH\program files\openssh", [EnvironmentVariableTarget]::User)

That way this version can be invoked from any directory.

If you restart Terminal, you should be able to issue

ssh -V

and get OpenSSH_for_Windows_9.2p1, LibreSSL 3.7.2

If I ssh to a remote linux system, run top, and issue CTRL-C - I get the linux prompt back (it doesn't terminate the ssh session)
I've also tested this with the -Y flag.

-B

@blakeduffey commented on GitHub (May 12, 2023): The OpenSSH Beta 9.2.2.0 is available via winget (which just pulls it off github) winget install Microsoft.OpenSSH.Beta Since this default install requires admin (it installs the server component as well) - I use this instead: `msiexec /a https://github.com/PowerShell/Win32-OpenSSH/releases/download/v9.2.2.0p1-Beta/OpenSSH-Win64-v9.2.2.0.msi /qb TARGETDIR="$env:LOCALAPPDATA\Programs\OpenSSH"` This will extract the zip into a user profile directory in $env:LOCALAPPDATA I generally add that path to the USERS path `[Environment]::SetEnvironmentVariable("PATH", $Env:PATH + ";$env:LOCALAPPDATA\Programs\OpenSSH\program files\openssh", [EnvironmentVariableTarget]::User)` That way this version can be invoked from any directory. If you restart Terminal, you should be able to issue `ssh -V` and get **OpenSSH_for_Windows_9.2p1, LibreSSL 3.7.2** If I ssh to a remote linux system, run top, and issue CTRL-C - I get the linux prompt back (it doesn't terminate the ssh session) I've also tested this with the -Y flag. -B
claunia commented 2026-01-31 05:20:41 +00:00
Author
Owner
Copy Link

@blakeduffey commented on GitHub (Jun 2, 2023):

So to followup on this...

The version of OpenSSH included with git 2.41 reports as:
OpenSSH_9.3p1, OpenSSL 1.1.1u 30 May 2023

The version of OpenSSH available from https://github.com/PowerShell/Win32-OpenSSH/releases reports as:
OpenSSH_for_Windows_9.2p1, LibreSSL 3.7.2

If I connect to server X with the first client, run top, and issue CTRL-C - I get
client_loop: send disconnect: Broken pipe

if I connect to server X with the second client, run top, and issue CTRL-C...
it ends top and the connection remains

Both of these are the latest version available. Obviously this isn't an issue with Terminal - but rather a certain version of the OpenSSH client.

@blakeduffey commented on GitHub (Jun 2, 2023): So to followup on this... The version of OpenSSH included with git 2.41 reports as: **OpenSSH_9.3p1, OpenSSL 1.1.1u 30 May 2023** The version of OpenSSH available from https://github.com/PowerShell/Win32-OpenSSH/releases reports as: **OpenSSH_for_Windows_9.2p1, LibreSSL 3.7.2** If I connect to server X with the first client, run top, and issue CTRL-C - I get **client_loop: send disconnect: Broken pipe** if I connect to server X with the second client, run top, and issue CTRL-C... it ends top and the connection remains Both of these are the latest version available. Obviously this isn't an issue with Terminal - but rather a certain version of the OpenSSH client.
claunia commented 2026-01-31 05:20:41 +00:00
Author
Owner
Copy Link

@hkodavid commented on GitHub (Jul 3, 2023):

After a year of suffering, I have a solution.

Reinstall it with "Use external OpenSSH" option.

@hkodavid commented on GitHub (Jul 3, 2023): After a year of suffering, I have a solution. Reinstall it with "Use external OpenSSH" option.
claunia commented 2026-01-31 05:20:42 +00:00
Author
Owner
Copy Link

@kennyhyun commented on GitHub (Jul 18, 2023):

I was mainly using cmd instead of Gitbash when I use ssh

But I haven't had this symptom for a while even in Gitbash.

Using 1.16.10261.0 and git version 2.39.2.windows.1 BTW

I found today,

vagrant ssh

^c killed the session ONLY in Gitbash

It didn't happen when

/usr/bin/ssh -F ssh.config default

or

/c/Windows/System32/OpenSSH/ssh.exe -F ssh.config default

where ssh.config was generated by

vagrant ssh-config > ssh.config

It's weird but I think it's happening only in limited situation.

so, to workaround would be either

  • set ~/.ssh/config and use plain ssh command instead of using vagrant ssh command or
  • install git with "Use external OpenSSH"

BTW, for external OpenSSH, can we also use /c/Windows/System32/OpenSSH/ssh.exe? I think that's the ssh used in cmd

@kennyhyun commented on GitHub (Jul 18, 2023): I was mainly using `cmd` instead of Gitbash when I use `ssh` But I haven't had this symptom for a while even in Gitbash. Using `1.16.10261.0` and git version `2.39.2.windows.1` BTW I found today, ``` vagrant ssh ``` `^c` killed the session ONLY in Gitbash It didn't happen when ``` /usr/bin/ssh -F ssh.config default ``` or ``` /c/Windows/System32/OpenSSH/ssh.exe -F ssh.config default ``` where `ssh.config` was generated by ``` vagrant ssh-config > ssh.config ``` It's weird but I think it's happening only in limited situation. so, to workaround would be either - set ~/.ssh/config and use plain ssh command instead of using `vagrant ssh` command or - install git with "Use external OpenSSH" ~~BTW, for external OpenSSH, can we also use `/c/Windows/System32/OpenSSH/ssh.exe`? I think that's the ssh used in cmd~~
claunia commented 2026-01-31 05:20:42 +00:00
Author
Owner
Copy Link

@poshest commented on GitHub (Aug 24, 2023):

I have Windows 10 22H2 as a host, Rocky Linux as a guest, with Vagrant version 2.3.7 + VirtualBox. The use case is issuing a vagrant up and vagrant ssh using the git bash, and then hitting Ctrl + C.

When I install Git for windows 2.42.0.windows.1: Not working, closes terminal. Reverting to 2.35.1.windows.2 fixes it.

I assume the difference is that for 2.42, I had to choose OpenSSL during setup (bundled OpenSSH not available)

image

whereas for 2.35 I had the option of OpenSSH and chose that

image

@poshest commented on GitHub (Aug 24, 2023): I have Windows 10 22H2 as a host, Rocky Linux as a guest, with Vagrant version 2.3.7 + VirtualBox. The use case is issuing a vagrant up and vagrant ssh using the git bash, and then hitting Ctrl + C. When I install Git for windows 2.42.0.windows.1: Not working, closes terminal. Reverting to 2.35.1.windows.2 fixes it. I assume the difference is that for 2.42, I had to choose OpenSSL during setup (bundled OpenSSH not available) ![image](https://github.com/microsoft/terminal/assets/6979221/d2360591-f06b-4739-99b5-a02340ac0547) whereas for 2.35 I had the option of OpenSSH and chose that ![image](https://github.com/microsoft/terminal/assets/6979221/469e903b-7cad-41ee-be82-d96edabd4f52)
claunia commented 2026-01-31 05:20:42 +00:00
Author
Owner
Copy Link

@blank71 commented on GitHub (Nov 14, 2023):

Thanks. It is solved with reinstall with the option enabling Use external OpenSSH. If you want to use newer OpenSSH, you can use winget to install it. The Path is automatically added to the top of system environment variable.

# after adding `Use external OpenSSH`
$ ssh -V
OpenSSH_for_Windows_8.6p1, LibreSSL 3.4.3

$ /c/Windows/System32/OpenSSH/ssh -V
OpenSSH_for_Windows_8.6p1, LibreSSL 3.4.3

# if you want newer OpenSSH, winget is one of options
$ winget install Microsoft.OpenSSH.Beta

# after winget install, the path change
$ ssh -V
OpenSSH_for_Windows_9.4p1, LibreSSL 3.7.3

$ /c/Program\ Files/OpenSSH/ssh -V
OpenSSH_for_Windows_9.4p1, LibreSSL 3.7.3

$ which ssh
/c/Program Files/OpenSSH/ssh
@blank71 commented on GitHub (Nov 14, 2023): Thanks. It is solved with reinstall with the option enabling `Use external OpenSSH`. If you want to use newer `OpenSSH`, you can use `winget` to install it. The Path is automatically added to the top of system environment variable. ``` # after adding `Use external OpenSSH` $ ssh -V OpenSSH_for_Windows_8.6p1, LibreSSL 3.4.3 $ /c/Windows/System32/OpenSSH/ssh -V OpenSSH_for_Windows_8.6p1, LibreSSL 3.4.3 ``` ``` # if you want newer OpenSSH, winget is one of options $ winget install Microsoft.OpenSSH.Beta ``` ``` # after winget install, the path change $ ssh -V OpenSSH_for_Windows_9.4p1, LibreSSL 3.7.3 $ /c/Program\ Files/OpenSSH/ssh -V OpenSSH_for_Windows_9.4p1, LibreSSL 3.7.3 $ which ssh /c/Program Files/OpenSSH/ssh ```
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-Author-Feedback Needs-Tag-Fix Needs-Triage 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#16716
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?