Windows Server · 2022 · Release · Security update (Patch Tuesday)

January 14, 2025—KB5049983 (OS Build 20348.3091)

Windows Server 2022: Supported LTSC release

Microsoft's known issues — KB5049983

  • Issue Known issue Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process.This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro editions of Windows are affected. Workaround: This issue is addressed in KB5053603 .
  • Issue Known issue Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update. This issue was observed on devices with Citrix Session Recording Agent (SRA) version 2411. The 2411 version of this application was released in December 2024. Affected devices might initially download and apply the January 2025 Windows security update correctly, such as via the Windows Update page in Settings. However, when restarting the device to complete the update installation, an error message with text similar to “Something didn’t go as planned. No need to worry – undoing changes” appears. The device will then revert to the Windows updates previous Workaround: The issue has been resolved in Citrix Session Recording Agent version 2503, released on April 28, 2025, and newer versions.For details, see the documentation provided by Citrix at " Microsoft's January Security Update Fails/Reverts on a machine with 2411 Session Recording Agent ".
  • Issue Known issue The Windows Event Viewer might display an error related to SgrmBroker.exe, on devices that have installed Windows updates released January 14, 2025, or later. This error can be found under Windows Logs > System as Event 7023, with text similar to ‘The System Guard Runtime Monitor Broker service terminated with the following error: %%3489660935’.This error is only observable if the Windows Event Viewer is monitored closely. It is otherwise silent and does not appear as a dialog box or notification.SgrmBroker.exe refers to the System Guard Runtime Monitor Broker Service. This service was originally created for Microsoft Defender, but it has not been a part of its operation for a very long time Workaround: This issue is addressed in KB5055526 .
  • Issue Known issue After installing this security update, you might experience issues with USB audio devices. You are more likely to experience this issue if you are using a USB 1.0 audio driver based DAC (Digital to Analog converter) in your audio setup. This issue might cause USB audio devices to stop working, preventing audio playback.DACs (Digital-to-Analog Converters) are commonly used in scenarios where users need to improve the quality of their audio systems. A few scenarios where they are used are home audio systems, professional music studios and portable music players.Resulting from this issue, the Device Manager might display the error ‘This device cannot start. (Code 10) Insufficient system resourc Workaround: This issue is addressed in KB5051979 .

Microsoft's release notes for KB5049983 ›

Known issues — reported on the forum

No problems reported on the forum for this build yet. Threads that name 20348.3091 or KB5049983 and describe a fault appear here automatically.

In the news

Discussed on the forum

Search the forum for 20348.3091 Ask about this build