Introduction

In October 2024, Microsoft released security updates KB5044285 and KB5044380 for Windows 11 versions 22H2 and 23H2. Shortly after, users began reporting issues with SSH (Secure Shell) connections, a critical tool for secure remote access and system management. This article delves into the nature of the problem, Microsoft's response, and the available solutions.

Understanding the SSH Connectivity Issue

The Problem

Post-installation of the October 2024 updates, the OpenSSH service on affected Windows 11 systems failed to start, preventing SSH connections. Notably:

  • Lack of Detailed Logs: The service failure did not generate detailed logs, complicating troubleshooting efforts.
  • Manual Intervention Required: Administrators had to manually start the INLINECODE0 process to restore functionality.

This issue primarily impacted enterprise, IoT, and education editions of Windows 11, with Microsoft investigating potential effects on Home and Pro editions.

Root Cause

The problem was traced to incorrect Access Control List (ACL) permissions on the INLINECODE1 directory and its subfolder INLINECODE2 . These misconfigurations prevented the SSH service from accessing necessary files, leading to startup failures.

Microsoft's Response

Insider Patch Release

On February 20, 2025, Microsoft rolled out Windows 11 Build 26100.3321 in the Release Preview Channel, targeting the SSH connectivity issue by addressing the ACL misconfigurations. This insider patch aimed to restore normal SSH functionality.

Temporary Workaround

Until the patch became widely available, Microsoft recommended a manual adjustment of ACL permissions as a temporary solution. The steps involved:

  1. Open PowerShell as Administrator: Ensure administrative privileges.
  2. Update Permissions:
  • For INLINECODE3 :

``INLINECODE4 `INLINECODE5 C:\ProgramData\ssh\logs`.

This script grants full control to SYSTEM and Administrators, while allowing read access to Authenticated Users.

Broader Implications

Impact on Users

For system administrators and organizations relying on SSH for remote management, this issue posed significant challenges:

  • Operational Disruptions: Inability to establish SSH connections hindered remote operations.
  • Security Concerns: Manual interventions increased the risk of misconfigurations and potential security vulnerabilities.

Lessons Learned

This incident underscores the delicate balance between implementing security updates and maintaining system functionality. It highlights the importance of:

  • Thorough Testing: Ensuring updates are tested in diverse environments to identify potential issues.
  • Clear Communication: Promptly informing users about known issues and providing effective workarounds.

Conclusion

Microsoft's proactive approach in addressing the SSH connectivity issue through an insider patch and providing a temporary workaround reflects its commitment to user experience and system security. Users are encouraged to apply the patch once available and utilize the workaround in the interim to maintain secure and efficient remote access.