14 DAY TRIAL // The most recent updates shipped by Microsoft as part of the June 2020 Patch Tuesday cycle also come with an unexpected issue breaking down printers on some devices.
Microsoft confirmed shortly after the rollout started that some printers indeed stop working after these updates are installed, and the company said that in some cases, even PDF printers are affected.
No workaround was available at first, and some turned to the complete removal of these updates to be able to use their printers. Needless to say, this wasn’t necessarily the best way to go since the June 2020 Patch Tuesday updates included major security fixes, so Microsoft needed to act fast to repair the whole thing.
And today, the software giant is offering a set of new updates for the affected Windows versions, and users whose printers stopped working after this month’s Patch Tuesday are now recommended to install them too.
The new updates are the following:
- Windows 10, version 1903/1909: KB4567512
- Windows 10, version 1809: KB4567513
- Windows 10, version 1803: KB4567514
Not available on Windows Update
All these updates come with a single fix, as Microsoft itself explains in the official release notes:
“Updates an issue that might prevent certain printers from printing, generate print errors, or cause apps and print spoolers to close unexpectedly.”
What’s important to know is that the updates are not available via Windows Update and must be downloaded and installed manually from the Microsoft Update Catalog. The download links are available on the pages mentioned above if you need to get the updates.
At this point, there’s just one known issue that Microsoft needs to resolve, and it concerns a broken Internet connection for some users.
“After installing this update on a Windows 10 device with a wireless wide area network (WWAN) LTE modem, reaching the internet might not be possible. However, the Network Connectivity Status Indicator (NCSI) in the notification area might still indicate that you are connected to the internet,” the company says.
A fix for this problem is supposed to go live in a future update.