Windows 10: OpenSSH server not available any more on latest version of Windows

Hi folks

If I'm using SSH from a remote system to access a Windows machine - seems the openssh server isn't available any more --only the client

This means I can't ssh files INTO a remote non windows system FROM a Windows machine. (It works the other way around --i.e Windows openssh is a CLIENT. I.e If I'm on a Linux NAS and I want files from Windows --no good -- if I want to send files from Windows to NAS OK.

I need the NAS system to send scripts etc to Windows for running automated backups etc --this was working perfectly until recent versions of W10.

I don't want to di it manually via SAMBA etc !!!

Anyway to install the server component any more. (This used to be in programs and applications -- optional features in the dropdown. Now only the client appears not the server).


This ius what I see now when trying to install.





I prefer using sftp for file xfers - things like filezilla etc can't connect any more with the Windows machine from Non Windows systems. I don't like using the network file browser in Windows or Samba for this stuff --dftp with encryption is nice, fast and secure.

Ms is always rabitting on about security -- why remove a nice safe secure file xfer system (SSH server).


Cheers
jimbo

:)

 

Having trouble getting the built-in OpenSSH server to work

Goal: I'm trying to set up the Windows built-in OpenSSH server (version 0.0.1.0, as I recall that being the latest one) in order to use my desktop PC remotely should I have the need for raw performance when on the road through a Windows
10 laptop.

Problem: Despite following
the official guide to the letter, when I try to run "Start-Service sshd" in PowerShell I get this error:

Code:

    Start-Service : Service 'OpenSSH SSH Server (sshd)' cannot be started due to the following error: Palvelun sshd avaamin    en tietokoneessa . epäonnistui.    At line:1 char:1    + Start-Service sshd    + ~~~~~~~~~~~~~~~~~~        + CategoryInfo          : OpenError: (System.ServiceProcess.ServiceController:ServiceController) [Start-Service],       ServiceCommandException        + FullyQualifiedErrorId : CouldNotStartService,Microsoft.PowerShell.Commands.StartServiceCommand

If I run the executable without "Start-Service", however, it runs and seemingly waits for connections, but according to the Services tab in Task Manager it's not actually doing anything at all, nor is there an SSH user account associated
with it.

What I've tried:

• Restarting Windows (after every installation)
• Uninstalling and re-installing both the server and the client (both from PowerShell and through the Settings application)
• Switched to local account instead of a Microsoft account (suggested on a forum thread, tried the previous steps again)
• Using an elevated PowerShell instance with admin rights

System information:

• Windows 10 Home, version 1809, build 17763.379
• Hardware configuration:
  • CPU: i9-9900k @ 4.9GHz
  • RAM: 32GB 3200MHz DDR4
  • GPU: Asus ROG Strix GTX 1080
  • Motherboard: Asus PRIME Z390-A, BIOS version 0805

Let me know if other information is required.

 

Windows Server 2019 Includes OpenSSH

Source: Windows Server 2019 Includes OpenSSH - Windows Developer Blog

 

Windows Server 2019 Includes OpenSSH

Source: Windows Server 2019 Includes OpenSSH - Windows Developer Blog