June’s big Patch Tuesday update for Windows 11 has caused a bit of a mess for users, so much so that Microsoft had to briefly pause the update and issue an emergency patch… that ended up causing even more issues. Microsoft now admits that the problems don’t end there.
Subsequent issues that have surfaced include a bug where the Print to PDF feature no longer works, which occurs specifically on systems with Windows 11 24H2 and, according to Microsoft, isn’t dramatic because it mainly affects corporate customers.
The problem occurs as follows: if you search for the “Print to PDF” option in the Settings app, you’ll no longer be able to find it. It’s normally found under the options for printers and scanners, but it’s no longer there. The option can also no longer be activated via PowerShell.
Microsoft is already working on a solution for this with optional preview update KB5060829, intended to resolve PDF problems in Windows 11. However, this preview update is also raising more problems.
More problems with update KB5060829
Let’s recap. On June 10th, Microsoft released Patch Tuesday update KB5060842, which caused issues. On June 11th, we got the out-of-band emergency update KB5063060, which caused more issues. Now, optional preview update KB5060829 is causing still more issues.
Some users have been complaining about Windows 11 performance problems after installing the update. Others are running into cursor delays when certain key combinations are used in games. Yet others are saying it causes the Windows Firewall to go haywire, with one Reddit user reporting that they’re seeing Firewall-related system events. It appears as if Firewall is no longer working properly or trying to fend off an attack.
Microsoft, however, says there’s no cause for concern. It’s a known problem that can be safely ignored by users who are getting it. Whenever the system is restarted, new Firewall-related system events are logged even without there being any real incidents. According to Microsoft, it’s due to a new feature that’s still under development, so the issue should resolve itself once the feature is fully implemented.
If you don’t want to risk these problems, you should hold off on installing the optional KB5060829 update and instead wait for Microsoft’s big Patch Tuesday update in July. If you’ve already installed it, you might be able to resolve any issues by rolling back the Windows update.
