Since the Windows security updates Microsoft sent out on January 14, 2025, feedback has rolled in about a smattering of issues. Some systems can’t install the update while others don’t get it due to missing SSUs; still, others face problems after installation. Here’s a quick look at the issues I’ve noticed.

As per a comment on a German blog, a reader DS2 has pointed out that the update KB5049983 for Windows Server 2022 cannot be installed through any method—a script, manual installation via the GUI, or using an msu file downloaded from the update catalog. All three approaches lead to an installation failure with the error code 0x8007000d (ERROR_INVALID_DATA), which indicates invalid data was encountered, most probably due to a corrupted update package or a compromised system.

A thread titled Server 2022 Failing to Update exists on reddit.com, in which the OP discusses the error code 0x8024200B. Others are seeing error code 0x8007000d when installing updates for Windows Server 2022. In comments, people experiencing problems give hints at several possible causes, per CBS.log, that might be going wrong. Yet a clear cause or solution seems to elude them. Is there also anyone among the readers who is affected?

In the article "Windows 10/Server 2022: SgrmBroker service no longer starts after Jan. 2025 update (KB5049981)," I covered the installation issue regardingJanuary 2025 updates forWindows Server 2022 stemming from Citrix environments. A user in this German comment mentions getting the installation error on Windows 11 24H2 and immediately blames it on the installed Checkpoint Endpoint Security Client.

I have seen reports that the January 2025 update was not offered in managed environments. In every case, it turned out that the SSUs from prior months needed to be installed. It seems there has in͏to be a change in Windows where a missing (failed) SSU might not get installed automatically. So, if the January 2025 update is not available, check that the SSUs are installed and up-to-date.

In my German blog (see this comment) and elsewhere on the Internet, I’ve come across many problems that started right after installing the January 2025 updates for Windows. Here’s a summary of those issues.

Roblox is an online gaming platform that lets you create your own computer games and interact with others. As per the support article KB5050009 from Microsoft in the Known Issues section, there are issues related to Roblox on ARM platform devices. Windows users on ARM devices cannot download or play Roblox through the Microsoft Store. The solution for these players is to download Roblox directly from www.Roblox.com.

Beginning in October 2024, several users will likely face the issue concerning the initiation of the OpenSSH (Open Secure Shell) service. Consequently, SSH connections cannot be established.
Microsoft has confirmed the issue in a support article for KB5050009 in known issues. OpenSSH never runs properly without detailed logging; it requires manual intervention to get the sshd.exe process started.

Affected are customers with Windows Enterprise, Windows IOT, and Windows Education systems. However, it is said to involve only a tiny fraction of devices. Microsoft is still in the process of checking if private users with Windows Home or Pro editions are also affected.

Im Blog-Beitrag mit dem Titel Windows 10/Server 2022: Dienst SgrmBroker startet nach Jan. 2025-Update (KB5049981) wurde das Problem des nicht mehr startenden SgrmBroker-Dienstes nicht behandelt. Es scheint, als hätte dieser Fehler keine praktischen Auswirkungen, da Windows weiterhin einwandfrei funktioniert.
Ich bekam zwei Meldungen zu Problemen mit Bitlocker. Ein Benutzer äußerte seinen Unmut in einer privaten deutschen Nachricht auf Facebook und fragte, wieso rund um Patchday unverzüglich der Bitlocker-Wiederherstellungsschlüssel angefordert wird.

Particularly annoying: The Bitlocker recovery key is stored in the user's Microsoft account; this is common knowledge. However, when trying to log into the Microsoft account, the user receives the error message shown in the screenshot above. Thus, they cannot access their Microsoft account to get the key. But, after a few restarts, the problem with asking for the recovery key seems to be resolved.

A report from colleagues at Bleeping Computer indicates a bug in Windows that triggers BitLocker warnings on TPM-equipped devices. It cites a Microsoft support document that claims after enabling BitLocker, the message "For your security, some settings are managed by your administrator" appears unexpectedly. This condition gives users a notion that their BitLocker settings are under administrator control; however, most probably, this bug is not directly related to January 2024's patch day. Does it ring a bell for anyone?

Related articles

Microsoft Security Updates (January 14, 2025) - Summary

Windows 10/11 Patches - Update Day (January 14, 2025)

Windows Server Patches - Update Day (January 14, 2025)

Microsoft Office Patches - Update Day January 2025