Microsoft Adding a Built-in OpenSSH Client to Windows 10

Posted on December 14, 2017 by Mehedi Hassan in Windows, Windows 10 with 27 Comments

Windows 10 is soon getting a built-in OpenSSH client. Microsoft has quietly started testing a built-in OpenSSH client for Windows 10, reports TechCrunch.

The built-in OpenSSH client in Windows 10 is available as an optional feature to users on the latest version of the Fall Creators Update, also known as Windows 10 Version 1709. Once you download and install the OpenSSH client using the settings app in Windows 10, you will be able to use SSH from an elevated CMD or PowerShell. Microsoft adding a built-in OpenSSH client to Windows 10 is obviously a big step forward for the OS, as users were required to use software like PuTTY to connect to SSH servers for years.

Of course, users using the Windows Subsystem for Linux have already been able to use SSH in Windows 10, but the addition of the built-in OpenSSH client right in Windows 10 will be a welcome addition for those who don’t need all the features that come with the entire Windows Subsystem for Linux.

Installing the OpenSSH client in Windows 10 isn’t too much of a hard task – all you need to do is head over to Apps > Manage optional features > Add a feature in the Settings app, scroll down the page and look for the OpenSSH Client or Server, and hit install. Once installed, just open up an elevated terminal and `ssh` will be ready for you to use.

Tagged with , , ,

Join the discussion!


Don't have a login but want to join the conversation? Become a Thurrott Premium or Basic User to participate

Comments (27)

27 responses to “Microsoft Adding a Built-in OpenSSH Client to Windows 10”

  1. Tony Barrett

    Mmm. Think I'll stick with PuTTy.

  2. snapch23

    We have been all looking to get the recycle bin windows 10 here.

  3. Locust Infested Orchard Inc.

    It jolly well about time a command line SSH client came bundled as standard with Windows. This should have happened with the release of Windows 2000 Professional.

    Many have used and loved PuTTy, but I personally have used SecureCRT from VanDyke, along with their other product offerings.

    Better late than never, I guess ‽

    • hrlngrv

      In reply to Locust Infested Orchard Inc.:

      I figure most people who'd want/need to use an ssh client on a Windows machine were either using PuTTY or alternatives or cygwin's or MSYS2's ssh clients or even the ssh client which the Windows version of git includes.

      This is no different than people needing, say, rectangular block marking and regular expressions in a plain text editor but not finding those features in Notepad. LOTS of 3rd party editors from which to choose. I figure MSFT doesn't need to bundle everything fewer than 1/4 of all Windows users would even know about and fewer than 1/10 use regularly.

  4. karlinhigh

    Way to go, Microsoft! I love it when new software versions are MORE capable, instead of removing functionality with the put-down, "it was more than most people needed."

  5. Ukghster

    Why would you need an elevated command prompt to run the ssh client?

    • jimchamplin

      In reply to Ukghster:

      Because designing the system to run using the standard user is so passé in ‘17.

      • hrlngrv

        In reply to jimchamplin:

        Good point. Let's return to Windows 95-like security.

        Actually, I had the same question. Looks like it's necessary the first time through to set up the ssh server and modify the config file under C:\Windows. Unclear whether elevation is needed to run the ssh client once the server is running.

  6. fishnet37222

    Is there a specific build of Windows you need to be running in order to see it in the available optional features? I don't see it when I go to install optional features.

  7. RamblingGeek

    I thought this was intresting when I made my own video last month, didn't think it was news worthly :-)

  8. snapch23

    so it is the recycle bin windows 10 here that can help us to get the trash folder in windows.