Update07/09/2025

KB5062570: upgrades the curl tool in Windows to version 8.13.0 to help protect against potential security risks

Windows Server 23H2
Microsoft

Update from:
patrick-devicebase (expert)

July 8, 2025—KB5062570 (OS Build 25398.1732)

Improvements
This security update includes improvements that were a part of update KB5060118 (released June 10, 2025) and KB5063774 (released July 1, 2025). The following summary outlines key issues addressed by the KB update after you install it. Also, included are available new features. The bold text within the brackets indicates the item or area of the change.

[DNS Server] Fixed: This update addresses an issue where a full zone transfer cannot be completed from a Windows DNS Server to another DNS Server when Extension Mechanisms for DNS is enabled.
[Language and character support] Fixed: An issue that affected some Chinese characters and experienced compliance issue with GB18030. These characters didn’t display correctly or weren’t accepted when using extended Unicode. A modern ICU-based solution now properly supports GB18030-2022 requirements.
[Performance] Fixed: This update addresses an issue that prevented the complete removal of unused language packs and Feature on Demand packages, which previously led to unnecessary storage use and longer Windows Update installation times.
[Security] This update upgrades the curl tool in Windows to version 8.13.0 to help protect against potential security risks, including unauthorized access to data or service disruptions.
[Microsoft RPC Netlogon protocol] This update includes a security hardening change to the Microsoft RPC Netlogon protocol. This change improves security by tightening access checks for a set of remote procedure call (RPC) requests. After this update is installed, Active Directory domain controllers will no longer allow anonymous clients to invoke some RPC requests through the Netlogon RPC server. These requests are typically related to domain controller location. Certain file and print service software can be affected, including Samba. If your organization uses Samba, please refer to the Samba release notes.