June 10, 2025—KB5060842 (OS Build 26100.4349)

Applies to: All users

Symptom

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

Microsoft has shared its findings on the blurry text issue at 96 DPI, along with potential solutions with Google for further discussion. For additional support, users can report issues related to Noto CJK fonts through the official Google Noto Fonts GitHub repository.

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.

Applies to: Enterprise customers and IT admins

Symptoms

After installing KB5055627, you might encounter issues with the Microsoft Print to PDF functionality. Specifically, the Microsoft Print to PDF printer might no longer appear under Settings > Bluetooth & devices > Printers & scanners. You might also notice that enabling the Printing-PrintToPDFServices-Feature returns error code 0x800f0922, which prevents the installation of the Microsoft Print to PDF printer driver located in C:\Windows\System32\DriverStore\FileRepository.

To address this, try enabling the Printing-PrintToPDFServices-Feature using one of the following options:

Option 1: Press Windows + R, type optional features, and enable Microsoft Print to PDF in the Windows Features dialog.

Option 2: Open PowerShell as Administrator and run the following commands:

1. Disable-WindowsOptionalFeature -Online -FeatureName Printing-PrintToPDFServices-Features​​​​​​​

2. Enable-WindowsOptionalFeature -Online -FeatureName Printing-PrintToPDFServices-Features

   Note: The final command might encounter an error with code 0x800f0922.

Workaround

This issue is addressed in KB5060829.