The June 2025 cumulative update KB5060842 for Windows 11 version 24H2 has introduced several significant issues affecting system administrators and end-users alike. Notably, discrepancies in update metadata timestamps have led to deployment delays, and the "Print to PDF" functionality has been disrupted.
Upon its release on June 10, 2025, update KB5060842 was intended to deliver essential security patches and quality improvements. However, the update's metadata contained an incorrect timestamp dated June 20, 2025. This misalignment has caused delays in deployment for managed systems utilizing update deferral policies, as these systems rely on metadata timestamps to schedule updates. Consequently, devices configured with deferral settings have experienced unexpected postponements in receiving the update. Microsoft has acknowledged this issue but has indicated that it will not amend the metadata. Administrators are advised to implement Expedited policies or adjust deployment rings to mitigate the delay. (borncity.com)
Microsoft's handling of these issues has drawn criticism from the IT community. The decision not to correct the metadata timestamp places the onus on administrators to implement workarounds, potentially increasing the risk of misconfigurations. Additionally, the Print to PDF issue disrupts workflows for users who rely on this feature for document management.
If these commands do not resolve the issue, consult Microsoft's support resources for additional troubleshooting steps.
In conclusion, while update KB5060842 was intended to enhance Windows 11 version 24H2, the associated problems have necessitated proactive measures from both Microsoft and system administrators. By implementing the recommended workarounds and staying vigilant for further updates, users can navigate these challenges effectively.
Source: BornCity Windows 11 24H2 June 2025 update issues: KB5060842 with wrong timestamp and Print to PDF | Born's Tech and Windows World
Metadata Timestamp Discrepancy
Upon its release on June 10, 2025, update KB5060842 was intended to deliver essential security patches and quality improvements. However, the update's metadata contained an incorrect timestamp dated June 20, 2025. This misalignment has caused delays in deployment for managed systems utilizing update deferral policies, as these systems rely on metadata timestamps to schedule updates. Consequently, devices configured with deferral settings have experienced unexpected postponements in receiving the update. Microsoft has acknowledged this issue but has indicated that it will not amend the metadata. Administrators are advised to implement Expedited policies or adjust deployment rings to mitigate the delay. (borncity.com)Print to PDF Functionality Issues
Another critical problem associated with KB5060842 is the malfunction of the "Print to PDF" feature. Users have reported that the Microsoft Print to PDF printer is missing from the list of available printers, and attempts to activate the Printing-PrintToPDFServices feature result in error code 0x800f0922. This error prevents the installation of the necessary printer driver, rendering the feature inoperable. Microsoft has confirmed this issue and recommends enabling the Printing-PrintToPDFServices feature via the Windows Features dialog or using specific PowerShell commands. If these solutions are ineffective, further troubleshooting steps are available. (borncity.com)Additional Complications and Microsoft's Response
Beyond the aforementioned issues, KB5060842 has been linked to compatibility problems with certain applications, including games utilizing Easy Anti-Cheat services. Users have reported unexpected system reboots when launching these games. In response, Microsoft released an out-of-band update, KB5063060, to address these compatibility concerns. (windowslatest.com)Microsoft's handling of these issues has drawn criticism from the IT community. The decision not to correct the metadata timestamp places the onus on administrators to implement workarounds, potentially increasing the risk of misconfigurations. Additionally, the Print to PDF issue disrupts workflows for users who rely on this feature for document management.
Recommendations for Administrators and Users
To mitigate the impact of these issues, the following steps are recommended:- For Metadata Timestamp Discrepancy: Administrators should create Expedited policies to bypass deferral settings or adjust deployment rings to reduce the delay window for affected devices.
- For Print to PDF Issues: Attempt to enable the Printing-PrintToPDFServices feature through the Windows Features dialog or by executing the following PowerShell commands with administrative privileges:
Code:
Disable-WindowsOptionalFeature -Online -FeatureName Printing-PrintToPDFServices-Features
Enable-WindowsOptionalFeature -Online -FeatureName Printing-PrintToPDFServices-Features- For Compatibility Issues with Applications: Ensure that all applications, especially those utilizing Easy Anti-Cheat services, are updated to their latest versions. Apply the out-of-band update KB5063060 to address known compatibility issues.
In conclusion, while update KB5060842 was intended to enhance Windows 11 version 24H2, the associated problems have necessitated proactive measures from both Microsoft and system administrators. By implementing the recommended workarounds and staying vigilant for further updates, users can navigate these challenges effectively.
Source: BornCity Windows 11 24H2 June 2025 update issues: KB5060842 with wrong timestamp and Print to PDF | Born's Tech and Windows World
