{"id":38543,"date":"2025-07-03T01:56:16","date_gmt":"2025-07-02T23:56:16","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=38543"},"modified":"2025-07-03T01:56:16","modified_gmt":"2025-07-02T23:56:16","slug":"windows-11-24h2-june-2025-update-issues-kb5060842-with-wrong-timestamp-and-print-to-pdf","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2025\/07\/03\/windows-11-24h2-june-2025-update-issues-kb5060842-with-wrong-timestamp-and-print-to-pdf\/","title":{"rendered":"Windows 11 24H2 June 2025 update issues: KB5060842 with wrong timestamp and Print to PDF"},"content":{"rendered":"

\"Windows\"[German<\/a>]The June 2025 update KB5060842 for Windows 10 24H2 was provided with an wrong timestamp (20.6.) in the meta files. This resulted in the update being delayed for installation on managed systems with update delay policies. The problem also occurs with Windows 10 22H2 and Windows 11 23H2. Microsoft has now confirmed this and will not fix anything, it's up to administrators to fix things. In addition, the \"Print to PDF\" issue I mentioned has also been confirmed as a problem.<\/p>\n

Update KB5060842 for Windows 11 24H2<\/h2>\n

\"\"Cumulative Update KB5060842<\/a> includes quality improvements and security patches for Windows 11 24H2 (see Patchday: Windows 10\/11 Updates (June 10,\u00a0 2025)<\/a>).\u00a0This update makes various security improvements to internal operating system functions (see Microsoft Security Update Summary (June 10, 2025)<\/a>). However, Microsoft had to release an out-of-band update for Windows 11 24H2 to fix issues with update KB5060842<\/a> (see Windows 11 24H2: Out-of-Band Update KB5063060<\/a>). For the updates, there was only one known issue with the release, which has been documented. Asian Noto fonts are displayed blurred.<\/p>\n

Wrong update delay for \"deferral policies\"<\/h2>\n

In the meantime, Microsoft has added the entry \"Update delay with deferral policies\" to the Known Issues of Update KB5060842<\/a> (noticed here<\/a>). It states that in managed environments where an update delay (deferral) has been configured via policies, the update is offered with a delay (probably after the date specified by the policy).<\/p>\n

Microsoft explains it this way: Although the update was released on June 10, 2025, the timestamp of the update metadata indicates the date of June 20, 2025. A client with activated update deferral will therefore not receive the update before June 20, 2025. This discrepancy can lead to devices with configured deferral periods receiving the update later than expected. An administrator told me, he checked the whole weekend, what went wrong with his deferral policies.<\/p>\n

Administrators can create an Expedit policy to bypass the deferral settings and deploy the update immediately. This works in organizations that use Windows Autopatch. Or the deployment rings or update delays configured for the clients can be adjusted to reduce the delay window for affected devices to receive the update.<\/p>\n

Microsoft writes that the issue only affects the timing of update availability for organizations using QU deferral policies. It has no impact on the quality or applicability of the update. Microsoft will not change the metadata value from the current value of June 20, 2025 and only offers the above workarounds as a last resort for this issue.<\/p>\n

Print to PDF does not work<\/h2>\n

In the Known Issues of update KB5060842<\/a>, Microsoft has meanwhile confirmed the known problem \"Print to PDF might not work\". After installing the April update KB5055627<\/a>, users notice that the Print to PDF<\/em> option is missing in the Print dialog box or that the print output as PDF does not work properly.<\/p>\n

Microsoft writes in the Know Issues that the Microsoft Print to PDF printer may no longer be displayed under Settings > Bluetooth & Devices > Printers & Scanners<\/em>. Users may also find that activating the Printing-PrintToPDFServices<\/em> function returns the error code 0x800f0922. The error code prevents the installation of the Microsoft Print to PDF printer driver in:<\/p>\n

C:\\Windows\\System32\\DriverStore\\FileRepository<\/p>\n

I just reported a similar situation in the blog post Windows 11 24H2: Microsoft Print to PDF is missing in fresh installs<\/a> and also mentioned the error code.<\/p>\n

As a workaround, Microsoft recommends activating the Printing-PrintToPDFServices<\/em> feature in Windows 11 24H2. This should be possible in the Windows Features dialog, or you can use the following PowerShell commands in the administrative PowerShell console.<\/p>\n

Disable-WindowsOptionalFeature -Online -FeatureName Printing-PrintToPDFServices-Features\u200b\u200b\u200b\u200b\u200b\u200b\u200b\r\n\r\nEnable-WindowsOptionalFeature -Online -FeatureName Printing-PrintToPDFServices-Features<\/pre>\n
If this does not work, there are some more tips in the blog post I linked. The problem should be fixed in the preview update KB5060829<\/a> from the end of June 2025.<\/p>\n
Similar articles:
\n<\/strong>Microsoft Security Update Summary (June 10, 2025)<\/a>
\nPatchday: Windows 10\/11 Updates (June 10,\u00a0 2025)<\/a>
\natchday: Windows Server-Updates (June 10,\u00a0 2025)<\/a>
\nPatchday: Microsoft Office Updates (June 10, 2025)<\/a><\/p>\n
Windows 11 24H2: Out-of-Band Update KB5063060<\/a>
\nWindows 10\/11: Preview Updates May 27, 28,2025<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
[German]The June 2025 update KB5060842 for Windows 10 24H2 was provided with an wrong timestamp (20.6.) in the meta files. This resulted in the update being delayed for installation on managed systems with update delay policies. The problem also occurs … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,22,2],"tags":[47,2925,195,194],"class_list":["post-38543","post","type-post","status-publish","format-standard","hentry","category-issue","category-update","category-windows","tag-issue","tag-patchday-6-2025","tag-update","tag-windows"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/38543","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=38543"}],"version-history":[{"count":1,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/38543\/revisions"}],"predecessor-version":[{"id":38544,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/38543\/revisions\/38544"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=38543"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=38543"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=38543"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}