Content Release: Patches for Windows published 2026-01-28

Content in the Patches for Windows site has been released.

Modified:

  • Major [ID:507481901] 5074819: SQL Server 2022 RTM Cumulative Update (CU) 23 - SQL Server 2022 - KB5074819 (x64)
  • Major [ID:507812705] 5078127: Cumulative Update for Windows 11 Version 24H2 - Windows 11 Version 24H2 - KB5078127 (x64)
  • Major [ID:507812707] 5078127: Cumulative Update for Windows 11 Version 24H2 for ARM64 - Windows 11 Version 24H2 - KB5078127 (arm64)
  • Major [ID:507812701] 5078127: Cumulative Update for Windows 11, version 25H2 - Windows 11 Version 25H2 - KB5078127 (x64)
  • Major [ID:507812703] 5078127: Cumulative Update for Windows 11, version 25H2 for ARM64 - Windows 11 Version 25H2 - KB5078127 (arm64)
  • Major [ID:507813501] 5078135: Cumulative Update for Microsoft server operating system version 24H2 - Windows Server 2025 - KB5078135 (x64)

Reason for Update:

  • Relevance has been modified for OOB updates.
  • False relevance has been added to the Fixlet [ID:507481901], as Microsoft temporarily made it unavailable for download due to the issues in the update.

Additional Notes:

  • None.

Actions to Take:
None

Published site version:
Patches for Windows, Version: 4668

Additional links:

Application Engineering Team
HCL BigFix

The patches that have this relevance need to be corrected:
(it as integer < 7628 and it as integer != _HOTPATCH_UBR_) of value "UBR" of key "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" of native registry

With the relevance like that, they show up as not relevant.

With it modified like this it shows relevant:

(it as integer < 7628 and it != "HOTPATCH_UBR") of value "UBR" of key "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" of native registry

I believe the issue is that it is looking for an integer when it is actually checking for text.

Yall are either really fast or were already working on this issue as I posted. Within 10 minutes of posting, the updated relevance got pulled down.

Thanks!

1 Like