When comparing PuTTY vs SSH of Windows' Linux subsystem, the Slant community recommends PuTTY for most people. In the question“What are the best SSH clients for Windows?” PuTTY is ranked 1st while SSH of Windows' Linux subsystem is ranked 4th. The most important reason people chose PuTTY is:
PuTTY is one of the oldest and most popular clients. It has earned the trust of a great number of users over a long period by being reliable, offering useful features and helpful support. It got into the [15 Essential Open Source Tools for Windows Admins list by InfoWorld](https://www.infoworld.com/article/2854954/microsoft-windows/15-essential-open-source-tools-for-windows-admins.html).
Ranked in these QuestionsQuestion Ranking
Pro De facto standard client for SSH, Telnet and Rlogin
PuTTY is one of the oldest and most popular clients. It has earned the trust of a great number of users over a long period by being reliable, offering useful features and helpful support. It got into the 15 Essential Open Source Tools for Windows Admins list by InfoWorld.
Pro Source code available
Full source available. Compile and modify it yourself.
Pro Lightweight and portable
Pro It's extremely easy to get running
All you have to do is go to the Microsoft store, choose a Linux distro you like, and install the client for free.
Pro Based on OpenSSH
OpenSSH is the reference for all ssh clients.
Pro Full Linux shell
Uses all relevant Linux ssh commands as normal.
Pro Excellent way for Windows users to learn Linux
It is much easier and more convenient than dealing with a dual boot Linux installation.
Con Lacks features
It is JUST an SSH client. There are many other options with built in X-servers, Multitabbing, etc.
Con Can not save passwords
Anyway, you can use "PuTTYgen" to generate a key pair, then use "Pageant" to do a password-less SSH remote login.
Con Ugly design, too simple
Con Tedious logging/tracing
Its tedious to set up logging and tracing (e.g. for serial connections).
Con No global settings
If you want to change a setting for all your connections, you'd have to do it individually.
Con No login scripting
Con Graphical problems
For example running Midnight commander (MC) makes terminal blinking.
Con Crontab and other background jobs don't work properly
Crontab only runs on ROOT, and it needs Windows to stay open. If you close it, you will kill the crontab. Some background jobs don't run on Windows WSL.
Con Does not install on PC virtual machines
Con Forces window to a certain size
Any other SSH client will render the remote server at whatever size the local client window is. The built-in SSH client on Windows, however, forces you to use a standard size, and it's small enough to cause problems.