[German]After Microsoft released security updates for Windows on January 14, 2025, there is some feedback on problems. Some systems fail with an installation error, on other systems the update is not offered due to missing SSUs. And there are some problems after installation. Here is a brief summary of what I have encountered.
Advertising
Server 2022: Installation ends with error code 0x8007000d
In this German comment, blog reader DS2 has reported that the update KB5049983 for Windows Server 2022 cannot be installed either via script, manually via the GUI or via msu file (download from the update catalog). In all three variants, the installation aborts with the error code 0x8007000d (ERROR_INVALID_DATA, means that invalid data was found, which is due to a broken update package or a damaged system).
On reddit.com there is the thread Server 2022 Failing to Update, where the thread starter describes the error 0x8024200B. But there are also affected people who receive the error code 0x8007000d during the update installation under Windows Server 2022. There, those affected state various causes which, according to CBS.log, are causing the problem. There doesn't really seem to be a cause or a solution. Anyone from the readership affected?
I had prepared the installation problem with the January 2025 updates under Windows Server 2022 when using Citrix environments separately in the article Windows 10/Server 2022: SgrmBroker service no longer starts after Jan. 2025 update (KB5049981).
In this German comment a user reports the installation error 0x80070005 under Windows 11 24H2 and immediately provides an installed Checkpoint Endpoint Security Client as the reason.
Update is not offered without SSU
I have also come across some reports that the January 2025 update was not offered in managed environments. In all cases, it turned out that the SSUs from previous months had to be installed. There seems to be a change in Windows that a missing (failed) SSU may not be installed automatically. So if the January 2025 update is not offered, check whether the SSUs are installed and up-to-date.
Problems after update installation
In my German blog (see this comment) as well as on the Internet, I have come across some problems that occur after installing the January 2025 updates on Windows. Below is an overview of these issues.
Problems with Roblox on ARM
Roblox is an online gaming platform where users can create their own computer games and play them with other users. Microsoft has documented in the support article for KB5050009 in the Known Issues that it is known that there are problems with Roblox on the ARM platform. Players on Arm devices are unable to download and play Roblox on Windows via the Microsoft Store. The workaround is for players on ARM devices to download Roblox directly from www.Roblox.com.
Advertising
OpenSSH problem unfixed since October 2024
Since October 2024, there has been a problem that the OpenSSH (Open Secure Shell) service cannot be started for some users. No SSH connections can then be established.
The OpenSSH service fails without detailed logging and manual intervention is required to run the sshd.exe process, for example, according to the support article for KB5050009 in the Known Issues.
This issue affects customers with Windows Enterprise, Windows IOT and Windows Education systems, with a limited number of devices said to be affected. Microsoft is currently investigating whether private customers with Windows Home or Pro editions are affected.
Das Problem mit dem nicht mehr startbaren Dienst SgrmBroker habe ich im Blog-Beitrag Windows 10/Server 2022: Dienst SgrmBroker startet nach Jan. 2025-Update (KB5049981) nicht mehr behandelt. Der Fehler hat wohl keine praktischen Konsequenzen, Windows funktioniert weiterhin.
Bitlocker recovery key is requested
I have come across two reports of problems with Bitlocker. In a private German message on Facebook, a user complained that the Bitlocker recovery key was suddenly being requested around Patchday.
Particularly unpleasant: The Bitlocker recovery key is stored in the user's Microsoft account – this is known. However, when trying to access the Microsoft account, the user receives the error message shown in the screenshot above. They are locked out of their Microsoft account and can no longer access the key. However, the problem with requesting the recovery key seems to have been resolved after several restarts.
Another Bitlocker problem
The colleagues from Bleeping Computer report in the article Windows BitLocker bug triggers warnings on devices with TPMs about another bug in Windows that causes Bitlocker warnings. They refer to the Microsoft support article After enabling BitLocker, "For your security, some settings are managed by your administrator" is unexpectedly displayed. It shows affected users that Bitlocker is managed by an administrator. However, the bug is probably not directly related to the January 2024 patchday. Anyone from the readership affected?
Similar articles
Microsoft Security Update Summary (January 14, 2025)
Patchday: Windows 10/11 Updates (January 14, 2025)
Patchday: Windows Server Updates (January 14, 2025)
Patchday: Microsoft Office Updates (January 2025)
Review: Windows Patchday issues January 2025
Windows 10/Server 2022: SgrmBroker service no longer starts after Jan. 2025 update (KB5049981)
Attention: Problems with Windows January 2025 updates and Citrix environments (session recordings)
Advertising
