June 10, 2025—KB5060999 (OS Builds OS Builds 22621.5472 and 22631.5472)

This security update includes quality improvements. Key changes include:

• This build includes all the improvements in Windows 11, version 22H2.

• There are no additional issues documented in this release.

This security update includes improvements that were part of update KB5058502 (released May 27, 2025). The following summary outlines key issues addressed by the KB after you install it. Also, included are available new features. The bold text within the brackets indicates the item or area of the change.

• [Graphics] Fixed: This update addresses a graphics support issue that prevented some users from successfully connecting using Remote Desktop, resulting in errors like “The Remote Desktop Services session has ended” or “A remote desktop connection cannot be established.”

If you installed earlier updates, your device downloads and installs only the new updates contained in this package.

For more information about security vulnerabilities, see the Security Update Guide and the June 2025 Security Update.

Applies to: All users

Symptoms

There are reports of blurry or unclear CJK (Chinese, Japanese, Korean) text when displayed at 96 DPI (100% scaling) in Chromium-based browsers such as Microsoft Edge and Google Chrome. The March 2025 Preview Update introduced Noto fonts in collaboration with Google, for CJK languages as fallbacks to improve text rendering when websites or apps don’t specify appropriate fonts. The issue is due to limited pixel density at 96 DPI, which can reduce the clarity and alignment of CJK characters. Increasing the display scaling improves clarity by enhancing text rendering.

Workaround

As a temporary workaround, increase your display scaling to 125% or 150% to improve text clarity. For more information, see Change your screen resolution and layout in Windows.

We are investigating this issue and will provide more information when it is available.

Symptoms

Some devices in environments where IT admis use quality update (QU) deferral policies might experience delays in receiving the June 2025 Windows security update. Although the update was released on June 10, 2025, its update metadata timestamp reflects a date of June 20, 2025. This discrepancy might cause devices with configured deferral periods to receive the update later than expected.

Workaround

To accelerate deployment of the June 2025 updates, admins can take one of the following actions:

• Create an expedite policy to bypass deferral settings and deliver the update immediately if the organization is using Windows Autopatch.

• Adjust deployment rings or deferral configurations to reduce the delay window for affected devices.

This delay issue affects only the timing of update availability for organizations using QU deferral policies and doesn't impact the quality or applicability of the update. We will not change the metadata value from the current June 20, 2025, value. This workaround is the final resolution we will provide for this issue.