June’s Patch Tuesday update for Windows 11 has stirred quite a commotion among users, prompting Microsoft to temporarily halt the rollout and issue an emergency patch. Unfortunately, this quick fix has led to a cascade of additional complications, and Microsoft now acknowledges that the challenges are far from over.
Among the newly emerged issues is a malfunction with the Print to PDF feature, specifically affecting systems running Windows 11 24H2. Microsoft downplays the severity of this bug, noting that it primarily impacts corporate users. The problem manifests in a rather perplexing manner: when users search for the “Print to PDF” option in the Settings app, it is conspicuously absent. Typically located under the printers and scanners settings, this option is no longer accessible, nor can it be activated via PowerShell.
In response, Microsoft is actively developing a solution through the optional preview update KB5060829, aimed at rectifying the PDF-related issues in Windows 11. However, this preview update is not without its own set of complications.
More problems with update KB5060829
To summarize the sequence of events: on June 10th, Microsoft rolled out Patch Tuesday update KB5060842, which introduced various issues. The following day, the out-of-band emergency update KB5063060 was released, only to exacerbate the situation further. Now, the optional preview update KB5060829 is adding to the list of concerns.
Users have reported a range of performance problems following the installation of the latest update. Some are experiencing cursor delays when using specific key combinations in games, while others have noted erratic behavior from the Windows Firewall. One Reddit user highlighted that they are receiving Firewall-related system events, suggesting that the Firewall may not be functioning correctly or is erroneously responding to perceived threats.
Despite these reports, Microsoft reassures users that there is no cause for alarm. The company has acknowledged the issue as a known problem that can be safely disregarded by affected users. They explain that upon restarting the system, new Firewall-related events may be logged even in the absence of actual incidents. This phenomenon is attributed to a new feature still in development, which is expected to resolve itself once fully implemented.
For those wary of encountering these issues, it may be prudent to postpone the installation of the optional KB5060829 update and instead await Microsoft’s upcoming Patch Tuesday update in July. If you have already installed it and are facing difficulties, rolling back the Windows update might provide a viable solution.
