大网数据广告活动
Windows Server 管理

Error 1053, Error 1067, or Event ID 7034 and OpenSSH Server Service Doesn't Start After You Install a Windows Update

· 52CE 我爱测

Explains how to resolve an issue that prevents the OpenSSH Server service from starting after you install specific Windows updates.

This article explains how to resolve an issue in which the OpenSSH Server service doesn't start after you update Windows.

Symptoms

After you install a Windows update for OpenSSH Version 9.5.2.1, the OpenSSH Server service doesn't start. This problem typically involves updates that were released between October 8, 2024, and March 11, 2025 (inclusive). The following updates might relate to this problem:

For a list of all operating system versions that received the updated version of OpenSSH, see the "Security Updates" section of CVE-2024-43581: Microsoft OpenSSH for Windows Remote Code Execution Vulnerability.

The exact behavior and messages vary based on your situation. The following scenarios show how the failure might occur, and the message that you see in each case:

  • Scenario 1. The System event log records Service Control Manager Event ID 7034:

    The openSSH SSH Server terminated unexpectedly. It has done this X time(s).

  • Scenario 2. OpenSSH 9.5 doesn't start, and you receive the following error message:

    Service 'OpenSSH SSH Server' (sshd) failed to start. Verify that you have sufficient privileges to start system services.

  • Scenario 3. You try to manually start the OpenSSH 9.5 Server service by using the Services MMC (Microsoft Management Console) snap-in (Services.msc). The service doesn't start, and you receive the following error message:

    Windows could not start the OpenSSH SSH Server service on Local computer. Error 1067. The process terminated unexpectedly.

  • Scenario 4. You try to manually start the OpenSSH 9.5 Server service by running sc query ssh-agent at a Windows command prompt. The service doesn't start, and you receive the following error message:

    StartService FAILED 1053: The service did not respond to the start or control request in a timely fashion.

Cause

This issue occurs if the C:\ProgramData\ssh and C:\ProgramData\ssh\logs folders have incorrect permissions. The permissions might be too limited or too open. For example, the SYSTEM account or the Administrators group might not have write permissions. For a second example, regular users might have write or full control permissions.

You can use Windows PowerShell to review the permissions in the current access control list (ACL) configuration. Open a PowerShell Command Prompt window, and then run the following commands:

Get-Acl C:\ProgramData | Select-Object -Property AccessToString | fl *
Get-Acl C:\ProgramData\ssh | Select-Object -Property AccessToString | fl *
Get-Acl C:\ProgramData\ssh\logs | Select-Object -Property AccessToString | fl *
Get-Acl "C:\ProgramData\ssh\sshd_config" | Select-Object -Property AccessToString | fl *

Resolution

On devices that this issue affects, start File Explorer, and then open the Properties dialog boxes for each of the ssh folders (C:\ProgramData\ssh and C:\ProgramData\ssh\logs). In each dialog box, select Security, and set the permissions that are shown in the following table.

Allowed permissions on SYSTEM and Administrators security principals Allowed permissions on all other security principals
Group: Administrators Permissions: Full control, Modify, Read & execute, List folder contents, Read, Write Group: Authenticated Users Permissions: Read & execute, List folder contents, Read
:::image type="content" source="media/error-1053-1067-7034-after-update-openssh-doesnt-start/openssh-administrative-permissions.png" alt-text="Windows permissions dialog box that shows full control access for SYSTEM and Administrators accounts." lightbox="./media/error-1053-1067-7034-after-update-openssh-doesnt-start/openssh-administrative-permissions.png"::: :::image type="content" source="media/error-1053-1067-7034-after-update-openssh-doesnt-start/openssh-nonadministrative-permissions.png" alt-text="Windows permissions dialog box that shows read and execute permissions on non-administrator accounts." lightbox="./media/error-1053-1067-7034-after-update-openssh-doesnt-start/openssh-nonadministrative-permissions.png":::

Workaround

Install updates that allow the service to start if the permissions aren't correct.

Install Windows updates that allow the OpenSSH service to start even if the C:\ProgramData\ssh and C:\ProgramData\ssh\logs folders don't have correct permissions. When you use this workaround, Windows logs Event ID 4. The description of Event ID 4 resembles the following excerpt:

For '%programdata\ssh' folder, write access is granted to the following users: NT AUTHORITY\Authenticated Users. Consider reviewing users to ensure that only NT AUTHORITY\SYSTEM, and the BUILTIN\Administrators group and its members have write access.

Note:

  • This message provides information only.
  • The list of users in this message might include users that belong to the local Administrators group. These users have valid reasons for having permissions on the C:\ProgramData\ssh folder.
  • The list of security principals that follows "granted to the following users:" (in the preceding example, "NT AUTHORITY\Authenticated User) changes based on the actual folder permissions.

Updates that fix the problem as described in this method include updates that were released on and after March 11, 2025. This update list includes the following Windows versions:

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
- ✅ Supported versions of Windows Server - ✅ Supported versions of Windows Client · Source date 02/12/2026
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。