Microsoft pushes emergency fix for Windows 10 KB5004945 printing problem …
Microsoft has actually launched an emergency fix for printing problems impacting Zebra and also Dymo invoice or tag printers triggered by modifications in the lately launched KB5003690, KB5004760, and also KB5004945 updates.
This week, Microsoft launched the out-of-band KB5004760 and also KB5004945 protection upgrade to fix the proactively made use of PrintNightmare susceptability.
After mounting the upgrade, Windows customers located that they might no more publish to their Zebra and also Dymo tag and also invoice printers attached by means of USB.
As most individuals reported the problems after mounting the out-of-band updates, customers thought that the trouble was associated with the spot for the PrintNightmare susceptability.
However, Microsoft introduced today that the problems are not “unrelated to CVE-2021-34527 or CVE-2021-1675,” and also are triggered by modifications presented in the June 2021 collective upgrade sneak peek.
Fixed utilizing Known Issue Rollback attribute
Thursday evening, Microsoft launched an emergency fix for Windows 10 2004, Windows 10 20H2, and also Windows 10 21H1 to solve these problems.
“After mounting KB5003690 or later on updates (consisting of out of band updates, KB5004760 and also < a rel=" nofollow noopener" data-linktype=" exterior" href="https://support.microsoft.com/help/5004945" target=" _ space">KB5004945), you might have issues printing to certain printers. Most affected printers are receipt or label printers that connect via USB,” Microsoft mentioned in a brand-new problem published to the Windows 10 health and wellness control panel.
This fix is being turned out with Microsoft’s Known Issue Rollback (KIR) attribute, which disperses repairs for recognized problems with Windows Update and also need to get to most individuals within 24 hrs.
“This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster,” describes Microsoft.
“For enterprise-managed gadgets that have actually set up an impacted upgrade and also experienced this problem, it can be solved by mounting and also setting up a unique Group Policy Note Devices require to be reactivated after setting up the uniqueGroup Policy For assistance, please see How to use Group Policy to deploy a Known Issue Rollback For basic info on utilizing Group Policies, see Group Policy Overview“
When Microsoft launches brand-new collective updates to fix a pest, the brand-new modifications might trigger various other problems inWindows 10 Using diagnostics and also telemetry shared by Windows 10 computer systems, Microsoft can identify when problems develop and also figure out just how broad an effect they have.
If the problems are impacting a huge populace of Windows 10 customers, Microsoft will certainly release a Known Issue Rollback (KIR) with Windows Update that disables the modification creating the problems, as revealed listed below.
While these repairs are dispersed by means of Windows Update, they are not provided as a real upgrade. Therefore, there is no very easy means for Windows 10 customers to recognize when a Known Issue Rollout fix is set up without examining the Registry.
To figure out if this KIR is set up on your computer system, you can open up the Registry Editor and also examine if the complying with essential exists. If it does, after that the KIR has actually been set up on your computer system.
If you do not see the KIR in the Registry, do not panic. It merely indicates it has actually not been lowered to your computer system yet.
Microsoft claims the rollout is anticipated to be total within 24 hrs which reactivating the computer system might quicken this procedure.