Windows 10’s one billion users need to be on high alert because Microsoft has issued serious update warnings and every Windows 10 user needs to take action. Go through this complete write-up to get the full information about how Microsoft’s new emergency fix Windows 10 Printing bugs.

Microsoft recently released an emergency fix for printing bug which harm both of the Zebra and the Dymo receipt or label printers cause by changes in the recent release KB5003690, KB5004760, and KB500495 updates.

This week, Microsoft released the out-of-band KB5004760 and KB5004945 security updates to fix the currently exploited PrintNigtmare vulnerability.

After installing the update, Windows users discover that they could no longer print to any of their Zebra and Dymo label and receipt printers connected through USB.

Almost all people expressed the issues right after installing the out-of-band updates, users expect that the problem was related to the bug for the PrintNightmare vulnerability.

Still, Microsoft revealed today that the concerns are not “related to CVE-2021-34527 or CVE-2021-1675,” and are harmed by changes made in the June 2021 increasing update preview.

Resolved by Utilizing famous Issues Rollback Features

On Thursday night, Microsoft revealed an emergency fix for Windows 10 2004, Windows 10 20H2, and Windows 10 21H1 to fixed these issues.

“After installing KB500390 or future updates including out of band updates like KB5004760 and KB5004945, you might have problem in printing to some printers. Most impacted printers are certified or labeled printers that connect via USB,” Microsoft said in a new issue posted to the Windows 10 health dashboard.

This resolve is being rolled out by Microsoft’s known Issue Rollback (KIR) characteristic, which administrates fixes for well-known issues through Windows Update and should reach most people within 24 hours.

Microsoft also explains in a search that “This problem is fixed using KIR short for Known Issue Rollback. Please note that it might take up to a day for the resolution to reproduce automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your devices faster.”

“For enterprise-managed devices that have installed an impactful update and come across this issue, it can be fixed by installing and configuring a specific Group Policy.”

Note: Your device needs to be restarted after configuring the special Group Policy.

When Microsoft releases new cumulative updates to resolve the issue, the new changes may cause other problems in Windows 10. Using diagnostics and telemetry shared by Windows 10 computers, Microsoft can discover when problems come up and know how big a harm they can give.

If the bugs are affecting a wide population of Windows 10 users, Microsoft will concern a Known Issue Rollback (KIR) through Windows Updates that disallow the change causing the issues, as mentioned below:

How to Check the KIR is Installed or Not?

While these issues are appropriated via Windows Update, they are not transmitted as an actual update. Therefore, there is no easiest way for Windows 10 users to determine when a Known Issues Rollout is fixed is installed without even going through the Registry.

To know whether this KIR is installed on your computer, you can launch the Registry Editor and check if the key which is given below exists. If it does, then the KIR has been installed on your computer.

Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Conrtol\FeatureManagement\Overrides\4\1861952651

If you do not see this KIR in the Repository, then no need to panic. It simply means that it has not been pushed down to your system yet.

Microsoft declares the rollout is about to be complete within 24 hours of time and that restarting your system may speed up or faster this whole process.