Windows 10 out-of-band update

Microsoft has released a fix for a bug that shipped with the June 2020 Patch Tuesday and stopped all print jobs on certain printers. And as of Tuesday it is now also using machine learning to bump up PCs on older versions of Windows 10 to the latest feature release, Windows 10, version 2004. 

The out-of-band update should fix Ricoh, Canon, Panasonic, and Brother printers that Windows 10 admins reported stopped working after installing the security update. 

Admins were rolling back the Patch Tuesday update to fix the printer issue, so Microsoft's new update should allow affected organizations and users to reinstall the security updates, which were part of the largest Patch Tuesday on record.

Know more : How to find your NOC.

Microsoft details a fix for the printer issue on its Windows 10 Message center page. A fix is available for Windows 10 versions 1803 through to 1909 and corresponding version of Windows Server. 

A fix for other affected versions of Windows will be released in the next few days, according to Microsoft. These include the latest feature release, Windows 10, version 2004, as well as the older version 1709, version 1607, Windows 10 Enterprise LTSC 2015, and Windows 8.1. Also affected are Windows Server version 1709, Windows Server 2012 R2, and Windows Server 2012.  

The update isn't installed automatically through Windows Update or WSUS, so users with affected printers will need to manually install it from the Microsoft Update Catalog. 

"An out-of-band optional update is now available on the Microsoft Update Catalog to address a known issue in which certain printers may be unable to print after installing updates released June 9, 2020," Microsoft said. 

"We recommend you only install this optional update if you are affected by this issue. For more information, see the known issues section for your version of Windows 10 or see the links below."

The KB4567512 update addresses the printer bug in Windows 10 1903 and 1909, while KB4567513 fixes it in version 1809, and KB4567514 fixes it in version 1803.  



  • No Comment Yet
Please login first for post a comment