How to Close SSH on Windows

To close an SSH session on Windows, the most common and graceful method is to type exit and press Enter. However, several other commands and keyboard shortcuts can be used depending on the situation, especially if the session becomes unresponsive.

Common Methods to Terminate an SSH Session

Closing an SSH connection can involve ending the remote shell session or directly terminating the local SSH client.

Using the exit Command

The most straightforward way to close an SSH session is by gracefully logging out of the remote server.

• Action: Type exit and press Enter.
• Explanation: This command tells the remote shell to terminate, which in turn closes the SSH connection. This is the preferred method when your remote session is active and responsive.

Keyboard Shortcuts

Several keyboard shortcuts can terminate processes or signals within the terminal, which can also close an SSH session.

Ctrl + D (End-of-File)

• Action: Press Ctrl + D.
• Explanation: In Unix-like environments, Ctrl + D sends an End-of-File (EOF) signal. If no process is running in the foreground, this signal often causes the shell to exit, thus closing the SSH connection. This is a common and usually graceful way to log out.

Ctrl + C (Interrupt)

• Action: Press Ctrl + C.
• Explanation: This shortcut sends an interrupt signal (SIGINT) to the foreground process. If your SSH session is simply waiting for input or has a simple command running, Ctrl + C might terminate that command. If there are no other processes to return to, it can sometimes close the shell and the SSH connection.

Ctrl + \ (Quit)

• Action: Press Ctrl + \.
• Explanation: This sends a SIGQUIT signal, which is similar to Ctrl + C but typically causes the process to terminate and dump a core file. It's a more forceful way to stop a process and can also lead to the SSH session closing if it's the only active process.

SSH Escape Sequences (Tilde ~)

When the remote server becomes unresponsive or the connection seems to be hung, SSH escape sequences provide a way to control the local SSH client directly. These sequences are activated by pressing Enter, then ~, followed by another character.

Standard Escape Sequence: ~. (Force Close)

• Action: Press Enter, then ~, then ..
• Explanation: This sequence tells the local SSH client to immediately terminate the connection, regardless of the remote server's state. It's particularly useful when the remote end hangs and exit or Ctrl+D don't work.

Backgrounding SSH: ~Ctrl+Z

• Action: Press Enter, then ~, then Ctrl+Z.
• Explanation: This suspends the SSH client process locally, returning you to your local Windows command prompt or PowerShell. The connection to the remote server remains open but is paused in the background. You can bring it back to the foreground later using fg (if your local shell supports job control) or kill the suspended process.

Sending a SIGTERM to SSH: ~&

• Action: Press Enter, then ~, then &.
• Explanation: This sends a SIGTERM signal to the local SSH client process, requesting it to shut down gracefully. It's another way to terminate a hung session, offering a slightly gentler approach than ~..

Handling Dead Keys (e.g., ~ with a Space)

• Action: For some keyboard layouts (especially non-US layouts), the tilde ~ is a "dead key." This means you might need to type ~ followed by a space for the character to register before typing the subsequent escape character.
• Example: Enter, then ~, then Space, then ..

Quick Reference for Closing SSH Sessions

Here's a summary of the methods to close an SSH connection on Windows:

Method	Description	When to Use
exit	Gracefully logs out of the remote shell.	Normal termination when the remote session is responsive.
Ctrl + D	Sends End-of-File signal; often logs out.	Common, often graceful, for responsive sessions.
~.	Forcefully terminates the SSH connection locally.	Remote session is hung, unresponsive, or exit doesn't work.
~Ctrl+Z	Suspends the SSH client process locally.	To temporarily pause the session and return to your local shell.
~&	Sends a SIGTERM to the local SSH client.	To gracefully terminate a hung session without disconnecting abruptly.
Ctrl + C	Interrupts the foreground process.	To stop a running command; may sometimes close the session if nothing else is active.
Ctrl + \	Sends a Quit signal to the foreground process.	More forceful termination; similar to Ctrl+C but with core dump potential.
~ + Space + .	For keyboard layouts where ~ is a dead key.	When the ~ escape sequence doesn't register directly.

Practical Insights and Troubleshooting

• Local Client vs. Remote Shell: Remember that commands like exit and Ctrl+D primarily interact with the remote shell. Escape sequences (~., ~Ctrl+Z, ~&) interact with the local SSH client running on your Windows machine.
• Unresponsive Sessions: When the remote server becomes unresponsive, or the network connection drops, the SSH client might not immediately recognize the disconnection. In such cases, ~. is the most reliable way to regain control of your local terminal.
• Task Manager: If all else fails and the SSH window is completely frozen, you can always close the terminal application (e.g., PowerShell, Command Prompt, or PuTTY) using the Windows Task Manager. Select the application and click "End task."

Understanding these different methods provides flexibility in managing your SSH connections, ensuring you can gracefully log out or forcefully disconnect when necessary.