issues with openssh service after win10 update

Anonymous
2024-10-11T07:28:42+00:00

Hello.

I've been using OpenSSH server on Win10 for a long time.

But recently I've noticed that after update (which was installed circa 10 of october 2024) OpenSSH service stopped working. Service is stopped and I can't start it.

Does anyone know what could be the cause of the problem?

I've noticed that issue on 2 workstations so far.

Greetz.

Windows 10 Pro

19045.5011

*** Moved from Windows / Windows 10 / Windows update, recovery, and backup ***

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes
Accepted answer
  1. Anonymous
    2024-10-14T15:31:00+00:00

    We were able to fix some of our servers by modifying the permissions of the Logs directory in c:\programdata\ssh. Remove everyone except SYSTEM and the administrators group. Service started after that.

    13 people found this answer helpful.
    0 comments No comments

6 additional answers

Sort by: Most helpful
  1. Anonymous
    2024-10-14T16:31:35+00:00

    We were able to fix some of our servers by modifying the permissions of the Logs directory in c:\programdata\ssh. Remove everyone except SYSTEM and the administrators group. Service started after that.

    Been trying many other fixes - this one finally pushed it over the top. Thanks!

    0 comments No comments
  2. Anonymous
    2024-10-14T17:17:02+00:00

    Hello,

    Thank you for posting in the Microsoft community forum.

    According to my research, Microsoft has not released known issues and fixes for the OpenSSH service regarding updates to OS Builds 19044.5011 and 19045.5011, which were released on 10/8/2024.

    It is advised to perform the following steps to repair the OpenSSH service and install the patch after it is released.

    1. Check the permission Settings of the OpenSSH folder.

    The main configuration folder is usually located in C:\programdata\ssh

    Ensure that the SYSTEM and Administrators groups have full control over this folder.

    1. Check the OpenSSH service status.

    Press Win + R to open the Run dialog box.

    Enter 'services.msc' and press Enter.

    Look for 'OpenSSH Authentication Agent' and 'OpenSSH Server' in the service list. Configure the startup type to automatic.

    1. Reinstall the OpenSSH component.

    Open Settings (press Win + I).

    Go to System > Optional features.

    Find "OpenSSH Client" and "OpenSSH Server" in the list, and uninstall them.

    After uninstalling, click Add Feature and reinstall OpenSSH Client and OpenSSH Server to add them again.

    Reference:

    OpenSSH Server configuration for Windows | Microsoft Learn

    I hope this helps.

    Best regards

    Jacen

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-11-05T19:33:46+00:00

    We were able to fix some of our servers by modifying the permissions of the Logs directory in c:\programdata\ssh. Remove everyone except SYSTEM and the administrators group. Service started after that.

    Seriously hero status on this reply. Thank you. Fixed our issue too.

    0 comments No comments
  4. Anonymous
    2024-11-13T09:33:42+00:00

    The root cause of this may be the incorrect permission settings on C:\ProgramData\ssh\log folder.

    In my case, I removed "Authenticated Users" from C:\ProgramData\ssh, but still not working.

    After tried many times, I uninstalled OpenSSH and renamed C:\ProgramData\ssh to ssh2.

    Then OpenSSH gets to work again after reinstallation.

    I have inspected the C:\ProgramData\ssh generated by reinstallation.

    There is no change in permission settings on ssh itself, but the ssh\log folder needs Adinistrator permissions to access which is not needed before reinstallation.

    Bill

    0 comments No comments